From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Reopen bug 535: Problem with highlit regions on Linux virtual terminal
Date: Wed, 08 Apr 2009 14:35:16 +0900 [thread overview]
Message-ID: <87y6ubhfmz.fsf@xemacs.org> (raw)
In-Reply-To: <20090407205509.GA3452@muc.de>
Alan Mackenzie writes:
> The cons in the marked line is of the mark and the variable
> `mark-active'. This variable doesn't have a coherent definition,
> but it causes the region to be highlit. It is "defined" as
>
> Non-nil means the mark and region are currently active in this
> buffer.
>
> As I have pointed out before, this is Humpty Dumpty language,
Not at all. Active regions and the terminology go back twenty years
or more. If the mark is non-nil, then the region exists. The region
may be active, in which case operations on the region will succeed, or
inactive, when such operations will fail.[1] In transient-mark-mode,
it is possible for the region to be inactive. Outside of transient-
mark-mode, the region is always active. (Or something like that,
that's how zmacs-regions works in XEmacs, transient-mark-mode has some
tiny differences that I never understood very well.)
It sounds to me like there's a bug in desktop.el[2], and maybe a lack of
documentation of active regions. But the term is well-defined.
Footnotes:
[1] This is the same terminology used for GUI elements. But I guess
you would say that the whole concept of "GUI" is a "category error".<wink>
[2] I guess, as you say, it should record and check for
transient-mark-mode before going ahead and highlighting regions.
Personally, I would prefer desktop to have an option such that mark
status is always reset across sessions.
next prev parent reply other threads:[~2009-04-08 5:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 23:05 Reopen bug 535: Problem with highlit regions on Linux virtual terminal Alan Mackenzie
2009-04-06 1:12 ` Miles Bader
2009-04-06 3:10 ` Chong Yidong
2009-04-06 9:36 ` Alan Mackenzie
2009-04-06 9:03 ` Alan Mackenzie
2009-04-06 9:30 ` Miles Bader
2009-04-06 12:52 ` Alan Mackenzie
2009-04-06 15:35 ` David De La Harpe Golden
2009-04-07 21:46 ` Alan Mackenzie
2009-04-07 20:55 ` Alan Mackenzie
2009-04-08 5:35 ` Stephen J. Turnbull [this message]
2009-04-08 8:13 ` Alan Mackenzie
2009-04-08 9:16 ` Eli Zaretskii
2009-04-08 9:26 ` Stephen J. Turnbull
2009-04-08 13:05 ` Alan Mackenzie
2009-04-08 14:44 ` Stephen J. Turnbull
2009-04-06 3:03 ` Chong Yidong
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=87y6ubhfmz.fsf@xemacs.org \
--to=stephen@xemacs.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=miles@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).