From: "Christian Ruppert" <idl0r@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-syntax:master commit in: syntax/
Date: Wed, 18 Apr 2012 19:47:04 +0000 (UTC) [thread overview]
Message-ID: <1334778418.b96040a131463343b609218a8d7b3bc0f64b7277.idl0r@gentoo> (raw)
commit: b96040a131463343b609218a8d7b3bc0f64b7277
Author: Christian Ruppert <idl0r <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 18 19:46:58 2012 +0000
Commit: Christian Ruppert <idl0r <AT> gentoo <DOT> org>
CommitDate: Wed Apr 18 19:46:58 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-syntax.git;a=commit;h=b96040a1
Highlight newicon
---
syntax/ebuild.vim | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/syntax/ebuild.vim b/syntax/ebuild.vim
index f91b66d..09da49d 100644
--- a/syntax/ebuild.vim
+++ b/syntax/ebuild.vim
@@ -62,7 +62,7 @@ syn keyword EbuildEutilsKeyword gen_usr_ldscript draw_line epatch have_NPTL get_
syn keyword EbuildEutilsKeyword emktemp enewuser enewgroup edos2unix make_desktop_entry unpack_pdv
syn keyword EbuildEutilsKeyword unpack_makeself check_license cdrom_get_cds cdrom_load_next
syn keyword EbuildEutilsKeyword cdrom_locate_file_on_cd strip-linguas epause ebeep built_with_use
-syn keyword EbuildEutilsKeyword make_session_desktop domenu doicon find_unpackable_file unpack_pdv
+syn keyword EbuildEutilsKeyword make_session_desktop domenu doicon newicon find_unpackable_file unpack_pdv
syn keyword EbuildEutilsKeyword set_arch_to_kernel set_arch_to_portage preserve_old_lib
syn keyword EbuildEutilsKeyword preserve_old_lib_notify built_with_use epunt_cxx dopamd newpamd
syn keyword EbuildEutilsKeyword make_wrapper
next reply other threads:[~2012-04-18 19:47 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 19:47 Christian Ruppert [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-06 21:20 [gentoo-commits] proj/gentoo-syntax:master commit in: syntax/ Christian Ruppert
2013-01-24 20:00 Tim Harder
2013-05-31 8:26 Tim Harder
2014-11-02 0:28 Tim Harder
2014-11-02 0:28 Tim Harder
2014-11-29 4:41 Tim Harder
2014-11-29 4:41 Tim Harder
2014-11-29 4:58 Tim Harder
2014-11-29 7:19 Tim Harder
2014-11-29 7:19 Tim Harder
2014-11-29 7:50 Tim Harder
2014-11-29 8:08 Tim Harder
2014-11-29 18:36 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
2016-03-05 23:50 Tim Harder
2018-08-14 13:55 Michał Górny
2018-08-14 13:55 Michał Górny
2018-08-14 13:58 Michał Górny
2018-08-20 20:10 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-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-09-15 19:18 Michał Górny
2019-05-25 6:45 Michał Górny
2019-05-25 6:45 Michał Górny
2019-09-30 7:28 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-12-13 7:16 Michał Górny
2019-12-13 10:52 Michał Górny
2020-10-05 15:27 Michał Górny
2020-12-16 13:32 Michał Górny
2021-04-28 7:27 Michał Górny
2021-09-01 16:21 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
2022-05-02 19:06 Michał Górny
2022-07-13 5:26 Michał Górny
2023-02-01 5:03 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-03-11 20:42 Michał Górny
2023-03-11 20:42 Michał Górny
2023-06-14 14:25 Michał Górny
2024-03-29 14:15 Michał Górny
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=1334778418.b96040a131463343b609218a8d7b3bc0f64b7277.idl0r@gentoo \
--to=idl0r@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