[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug#7771: 23.1; can't turn off font-lock-mode globally
From: |
K. Richard Pixley |
Subject: |
Re: bug#7771: 23.1; can't turn off font-lock-mode globally |
Date: |
Mon, 03 Jan 2011 10:33:46 -0800 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 |
On 20110103 00:13, Drew Adams wrote:
compile (and grep) require font-lock to work.
They did not used to require font locking. This is a regression, a feature
loss, if users are deprived of the Emacs `grep' and `compile' commands if they
simply turn off font-locking.
I concur. This is a sad regression.
The added benefit users get from font-lock should just be a plus, not a
requirement. With font-lock turned off we should just not show any font-lock
highlighting, nothing more.
As is, it's not a plus. It simply makes those commands difficult to
use. You have to switch to the buffer and manually turn font locking
off in them each time you create a pop up in order to view the pop up's
contents.
(I haven't tried to set up a mode-local hook to do it.)
Font lock was finally turned on by default globally (a change I support
strongly). But that should just be the _default_ behavior. Font lock should
not be required in order to compile or grep.
I think it could be a reasonable default if it were visible in all
cases. Since it's clearly not, it is, in my opinion, premature to turn
on by default.
New users and people who are ignorant of the font lock system should not
be presented with illegible screens nor be forced to learn the details
of this system simply in order to use emacs.
IMO, that's intolerable and extremely embarrassing. I can't very well
advocate for emacs use when this is such a common occurrence.
As the person who first added regexp highlighting to the Emacs `grep' command
(my version), I know it is a definite plus. But the implementation of the
`grep' and `compile' commands should not _require_ font locking for users to be
able to use the commands for their most important purpose.
Again, I strongly concur.
As a model, assume for a moment that "font-lock" meant "white characters
on a white background".
--rich
- Re: bug#7771: 23.1; can't turn off font-lock-mode globally, (continued)
- bug#7771: 23.1; can't turn off font-lock-mode globally, Drew Adams, 2011/01/03
- bug#7771: 23.1; can't turn off font-lock-mode globally, Eli Zaretskii, 2011/01/03
- bug#7771: 23.1; can't turn off font-lock-mode globally, Drew Adams, 2011/01/03
- bug#7771: 23.1; can't turn off font-lock-mode globally, Eli Zaretskii, 2011/01/03
- bug#7771: 23.1; can't turn off font-lock-mode globally, Drew Adams, 2011/01/03
- bug#7771: 23.1; can't turn off font-lock-mode globally, Eli Zaretskii, 2011/01/03
- Message not available
- Re: bug#7771: 23.1; can't turn off font-lock-mode globally, K. Richard Pixley, 2011/01/03
- Message not available
- Re: bug#7771: 23.1; can't turn off font-lock-mode globally,
K. Richard Pixley <=
- Message not available
- Re: bug#7771: 23.1; can't turn off font-lock-mode globally, K. Richard Pixley, 2011/01/02
bug#7771: 23.1; can't turn off font-lock-mode globally, K. Richard Pixley, 2011/01/02
bug#7771: 23.1; can't turn off font-lock-mode globally, Drew Adams, 2011/01/03
bug#7771: 23.1; can't turn off font-lock-mode globally, Lennart Borgman, 2011/01/03
bug#7771: 23.1; can't turn off font-lock-mode globally, Drew Adams, 2011/01/03
bug#7771: 23.1; can't turn off font-lock-mode globally, Lennart Borgman, 2011/01/03