From: Drew Adams <drew.adams@oracle.com>
To: 16513@debbugs.gnu.org
Subject: bug#16513: 24.3.50; doc string of `use-empty-active-region'
Date: Mon, 20 Jan 2014 20:20:18 -0800 (PST) [thread overview]
Message-ID: <8da28f3d-e5ec-48d4-9407-377ec2afbc6c@default> (raw)
1. Remove the last part: ", and on the text near point otherwise." It
is inappropriate and wrong. (This is the reason I filed this bug.)
This is about commands that act differently depending on whether or
not the region is active. Do not say anything about what the behavior
must be in either case: active or inactive. Certainly, do not claim
that when the region is inactive such commands act on the text near
point. That is pure fantasy.
2. Simplify the following, which suggests that having an active region
is somehow different from having an active mark:
"If non-nil, region-aware commands treat the region as active as long as
the mark is active, even if the region is empty." Just say: "If
non-nil, region-aware commands treat an active region as such, even if
it is empty."
3. Do not speak of "regions", as it can confuse people. In any given
buffer at any moment there is only one region. "The region" makes
sense; "regions" does not, unless you are talking about multiple
buffers.
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2014-01-17 on ODIEONE
Bzr revision: 116059 michael.albinus@gmx.de-20140117182409-gz695p2c951idlee
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
CPPFLAGS=-Ic:/Devel/emacs/include'
next reply other threads:[~2014-01-21 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 4:20 Drew Adams [this message]
2014-02-10 5:34 ` bug#16513: 24.3.50; doc string of `use-empty-active-region' Lars Ingebrigtsen
2016-04-29 15:54 ` Lars Ingebrigtsen
2016-04-29 18:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8da28f3d-e5ec-48d4-9407-377ec2afbc6c@default \
--to=drew.adams@oracle.com \
--cc=16513@debbugs.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 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.