From: David Kastrup <dak@gnu.org>
Cc: Juri Linkov <juri@jurta.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [rms@gnu.org: Re: mouse cannot be used in *grep* buffer if font-lock is turned off]
Date: Tue, 19 Oct 2004 22:59:43 +0200 [thread overview]
Message-ID: <x5pt3e8lvk.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20041019210656.2de3ff4b@pfdabpc.inhouse.start.de> (Daniel Pfeiffer's message of "Tue, 19 Oct 2004 21:06:56 +0200")
dapfy@t-online.de (Daniel Pfeiffer) writes:
> This sounds like a step further: font-lock without fonts, i.e. a
> property lock mode. Actually I can't for the life of me imagine why
> anybody would not want font-locking, even vi can do it nowadays. It
> adds so much legibility, I feel it should be on by default.
It _removes_ legibility since it decreases the already low contrast
(as compared to paper) of computer screens further. I don't work with
font lock at all and find it very distracting in addition to
unreadable.
That being said, I second that it should be on by default. I'll turn
it off first thing, but it is the kind of thing beginners expect.
However, we would need a command line option to turn it off, too, or
people with disabilities or screen readers might be unable to even
handle turning off the default fontification via customize.
> My oldish 500MHz P3 can handle it easily and I'm pretty sure I used
> without great penalty way back on my 100MHz box.
How often do you edit 1MB text files with complex patterns? That is
not unusual if you are preparing a book.
> An easy workaround for those who want it, is to customize the faces
> to default.
But there is no sense in forcing a heavy performance penalty if you
don't even see a thing.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-10-19 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 6:13 [rms@gnu.org: Re: mouse cannot be used in *grep* buffer if font-lock is turned off] Richard Stallman
2004-10-19 19:06 ` Daniel Pfeiffer
2004-10-19 19:43 ` Stefan Monnier
2004-10-21 1:45 ` Richard Stallman
2004-10-19 20:59 ` David Kastrup [this message]
2004-10-19 21:59 ` Daniel Pfeiffer
2004-10-19 22:39 ` David Kastrup
2004-10-20 7:07 ` Daniel Pfeiffer
2004-10-21 1:46 ` Richard Stallman
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=x5pt3e8lvk.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@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).