unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: Re: Misleading --help text
Date: Wed, 27 Jun 2007 23:25:48 -0600	[thread overview]
Message-ID: <f5vgor$7nb$1@sea.gmane.org> (raw)
In-Reply-To: <alpine.DEB.0.99.0706271054000.31832@localhost.localdomain>

Reuben Thomas wrote:
> I'm not sure whether this applies to current CVS (sorry, I only use 
> emacs from my GNU/Linux distribution), but emacs 21.4 --help says:
> 
> Action options:
> 
> FILE            visit FILE using find-file
> +LINE FILE        visit FILE using find-file, then go to line LINE
> +LINE:COLUMN FILE    visit FILE using find-file, then go to line LINE,
>                 column COLUMN
> 
> Reading this, I would expect that
> 
> emacs +5 +5 foo
> 
> would visit a file called "+5", then go to line 5, and also visit a file 
> called "foo" but it doesn't, it visits "foo", then goes to line 5. 
> That's fine by me, but it does mean the documentation is misleading.
> 
> I suggest the following stanza instead:
> 
> Action options:
> 
> FILE            visit FILE using find-file
> +LINE            go to line LINE in the next file visited
> +LINE:COLUMN         go to line LINE, column COLUMN in the next file
>                 visited
> 
> Then it's fairly obvious that if you give two successive +LINE[:COLUMN] 
> options, the second will override the first.

Actually, I think it's misleading to mention visited files: the +LINE
and +LINE:COLUMN options act within the current buffer whether it is
visiting a file or not.

-- 
Kevin Rodgers
Denver, Colorado, USA

  reply	other threads:[~2007-06-28  5:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  9:58 Misleading --help text Reuben Thomas
2007-06-28  5:25 ` Kevin Rodgers [this message]
2007-06-28  9:04   ` Andreas Schwab
2007-06-29  2:17     ` Kevin Rodgers

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='f5vgor$7nb$1@sea.gmane.org' \
    --to=kevin.d.rodgers@gmail.com \
    --cc=bug-gnu-emacs@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).