From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: juri@jurta.org, emacs-devel@gnu.org, storm@cua.dk
Subject: Re: Emphasize the character to be typed next in *Completions*
Date: 30 Mar 2004 20:32:03 -0500 [thread overview]
Message-ID: <m1u105953g.fsf-monnier+emacs@empanada.iro.umontreal.ca> (raw)
In-Reply-To: <E1B8Tvj-0007ij-Lr@fencepost.gnu.org>
> I haven't used it in a while now), but that was not my point: my point
> is that buffer-local faces are useful for user customization and as
> long as we don't really support them, we should try to keep using the
> "face-variables" indirection used by font-lock: those variables are
> not obsolete.
> I agree, as regards font lock faces. However, when a face is used
> only in a specific mode, then this motivation for customizing it would
> be rare.
I don't see any reason why similar issues wouldn't come up.
You might want to use different faces for "dired on /etc" than "dired on
/home/foo".
Other examples: header-line face, default face, ... I'd love to have
different settings for those in different buffers (or at least in different
modes).
Stefan
next prev parent reply other threads:[~2004-03-31 1:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040322053942.03A2467DC4@imf.math.ku.dk>
2004-03-22 9:31 ` Emphasize the character to be typed next in *Completions* Lars Hansen
2004-03-22 9:48 ` Lars Hansen
2004-03-22 9:55 ` Masatake YAMATO
2004-03-22 11:16 ` Lars Hansen
2004-03-22 11:37 ` David Kastrup
2004-03-22 12:02 ` Lars Hansen
2004-03-23 3:04 ` Richard Stallman
2004-03-23 10:43 ` Masatake YAMATO
2004-03-23 15:09 ` Kim F. Storm
2004-03-23 15:07 ` Stefan Monnier
2004-03-24 0:07 ` Kim F. Storm
2004-03-24 2:36 ` Masatake YAMATO
2004-03-24 5:53 ` Miles Bader
2004-03-24 10:38 ` Kim F. Storm
2004-03-24 5:34 ` Richard Stallman
2004-03-24 10:44 ` Kim F. Storm
2004-03-23 14:29 ` Robert J. Chassell
2004-03-23 18:38 ` Juri Linkov
2004-03-23 21:27 ` Robert J. Chassell
2004-03-25 21:57 ` Juri Linkov
2004-03-23 17:55 ` Juri Linkov
2004-03-23 22:44 ` David Kastrup
2004-03-25 21:31 ` Juri Linkov
2004-03-25 2:00 ` Richard Stallman
2004-03-25 10:04 ` Kim F. Storm
2004-03-27 5:52 ` Richard Stallman
2004-03-27 22:24 ` Stefan Monnier
2004-03-28 4:25 ` Richard Stallman
2004-03-28 17:35 ` Stefan Monnier
2004-03-29 20:56 ` Richard Stallman
2004-03-29 21:24 ` Stefan Monnier
2004-03-30 5:58 ` Eli Zaretskii
2004-03-30 11:14 ` Juri Linkov
2004-03-31 0:50 ` Richard Stallman
2004-03-31 1:32 ` Stefan Monnier [this message]
2004-03-31 23:02 ` Miles Bader
[not found] <20040325063231.137606B7A5@imf.math.ku.dk>
2004-03-25 11:32 ` Lars Hansen
2004-03-25 16:03 ` Masatake YAMATO
2004-04-08 16:30 ` Glenn Morris
2004-04-11 18:12 ` Masatake YAMATO
2004-04-13 17:45 ` Richard Stallman
2004-04-14 3:16 ` Masatake YAMATO
2004-04-15 18:25 ` Juri Linkov
2004-04-16 8:59 ` Masatake YAMATO
2004-03-21 15:13 Masatake YAMATO
2004-03-22 5:25 ` Richard Stallman
2004-03-22 18:29 ` Tak Ota
2004-03-23 0:14 ` Kim F. Storm
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=m1u105953g.fsf-monnier+emacs@empanada.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=storm@cua.dk \
/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.