From: "Sebastian Pipping" <sping@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/emacs-tools:gentoo-syntax commit in: /
Date: Sun, 6 May 2012 16:06:22 +0000 (UTC) [thread overview]
Message-ID: <1328826359.06ed06be461690bd7c2beabf3b429ebd427691a5.sping@gentoo> (raw)
commit: 06ed06be461690bd7c2beabf3b429ebd427691a5
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu Feb 9 22:25:59 2012 +0000
Commit: Sebastian Pipping <sping <AT> gentoo <DOT> org>
CommitDate: Thu Feb 9 22:25:59 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/emacs-tools.git;a=commit;h=06ed06be
Allow whitespace at beginning of line in ebuild-mode-arch-regexp, bug 402573.
svn path=/gentoo-syntax/; revision=1723
---
ChangeLog | 5 +++++
gentoo-syntax.el | 2 +-
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 3e110db..bf292cf 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2012-02-09 Ulrich Müller <ulm@gentoo.org>
+
+ * gentoo-syntax.el (ebuild-mode-arch-regexp): Allow whitespace at
+ beginning of line, bug 402573.
+
2012-01-21 Christian Faulhammer <fauli@gentoo.org>
* ebuild-mode-keywords.el (ebuild-mode-keywords-savedconfig):
diff --git a/gentoo-syntax.el b/gentoo-syntax.el
index cbb519f..fa53a0b 100644
--- a/gentoo-syntax.el
+++ b/gentoo-syntax.el
@@ -112,7 +112,7 @@ A formfeed is not considered whitespace by this function."
ebuild-mode-arch-list))
(defvar ebuild-mode-arch-regexp
- "^KEYWORDS=[\"']\\([^\"]*\\)[\"'][ \t]*$")
+ "^[ \t]*KEYWORDS=[\"']\\([^\"]*\\)[\"'][ \t]*$")
(defvar ebuild-mode-licenses
(condition-case nil
next reply other threads:[~2012-05-06 16:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 16:06 Sebastian Pipping [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-04 19:21 [gentoo-commits] proj/emacs-tools:gentoo-syntax commit in: / Ulrich Mueller
2013-03-09 7:42 Ulrich Mueller
2013-03-09 7:42 Ulrich Mueller
2013-03-09 7:42 Ulrich Mueller
2013-03-09 7:42 Ulrich Mueller
2013-01-13 21:15 Ulrich Mueller
2013-01-13 21:15 Ulrich Mueller
2012-09-22 22:47 Ulrich Mueller
2012-09-22 21:26 Ulrich Mueller
2012-09-22 21:26 Ulrich Mueller
2012-09-22 20:48 Ulrich Mueller
2012-09-22 17:34 Ulrich Mueller
2012-09-22 17:34 Ulrich Mueller
2012-09-22 17:34 Ulrich Mueller
2012-09-22 17:34 Ulrich Mueller
2012-06-09 13:10 Ulrich Mueller
2012-05-06 18:47 Ulrich Mueller
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
2012-05-06 16:06 Sebastian Pipping
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=1328826359.06ed06be461690bd7c2beabf3b429ebd427691a5.sping@gentoo \
--to=sping@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