From: dapfy@t-online.de (Daniel Pfeiffer)
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 23:59:01 +0200 [thread overview]
Message-ID: <20041019235901.4c13c969@pfdabpc.inhouse.start.de> (raw)
In-Reply-To: <x5pt3e8lvk.fsf@lola.goethe.zz>
Moin David,
David Kastrup <dak@gnu.org> skribis:
> 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.
That's a good point! They might profit from the early black & white font-lock
style (like I try to keep my setup as far as possible -- colours always remind
me of M$-Windoze). Maybe the customizability of faces should evolve more in
the CSS direction, with accessability, reader and printer styles.
> > 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.
I too am not sure about the argument of always running this if you get no
benefit. As for compilation and grep the benefit is clear. Font-lock has
rather good parsing capabilities, and these modes need that. The gaudiness is
a side effect really.
coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer
--
lerne / learn / apprends / lär dig / ucz się Esperanto:
http://lernu.net/
next prev parent reply other threads:[~2004-10-19 21: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
2004-10-19 21:59 ` Daniel Pfeiffer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041019235901.4c13c969@pfdabpc.inhouse.start.de \
--to=dapfy@t-online.de \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=occitan@esperanto.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 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.