From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-syntax:master commit in: syntax/
Date: Sun, 20 Feb 2022 16:03:07 +0000 (UTC) [thread overview]
Message-ID: <1645372792.7c4da79abe0d70a73f725d804ff06dd3f9f6a806.mgorny@gentoo> (raw)
commit: 7c4da79abe0d70a73f725d804ff06dd3f9f6a806
Author: Anna “CyberTailor” <cyber <AT> sysrq <DOT> in>
AuthorDate: Thu Feb 17 16:18:30 2022 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 20 15:59:52 2022 +0000
URL: https://gitweb.gentoo.org/proj/gentoo-syntax.git/commit/?id=7c4da79a
syntax/gentoo-make-conf: highlight F(C)FLAGS
Signed-off-by: Anna Vyalkova <cyber+gentoo <AT> sysrq.in>
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
syntax/gentoo-make-conf.vim | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/syntax/gentoo-make-conf.vim b/syntax/gentoo-make-conf.vim
index d66033c..e843177 100644
--- a/syntax/gentoo-make-conf.vim
+++ b/syntax/gentoo-make-conf.vim
@@ -118,8 +118,9 @@ hi def link GentooMakeConfEAPIN Error
hi def link GentooMakeConfEAPIX Preproc
" }}}
-" C*FLAGS {{{
+" C*FLAGS and F*FLAGS {{{
syn match GentooMakeConfECFLAGS /C\(XX\)\?FLAGS/ contained nextgroup=GentooMakeConfECFLAGSE skipwhite
+syn match GentooMakeConfECFLAGS /FC\?FLAGS/ contained nextgroup=GentooMakeConfECFLAGSE skipwhite
syn match GentooMakeConfECFLAGSE /=/ contained nextgroup=GentooMakeConfECFLAGSV,GentooMakeConfECFLAGSVNoQ skipwhite
syn cluster GentooMakeConfECFLAGSIC add=GentooMakeConfECFLAGSIB1,GentooMakeConfECFLAGSIB2,GentooMakeConfECFLAGSIB3,GentooMakeConfECFLAGSIX
syn region GentooMakeConfECFLAGSV contained start=/"/ end=/"/ contains=@GentooMakeConfECFLAGSIC
next reply other threads:[~2022-02-20 16:03 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 16:03 Michał Górny [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
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:50 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=1645372792.7c4da79abe0d70a73f725d804ff06dd3f9f6a806.mgorny@gentoo \
--to=mgorny@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