public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Mueller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/emacs:master commit in: eclass/
Date: Wed,  4 Sep 2013 19:12:58 +0000 (UTC)	[thread overview]
Message-ID: <1378321927.cf86331609a3e82f99313edf70e2e18f90a56623.ulm@gentoo> (raw)

commit:     cf86331609a3e82f99313edf70e2e18f90a56623
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Wed Sep  4 19:12:07 2013 +0000
Commit:     Ulrich Mueller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Sep  4 19:12:07 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/emacs.git;a=commit;h=cf863316

Add proper @CODE tags in comments.

---
 eclass/ChangeLog           |  3 +++
 eclass/elisp-common.eclass | 46 +++++++++++++++++++++++++++++++---------------
 2 files changed, 34 insertions(+), 15 deletions(-)

diff --git a/eclass/ChangeLog b/eclass/ChangeLog
index 9495777..d443777 100644
--- a/eclass/ChangeLog
+++ b/eclass/ChangeLog
@@ -778,6 +778,9 @@
 Copyright 2002-2012 Gentoo Foundation
 Distributed under the terms of the GNU General Public License v2
 
+  04 Sep 2013; Ulrich Müller <ulm@gentoo.org> elisp-common.eclass:
+  Add proper @CODE tags in comments.
+
   24 Aug 2012; Ulrich Müller <ulm@gentoo.org> elisp-common.eclass:
   Suppress warning for initial installation.
 

diff --git a/eclass/elisp-common.eclass b/eclass/elisp-common.eclass
index 4decc2c..8085e56 100644
--- a/eclass/elisp-common.eclass
+++ b/eclass/elisp-common.eclass
@@ -23,7 +23,9 @@
 #
 # When relying on the emacs USE flag, you need to add
 #
-#   	emacs? ( virtual/emacs )
+# @CODE
+# 	emacs? ( virtual/emacs )
+# @CODE
 #
 # to your DEPEND/RDEPEND line and use the functions provided here to
 # bring the files to the correct locations.
@@ -35,7 +37,9 @@
 # tested with function elisp-need-emacs(), which would typically be
 # called from pkg_setup(), as in the following example:
 #
-#   	elisp-need-emacs 23 || die "Emacs version too low"
+# @CODE
+# 	elisp-need-emacs 23 || die "Emacs version too low"
+# @CODE
 #
 # Please note that such tests should be limited to packages that are
 # known to fail with lower Emacs versions; the standard case is to
@@ -50,7 +54,9 @@
 # directory is added to the load-path which makes sure that all files
 # are loadable.
 #
-#   	elisp-compile *.el
+# @CODE
+# 	elisp-compile *.el
+# @CODE
 #
 # Function elisp-make-autoload-file() can be used to generate a file
 # with autoload definitions for the lisp functions.  It takes the output
@@ -70,16 +76,20 @@
 # choose something else, but remember to tell elisp-site-file-install()
 # (see below) the change, as it defaults to ${PN}.
 #
-#   	elisp-install ${PN} *.el *.elc
+# @CODE
+# 	elisp-install ${PN} *.el *.elc
+# @CODE
 #
 # To let the Emacs support be activated by Emacs on startup, you need
 # to provide a site file (shipped in ${FILESDIR}) which contains the
 # startup code (have a look in the documentation of your software).
 # Normally this would look like this:
 #
-#   	(add-to-list 'load-path "@SITELISP@")
-#   	(add-to-list 'auto-mode-alist '("\\.csv\\'" . csv-mode))
-#   	(autoload 'csv-mode "csv-mode" "Major mode for csv files." t)
+# @CODE
+# 	(add-to-list 'load-path "@SITELISP@")
+# 	(add-to-list 'auto-mode-alist '("\\.csv\\'" . csv-mode))
+# 	(autoload 'csv-mode "csv-mode" "Major mode for csv files." t)
+# @CODE
 #
 # If your Emacs support files are installed in a subdirectory of
 # /usr/share/emacs/site-lisp/ (which is strongly recommended), you need
@@ -108,11 +118,15 @@
 # Best practice is to define a SITEFILE variable in the global scope of
 # your ebuild (e.g., right after S or RDEPEND):
 #
-#   	SITEFILE="50${PN}-gentoo.el"
+# @CODE
+# 	SITEFILE="50${PN}-gentoo.el"
+# @CODE
 #
 # Which is then installed by
 #
-#   	elisp-site-file-install "${FILESDIR}/${SITEFILE}"
+# @CODE
+# 	elisp-site-file-install "${FILESDIR}/${SITEFILE}"
+# @CODE
 #
 # in src_install().  Any characters after the "-gentoo" part and before
 # the extension will be stripped from the destination file's name.
@@ -126,13 +140,15 @@
 # After that you need to recreate the start-up file of Emacs after
 # emerging and unmerging by using
 #
-#   	pkg_postinst() {
-#   		elisp-site-regen
-#   	}
+# @CODE
+# 	pkg_postinst() {
+# 		elisp-site-regen
+# 	}
 #
-#   	pkg_postrm() {
-#   		elisp-site-regen
-#   	}
+# 	pkg_postrm() {
+# 		elisp-site-regen
+# 	}
+# @CODE
 #
 # When having optional Emacs support, you should prepend "use emacs &&"
 # to above calls of elisp-site-regen().


             reply	other threads:[~2013-09-04 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 19:12 Ulrich Mueller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-31  8:34 [gentoo-commits] proj/emacs:master commit in: eclass/ Ulrich Müller
2015-12-20 15:36 Ulrich Müller
2015-05-25 13:19 Ulrich Müller
2015-05-25 13:19 Ulrich Müller
2015-05-25 13:19 Ulrich Müller
2014-06-11  9:15 Ulrich Müller
2014-06-07 10:32 Ulrich Müller
2014-05-19 17:38 Ulrich Müller
2014-05-18 14:53 Ulrich Müller
2014-05-18 14:53 Ulrich Müller
2013-11-04 21:34 Ulrich Müller
2013-10-31 15:07 Ulrich Müller
2013-08-02 16:46 Ulrich Mueller
2013-07-22 20:07 Ulrich Mueller
2013-07-18 20:36 Ulrich Mueller
2013-07-16 16:37 Mats Lidell

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=1378321927.cf86331609a3e82f99313edf70e2e18f90a56623.ulm@gentoo \
    --to=ulm@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