From: storm@cua.dk (Kim F. Storm)
Cc: David Kastrup <dak@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Buffer-local faces
Date: 04 May 2004 10:40:05 +0200 [thread overview]
Message-ID: <m3k6zsbn6i.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20040504095707.GA9691@fencepost>
Miles Bader <miles@gnu.org> writes:
> On Tue, May 04, 2004 at 11:18:21AM +0200, David Kastrup wrote:
> > I am uncomfortable about the whole change. And the reason has to do
> > with the feature freeze. Now you may argue that the change is not so
> > intrusive as to be likely to trigger new bugs, but that's beside the
> > point.
>
> I said nothing about the feature freeze. I did not post my patch to `sneak
> in under the wire' of the freeze, I posted it because I (1) happened to have
> been working on it, and (2) came up with something nice.
Again, feature freeze means that people should switch attention away
from developing new features -- but that doesn't exclude that we
can add things (for a short period) that people have already been
working on before the freeze.
If those new features are useful (and the changes are not too
intrusive), I would prefer to get them into 21.5 rather than wait for
22.x to come out (history shows that major emacs releases don't happen
everyday :-| )
I think Miles' approach is quite elegant, as it solves a real problem
in a simple and IMO clean way. There may be cases that are not
handled by this approach, but it is still a whole lot better than
having no approach at all.
And even if we find a better or more general approach later on, I
believe it can co-exist with Miles' code, as that code works on a
pretty low level (implementation-wise).
Of course, there may be things that don't work with Miles' patch (fringe
faces may be one case -- haven't checked), but it could be fixed during
pretest if deemed necessary.
I would love to have this feature.
> I don't think it's a kludge at all, it's an elegant way of leveraging emacs'
> very flexible variable mechanism to achieve the goal -- not only is it almost
> trivial to implement, but it would seem to fit very well with the way emacs
> modes work.
I don't think it is a kludge either.
>
> Perhaps xemacs has a better way of doing it, I don't know -- I'm afraid I'm
> not familiar with xemacs in recent years.
As a true GNU emacs evangelist, I've never been familiar with xemacs...
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-05-04 8:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 13:03 Buffer-local faces Miles Bader
2004-05-03 13:33 ` Miles Bader
2004-05-03 22:20 ` Richard Stallman
2004-05-03 23:19 ` Miles Bader
2004-05-04 5:56 ` Eli Zaretskii
2004-05-04 13:27 ` Stefan Monnier
2004-05-04 20:07 ` Richard Stallman
2004-05-03 22:42 ` Stefan Monnier
2004-05-03 23:27 ` Miles Bader
2004-05-04 5:45 ` Juri Linkov
2004-05-04 8:22 ` Miles Bader
2004-05-04 13:37 ` Stefan Monnier
2004-05-04 14:02 ` Miles Bader
2004-05-04 14:10 ` Stefan Monnier
2004-05-05 20:20 ` Richard Stallman
2004-05-05 20:20 ` Richard Stallman
2004-05-06 13:55 ` Miles Bader
2004-05-05 20:20 ` Richard Stallman
2004-05-05 20:43 ` Stefan Monnier
2004-05-05 8:09 ` Richard Stallman
2004-05-04 20:08 ` Richard Stallman
2004-05-04 9:18 ` David Kastrup
2004-05-04 9:57 ` Miles Bader
2004-05-04 8:40 ` Kim F. Storm [this message]
2004-05-04 9:59 ` Juri Linkov
2004-05-05 20:20 ` 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=m3k6zsbn6i.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).