public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
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: <1334044188.f86437a98c51b3c3a5c53c7f657379bc22a8993a.sping@gentoo> (raw)

commit:     f86437a98c51b3c3a5c53c7f657379bc22a8993a
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 10 07:49:48 2012 +0000
Commit:     Sebastian Pipping <sping <AT> gentoo <DOT> org>
CommitDate: Tue Apr 10 07:49:48 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/emacs-tools.git;a=commit;h=f86437a9

Small syntax fixes in gentoo-syntax.texi.

svn path=/gentoo-syntax/; revision=1727

---
 ChangeLog          |    4 ++++
 gentoo-syntax.texi |   20 ++++++++++----------
 2 files changed, 14 insertions(+), 10 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index bf292cf..95919bd 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2012-04-10  Ulrich Müller  <ulm@gentoo.org>
+
+	* gentoo-syntax.texi: Small syntax fixes.
+
 2012-02-09  Ulrich Müller  <ulm@gentoo.org>
 
 	* gentoo-syntax.el (ebuild-mode-arch-regexp): Allow whitespace at

diff --git a/gentoo-syntax.texi b/gentoo-syntax.texi
index 2fb5c83..6355846 100644
--- a/gentoo-syntax.texi
+++ b/gentoo-syntax.texi
@@ -21,7 +21,7 @@ later version published by the Free Software Foundation.
 @dircategory Gentoo
 @dircategory Emacs
 @direntry
-* gentoo-syntax: (gentoo-syntax).         Describing a mode for ebuilds, eclasses and eselect modules
+* gentoo-syntax: (gentoo-syntax).       Major mode for ebuilds, eclasses and eselect modules.
 @end direntry
 
 
@@ -62,11 +62,11 @@ of often needed commands (like KEYWORDS manipulation) or fast-track
 creation of new ebuilds by skeleton support.
 
 @menu
-* Commands:: What gentoo-syntax provides
-* ebuild-mode:: Editing ebuilds
-* eclass-mode:: Editing eclasses
-* eselect-mode:: Editing eselect modules
-* gentoo-newsitem-mode:: Editing GLEP 42 news items
+* Commands:: What gentoo-syntax provides.
+* ebuild-mode:: Editing ebuilds.
+* eclass-mode:: Editing eclasses.
+* eselect-mode:: Editing eselect modules.
+* gentoo-newsitem-mode:: Editing GLEP 42 news items.
 @end menu
 
 @node Commands, ebuild-mode, Top, Top
@@ -92,7 +92,7 @@ activated.  So every user has the choice for his/her preferred way of
 interfacing with Emacs.
 
 @node ebuild-mode, eclass-mode, Commands, Top
-@chapter Describing ebuild-mode
+@chapter ebuild-mode
 @section Writing a new ebuild
 Starting a completely new ebuild from scratch is best done by inserting
 an ebuild skeleton.  The command @code{ebuild-mode-skeleton} does this
@@ -185,16 +185,16 @@ Create a ChangeLog entry.
 @end table
 
 @node eclass-mode, eselect-mode, ebuild-mode, Top
-@chapter Describing eclass-mode
+@chapter eclass-mode
 There is no special eclass-mode but ebuild-mode is used without the
 commands that make no sense in eclasses.
 
 @node eselect-mode, gentoo-newsitem-mode ,eclass-mode, Top
-@chapter Describing eselect-mode
+@chapter eselect-mode
 This mode only supports highlighting of special eselect keywords.
 
 @node gentoo-newsitem-mode, ,eselect-mode, Top
-@chapter Describing gentoo-newsitem-mode for GLEP 42 news items
+@chapter gentoo-newsitem-mode for GLEP 42 news items
 This mode supports the highlighting of relevant keywords for GLEP 42
 news items.  These news items get displayed if special criteria for
 installed packages or profiles are met on the user's system.  Special



             reply	other threads:[~2012-05-06 16:11 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=1334044188.f86437a98c51b3c3a5c53c7f657379bc22a8993a.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