unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: [drew.adams@oracle.com: RE: file-cache doc should state thatthecache is non-persistent]
Date: Tue, 28 Mar 2006 12:03:28 -0800	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICCEDGDEAA.drew.adams@oracle.com> (raw)
In-Reply-To: <upsk6beg7.fsf@gnu.org>

    >     Btw, should we merge the "File Name Cache" section with
    >     the following one, "File Convenience"?  They are both short,
    >     and the file cache is certainly a convenience feature of the
    >     kind described in the latter section.
    >
    > No, I don't think that's a very good idea. File Name Cache is
    > a reasonable, self-contained topic. File Convenience is, currently,
    > a grab-bag or catch-all.

    There's nothing wrong with a grab-bag section describing a feature
    that has several commands.

I didn't say there was anything wrong with that (though that node could
benefit from a bit more structure (e.g. bullets), as it is essentially a
list).

What I said was that File Name Cache is a self-contained topic. I see no
reason to toss it into the grab bag, but the grab-bag list could (should)
include a link to File Name Cache.

Just one opinion.

  reply	other threads:[~2006-03-28 20:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 22:30 [drew.adams@oracle.com: RE: file-cache doc should state that the cache is non-persistent] Richard Stallman
2006-03-28 12:06 ` Eli Zaretskii
2006-03-28 15:32   ` [drew.adams@oracle.com: RE: file-cache doc should state that thecache " Drew Adams
2006-03-28 18:40     ` Eli Zaretskii
2006-03-28 20:03       ` Drew Adams [this message]
2006-03-29  8:14   ` [drew.adams@oracle.com: RE: file-cache doc should state that the cache " Richard Stallman

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=DNEMKBNJBGPAOPIJOOICCEDGDEAA.drew.adams@oracle.com \
    --to=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).