From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-syntax:master commit in: syntax/
Date: Wed, 14 Jun 2023 14:25:54 +0000 (UTC) [thread overview]
Message-ID: <1686752731.865f01aa04434838f0ed1915734e2200759d925b.mgorny@gentoo> (raw)
commit: 865f01aa04434838f0ed1915734e2200759d925b
Author: Paul Zander <negril.nx <AT> gmail <DOT> com>
AuthorDate: Wed Jun 14 12:04:40 2023 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Jun 14 14:25:31 2023 +0000
URL: https://gitweb.gentoo.org/proj/gentoo-syntax.git/commit/?id=865f01aa
syntax/ebuild.vim: Add eqawarn
Closes: https://github.com/gentoo/gentoo-syntax/pull/62
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
syntax/ebuild.vim | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/syntax/ebuild.vim b/syntax/ebuild.vim
index 17c774c..f998ab8 100644
--- a/syntax/ebuild.vim
+++ b/syntax/ebuild.vim
@@ -29,7 +29,7 @@ syn match bkshFunction "^\s*\<\h[0-9a-zA-Z_\-\.]*\>\s*()" skipwhite skipnl conta
" Default keywords
syn keyword EbuildCoreKeyword use has_version best_version use_with use_enable
-syn keyword EbuildCoreKeyword keepdir econf die einstall einfo ewarn eerror diropts
+syn keyword EbuildCoreKeyword keepdir econf die einstall einfo ewarn eqawarn eerror diropts
syn keyword EbuildCoreKeyword dobin docinto dodoc doexe doheader doinfo doins
syn keyword EbuildCoreKeyword dolib dolib.a dolib.so doman dosbin dosym emake exeinto
syn keyword EbuildCoreKeyword exeopts fowners fperms insinto insopts into libopts newbin
next reply other threads:[~2023-06-14 14:25 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 14:25 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-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: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=1686752731.865f01aa04434838f0ed1915734e2200759d925b.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