From: "Tim Harder" <radhermit@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-syntax:master commit in: syntax/
Date: Sat, 29 Nov 2014 07:50:57 +0000 (UTC) [thread overview]
Message-ID: <1417247322.a3a9d028acae0af472beb7c29eb9e6da9a508b02.radhermit@gentoo> (raw)
commit: a3a9d028acae0af472beb7c29eb9e6da9a508b02
Author: Tim Harder <radhermit <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 29 07:48:42 2014 +0000
Commit: Tim Harder <radhermit <AT> gentoo <DOT> org>
CommitDate: Sat Nov 29 07:48:42 2014 +0000
URL: http://sources.gentoo.org/gitweb/?p=proj/gentoo-syntax.git;a=commit;h=a3a9d028
remove special highlighting for gentoo cvs headers
This feels pointless and causes bug #297282 anyway.
---
syntax/gentoo-common.vim | 6 ------
1 file changed, 6 deletions(-)
diff --git a/syntax/gentoo-common.vim b/syntax/gentoo-common.vim
index d509833..b3e2ae8 100644
--- a/syntax/gentoo-common.vim
+++ b/syntax/gentoo-common.vim
@@ -8,10 +8,6 @@ if &compatible || v:version < 603
finish
endif
-syn region GentooHeaderBlock start=/\%^\(#\)\@=/ end=/^$/ contains=GentooHeader
-syn region GentooHeader contained start=/^#/ end=/$/ contains=GentooHeaderCVSVar
-syn region GentooHeaderCVSVar contained start=/\$\S\+:/ end=/\$/
-
syn match GentooBug contained /\(\([gG]entoo \|[dD]ebian \|[sS]ource[Ff]orge \)\?[Bb]ug \(#\s*\)\?\|#\)\d\{1,\}/
" bad space
@@ -19,7 +15,5 @@ syn region GentooError start=/^ / end=/$/
" trailing whitespace
syn match GentooError /\s\+$/
-hi def link GentooHeader Comment
-hi def link GentooHeaderCVSVar PreProc
hi def link GentooBug Underlined
hi def link GentooError Error
next reply other threads:[~2014-11-29 7:51 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 7:50 Tim Harder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-29 14:15 [gentoo-commits] proj/gentoo-syntax:master commit in: syntax/ Michał Górny
2023-06-14 14:25 Michał Górny
2023-03-11 20:42 Michał Górny
2023-03-11 20:42 Michał Górny
2023-03-09 5:46 Michał Górny
2023-03-09 5:46 Michał Górny
2023-03-09 5:46 Michał Górny
2023-03-09 5:46 Michał Górny
2023-03-09 5:46 Michał Górny
2023-02-01 5:03 Michał Górny
2022-07-13 5:26 Michał Górny
2022-05-02 19:06 Michał Górny
2022-02-20 16:03 Michał Górny
2022-02-20 16:03 Michał Górny
2022-02-20 16:03 Michał Górny
2022-02-20 16:03 Michał Górny
2021-09-01 16:21 Michał Górny
2021-04-28 7:27 Michał Górny
2020-12-16 13:32 Michał Górny
2020-10-05 15:27 Michał Górny
2019-12-13 10:52 Michał Górny
2019-12-13 7:16 Michał Górny
2019-11-27 8:09 Michał Górny
2019-11-27 8:09 Michał Górny
2019-11-27 8:09 Michał Górny
2019-09-30 7:28 Michał Górny
2019-05-25 6:45 Michał Górny
2019-05-25 6:45 Michał Górny
2018-09-15 19:18 Michał Górny
2018-08-21 8:02 Michał Górny
2018-08-21 8:02 Michał Górny
2018-08-21 8:02 Michał Górny
2018-08-21 8:02 Michał Górny
2018-08-21 8:02 Michał Górny
2018-08-21 8:02 Michał Górny
2018-08-21 8:02 Michał Górny
2018-08-21 8:02 Michał Górny
2018-08-20 20:37 Michał Górny
2018-08-20 20:37 Michał Górny
2018-08-20 20:37 Michał Górny
2018-08-20 20:10 Michał Górny
2018-08-14 13:58 Michał Górny
2018-08-14 13:55 Michał Górny
2018-08-14 13:55 Michał Górny
2016-03-05 23:50 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2014-11-29 18:36 Tim Harder
2014-11-29 8:08 Tim Harder
2014-11-29 7:19 Tim Harder
2014-11-29 7:19 Tim Harder
2014-11-29 4:58 Tim Harder
2014-11-29 4:41 Tim Harder
2014-11-29 4:41 Tim Harder
2014-11-02 0:28 Tim Harder
2014-11-02 0:28 Tim Harder
2013-05-31 8:26 Tim Harder
2013-01-24 20:00 Tim Harder
2012-11-06 21:20 Christian Ruppert
2012-04-18 19:47 Christian Ruppert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1417247322.a3a9d028acae0af472beb7c29eb9e6da9a508b02.radhermit@gentoo \
--to=radhermit@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox