unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Reopen bug 535: Problem with highlit regions on Linux virtual terminal
Date: Mon, 06 Apr 2009 18:30:28 +0900	[thread overview]
Message-ID: <buohc12gmdn.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <20090406090321.GA1645@muc.de> (Alan Mackenzie's message of "Mon,  6 Apr 2009 09:03:21 +0000")

Alan Mackenzie <acm@muc.de> writes:
> Yes, it is high-contrast and so on, in the same way that a foghorn at
> 200m is highly audible when you're trying to have a quiet conversation.

This a silly analogy, and bears no resemblance to the actual appearance,
which is quite nice in my opinion.

>> You seem to be right that it's suppressing most of the font-locking in
>> the highlighted area.
>
> It all but obliterates it.

... and yet, it simply _doesn't matter_, because highlighted regions are
_temporary_.  I use Emacs too, and I find the behavior very reasonable.

Font-Locking is nice, but it's very much secondary information, and
suppressing some of it when selecting a region (when your attention is
focused on the region), is just not a big deal -- indeed, I didn't even
_notice_ that font-locking colors were suppressed by the region on a tty
until you mentioned it!

>It obliterates hi-lock mode entirely.  I
> think it does this in GUI environments too.

Yes, because hi-lock uses the background.  This is probably not
particularly important.

> A blaring foghorn is temporary too.

... which is quite irrelevant, since your "foghorn" analogy is not
accurate; arguing by means of poor analogies is not useful.

> When I start Emacs 23 -Q, all of my buffers (loaded by desktop) are
> foghorned - I find Emacs in this state unusable.

All of your buffers have activated  regions when Emacs starts?

If so, _that_ sounds like a bug (so please try to send a test case);
needless to say, I think, I do not see this behavior.

> I agree with the logic here.  Region highlighting is incompatible with
> font lock and hi-lock.  Do you think that turning off font lock by
> default might be a good solution?

Of course not, since as far as I can see, there isn't actually any
problem.

It seems pretty obvious to me that all of this is much more a matter of
taste than anything else.  You have made your opinion on the matter very
clear, repeatedly.  The Emacs maintainers have made their best judgement
as to what the majority of Emacs users will prefer.  You know how to
turn off the highlighting.

-Miles

-- 
"Whatever you do will be insignificant, but it is very important that
 you do it."  Mahatma Gandhi




  reply	other threads:[~2009-04-06  9:30 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 [this message]
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
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=buohc12gmdn.fsf@dhlpc061.dev.necel.com \
    --to=miles@gnu.org \
    --cc=acm@muc.de \
    --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).