From: David Kastrup <dak@gnu.org>
To: storm@cua.dk (Kim F. Storm)
Cc: angeli@caeruleus.net, Eli Zaretskii <eliz@gnu.org>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Split man directory
Date: Wed, 05 Sep 2007 12:10:42 +0200 [thread overview]
Message-ID: <86ir6pbexp.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <877in51myr.fsf@kfs-lx.testafd.dk> (Kim F. Storm's message of "Wed\, 05 Sep 2007 11\:27\:24 +0200")
storm@cua.dk (Kim F. Storm) writes:
> Richard Stallman <rms@gnu.org> writes:
>
>> Indeed. But instead of `man', why not use the GNU-standard `doc'?
>> Thus, we will have
>>
>> doc/emacs
>> doc/lispref
>> doc/lispintro
>> doc/contrib (for other manuals)
>>
> I would suggest doc/userman rather than doc/emacs, as all of the manuals
> are about emacs one way or another.
I find doc/emacs more appropriate since, after all, emacs.info is
generated from the files in that directory.
--
David Kastrup
next prev parent reply other threads:[~2007-09-05 10:10 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1IPj9V-0003Yo-MM@fencepost.gnu.org>
2007-09-01 2:49 ` Split man directory Glenn Morris
2007-09-01 6:03 ` David Kastrup
2007-09-02 15:50 ` Richard Stallman
2007-09-02 15:57 ` David Kastrup
2007-09-03 18:25 ` Richard Stallman
2007-09-03 18:39 ` Glenn Morris
2007-09-04 16:45 ` Richard Stallman
2007-09-01 8:16 ` Eli Zaretskii
2007-09-01 19:11 ` Richard Stallman
2007-09-01 19:47 ` Glenn Morris
2007-09-02 16:42 ` Andreas Schwab
2007-09-03 18:25 ` Richard Stallman
2007-09-03 18:42 ` Glenn Morris
2007-09-03 19:19 ` Ralf Angeli
2007-09-03 19:39 ` Eli Zaretskii
2007-09-03 20:04 ` Leo
2007-09-03 21:32 ` David Kastrup
2007-09-04 12:17 ` Stefan Monnier
2007-09-04 12:25 ` David Kastrup
2007-09-04 13:43 ` Stephen Berman
2007-09-04 22:58 ` Richard Stallman
2007-09-04 13:46 ` Miles Bader
2007-09-04 16:45 ` Richard Stallman
2007-09-04 23:06 ` Juri Linkov
2007-09-05 20:02 ` Richard Stallman
2007-09-24 17:10 ` Splitting gnus.texi (was: Split man directory) Reiner Steib
2007-09-25 10:44 ` Richard Stallman
2007-09-26 0:23 ` Splitting gnus.texi Katsumi Yamaoka
2007-09-26 6:07 ` Reiner Steib
2007-09-30 20:50 ` Giorgos Keramidas
2007-09-30 21:34 ` Reiner Steib
2007-09-30 21:46 ` Giorgos Keramidas
2007-09-26 8:55 ` Juri Linkov
2007-09-26 18:14 ` Directory doc/gnus in Emacs CVS (was: Splitting gnus.texi) Reiner Steib
2007-10-20 22:33 ` Directory doc/gnus in Emacs CVS Bill Wohler
2007-10-21 9:37 ` Reiner Steib
2007-10-21 16:26 ` Richard Stallman
2007-09-26 0:30 ` Splitting gnus.texi Jay Belanger
2007-09-26 16:29 ` Richard Stallman
2007-09-05 9:27 ` Split man directory Kim F. Storm
2007-09-05 10:10 ` David Kastrup [this message]
2007-09-05 11:57 ` Miles Bader
2007-09-06 4:59 ` Richard Stallman
2007-09-06 5:23 ` Glenn Morris
2007-09-08 10:40 ` Eli Zaretskii
2007-09-04 16:45 ` Richard Stallman
2007-09-04 17:57 ` Ralf Angeli
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=86ir6pbexp.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=angeli@caeruleus.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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).