unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: man/files.texi
Date: Sun, 27 Mar 2005 13:00:31 +0200	[thread overview]
Message-ID: <01c532bc$Blat.v2.4$571d36e0@zahav.net.il> (raw)
In-Reply-To: <200503270351.j2R3pxo18619@raven.dms.auburn.edu> (message from Luc Teirlinck on Sat, 26 Mar 2005 21:51:59 -0600 (CST))

> Date: Sat, 26 Mar 2005 21:51:59 -0600 (CST)
> From: Luc Teirlinck <teirllm@dms.auburn.edu>
> 
> The recent addition of auto-revert-check-vc-info to man/files.texi is
> somewhat confusing.  It seems to suggest that the normal state of any
> buffer is to have version control info in the mode line.  Just
> mentioning VC without reference at that stage is confusing to a reader
> reading the manual back to front, because the concept of VC has not
> yet been introduced at that stage.

Indeed.

> What about the following small change?  I can install if desired.
> 
> ===File ~/man-files.texi-diff===============================
> *** files.texi	26 Mar 2005 09:57:37 -0600	1.101
> --- files.texi	26 Mar 2005 20:54:06 -0600	

How about moving the entire documentation of auto-revert-check-vc-info
to one of the sections that document VC?  The section about reverting
could then say something like

  xref{..., auto-revert-check-vc-info}, for Auto Revert peculiarities
  in buffers that visit files under version control.

  reply	other threads:[~2005-03-27 11:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27  3:51 man/files.texi Luc Teirlinck
2005-03-27 11:00 ` Eli Zaretskii [this message]
2005-03-30  3:14   ` man/files.texi Luc Teirlinck
2005-03-30  4:59     ` man/files.texi Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2005-03-22  3:06 man/files.texi Luc Teirlinck
2005-03-22 20:45 ` man/files.texi 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='01c532bc$Blat.v2.4$571d36e0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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).