From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: [gnus git] branch no-gnus updated: m0-1-92-gaee2cfd =1= Several miscellaneous doc changes
Date: Thu, 12 Apr 2012 10:43:05 +0900 [thread overview]
Message-ID: <b4mlim1pvx2.fsf@jpl.org> (raw)
In-Reply-To: <b4mzkaik5j5.fsf@jpl.org>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
Katsumi Yamaoka wrote:
> So, should we do something on epa.texi? (I'm not very
> enthusiastic. ;-)
I changed mind, and tried making texinfmt.el support @comma{}.
Not tested thoroughly, but EMACSINFO got to work for epa.texi.
Though I needed to change epa.texi slightly in the @enumerate
section. Patches:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Patch for texinfmt.el --]
[-- Type: text/x-patch, Size: 875 bytes --]
--- texinfmt.el~ 2012-04-09 21:53:08.339416000 +0000
+++ texinfmt.el 2012-04-12 01:39:35.713076600 +0000
@@ -1085,7 +1085,8 @@
(while (/= (preceding-char) ?\})
(skip-chars-forward " \t\n")
(setq beg (point))
- (re-search-forward "[},]")
+ (while (and (re-search-forward "[},]" nil t)
+ (get-text-property (match-beginning 0) 'ignore)))
(setq next (point))
(forward-char -1)
(skip-chars-backward " \t\n")
@@ -1379,6 +1380,15 @@
(texinfo-discard-command))
\f
+;;; @comma
+
+(put 'comma 'texinfo-format 'texinfo-format-comma)
+(defun texinfo-format-comma ()
+ (texinfo-parse-arg-discard)
+ (insert ",")
+ (put-text-property (1- (point)) (point) 'ignore t))
+
+\f
;;; @kbdinputstyle, @vskip, headings & footings
;; These commands for not for Info and should never
;; appear in an Info environment; but if they do,
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: Patch for epa.texi --]
[-- Type: text/x-patch, Size: 611 bytes --]
--- epa.texi~ 2012-04-11 00:11:23.000000000 +0000
+++ epa.texi 2012-04-12 01:39:35.712076600 +0000
@@ -445,9 +445,12 @@
not you want to use gpg-agent. Here are some questions:
@enumerate
-@item Do you use GnuPG version 2 instead of GnuPG version 1?
-@item Do you use symmetric encryption rather than public key encryption?
-@item Do you want to use gpg-agent?
+@item
+Do you use GnuPG version 2 instead of GnuPG version 1?
+@item
+Do you use symmetric encryption rather than public key encryption?
+@item
+Do you want to use gpg-agent?
@end enumerate
Here are configurations depending on your answers:
prev parent reply other threads:[~2012-04-12 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1SFOLy-0003Wm-Pa@quimby.gnus.org>
2012-04-04 11:53 ` Katsumi Yamaoka
2012-04-10 18:49 ` Lars Magne Ingebrigtsen
2012-04-11 0:13 ` Katsumi Yamaoka
2012-04-11 7:51 ` Julien Danjou
2012-04-11 8:28 ` Katsumi Yamaoka
2012-04-11 8:40 ` Julien Danjou
2012-04-11 8:59 ` Katsumi Yamaoka
2012-04-12 1:43 ` Katsumi Yamaoka [this message]
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=b4mlim1pvx2.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).