all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 10023@debbugs.gnu.org
Subject: bug#10023: 24.0.91; `mark-whole-buffer' doesn't always "mark the whole buffer"
Date: Sat, 12 Nov 2011 14:30:09 -0500	[thread overview]
Message-ID: <kw7h3516m6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAH8Pv0gDxP+G0DSvns8w8gNmhkt_58FSWvbLOU9vTajzReykjg@mail.gmail.com> (Dani Moncayo's message of "Sat, 12 Nov 2011 12:51:55 +0100")

Dani Moncayo wrote:

> The `mark-whole-buffer' command, when invoked from a narrowed buffer,
> doesn't mark the whole buffer (like its name, docstring and the manual
> say) but only the narrowed portion.
>
> Therefore, I think that:
> * The docstring and the manual should explain this use-case.
> * The command name could be renamed to just `mark-buffer', since the
> "whole" part is specially unfortunate.

From the Emacs manual on narrowing:

    When you have narrowed down to a part of the buffer, that part
    appears to be all there is.  You can't see the rest, you can't move
    into it (motion commands won't go outside the accessible part), you
    can't change it in any way.

This is a common concept that I don't think needs to be explained in
the doc of every command that it might effect. `mark-whole-buffer'
definitely does not need to be renamed.

Narrow-to-region is a disabled command; you get a notice about this kind
of thing when you invoke it.





  reply	other threads:[~2011-11-12 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12 11:51 bug#10023: 24.0.91; `mark-whole-buffer' doesn't always "mark the whole buffer" Dani Moncayo
2011-11-12 19:30 ` Glenn Morris [this message]
2011-11-12 20:53   ` Dani Moncayo
2011-11-15  0:39     ` Glenn Morris

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=kw7h3516m6.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=10023@debbugs.gnu.org \
    --cc=dmoncayo@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.