From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 965@debbugs.gnu.org
Subject: bug#965: 23.0.60; filesets doc
Date: Sun, 09 Feb 2014 19:43:04 -0800 [thread overview]
Message-ID: <87txc7fx9z.fsf@building.gnus.org> (raw)
In-Reply-To: <000001c91486$11e281c0$0200a8c0@us.oracle.com> (Drew Adams's message of "Thu, 11 Sep 2008 20:17:18 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> Some quick feedback on the filesets doc:
>
> 1. `i' in the Emacs manual followed by `filesets' shows index entries
> `filesets' and `filesets <1>'. The former is not about filesets in
> general, but about version control editing. The latter is the normal
> filesets entry, but `<1>' means nothing to users.
Seems to be fixed now.
> 2. There is no index entry for `file set' or `file-set' or `sets of
> files'. A user might not know that `fileset' just happens to be
> written that (non-standard) way.
Adding these spelling variations to the index doesn't seem very productive.
> 3. Node Filesets: "initially creates only the current file": no file
> is _created_.
Can't find that string in the manual.
> 7. There is nothing in the Emacs-Lisp manual about filesets. The
> fileset features and the Emacs Lisp behind them (e.g. keywords) should
> be explained (somewhere). Presumably, filesets should be of interest
> to Lisp programmers.
It seems more useful to users than to Lisp programmers. I've never
heard of the stuff until now.
Anyway, closing.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-02-10 3:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 3:17 bug#965: 23.0.60; filesets doc Drew Adams
2008-09-12 6:29 ` Drew Adams
2008-09-12 17:16 ` Drew Adams
2011-07-06 18:29 ` Lars Magne Ingebrigtsen
2011-07-06 19:25 ` Drew Adams
2011-07-07 16:25 ` Lars Magne Ingebrigtsen
2011-07-07 16:39 ` Drew Adams
2011-07-07 16:44 ` Lars Magne Ingebrigtsen
2014-02-10 3:43 ` Lars Ingebrigtsen [this message]
2014-02-10 4:27 ` Drew Adams
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=87txc7fx9z.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=965@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).