From: Juri Linkov <juri@jurta.org>
To: rms@gnu.org
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Info-history is not in the Info manual
Date: Sun, 30 Sep 2007 01:35:18 +0300 [thread overview]
Message-ID: <874phd5cf3.fsf@jurta.org> (raw)
In-Reply-To: <E1IZsXQ-0002Ar-5N@fencepost.gnu.org> (Richard Stallman's message of "Mon\, 24 Sep 2007 14\:20\:08 -0400")
> I see no reason to delay documenting this command.
> Would someone please give it a try?
I documented it in Emacs-22. I'm not sure if it will propagate to the trunk
or not after the recent changes of the doc directory layout.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2007-09-29 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 8:51 Info-history is not in the Info manual Drew Adams
2007-09-24 0:54 ` Juri Linkov
2007-09-24 1:21 ` Drew Adams
2007-09-24 18:20 ` Richard Stallman
2007-09-29 22:35 ` Juri Linkov [this message]
2007-09-29 23:03 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874phd5cf3.fsf@jurta.org \
--to=juri@jurta.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).