unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "rgb" <rbielaws@i1.net>
To: help-gnu-emacs@gnu.org
Subject: Re: *background color*
Date: 12 Feb 2007 05:36:32 -0800	[thread overview]
Message-ID: <1171287392.073501.191390@m58g2000cwm.googlegroups.com> (raw)
In-Reply-To: <uk5ynltiq.fsf@gmail.com>

On Feb 12, 1:33 am, Mathias Dahl <brakjol...@gmail.com> wrote:
> A Soare <alins...@voila.fr> writes:
> > Why is it not possible to associate a background color to a buffer,
> > not just to a frame? It could be possible to insert such a feature
> > in future?
>
> Interesting idea! I might actually use such a feature. One could have
> different background color on important buffer, to quickly recognize
> them when swithing/cycling/whatever buffers or when having several
> frames or windows.
>
> I saw Stefan's reply, let's hope for Emacs 23...
>
> I wonder if it could be implemented using overlays in the meantime, or
> maybe that would be slow? Or impossible.

If you care to go thru the trouble, Stefan mentioned in a
recent thread

"
> The stock font-lock face names (like font-lock-builtin-face, etc) all
> are symbols that point to themselves (or something like that) and so
> are more-or-less self-quoting.
...
The purpose of those vars is not just to make it "self-quoting", but
rather
to be able to change the face in some buffers, by making the variable
local
to that buffer."

So the capabilities appear to be there.  The mechanics to issue all
the make-local-variable commands would then be whats missing.
Perhaps some tweeks to color theme could be made to issue them?

Or maybe non-stock faces are often not implemented in the necessary
way?

  reply	other threads:[~2007-02-12 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4349.1171217714.2155.help-gnu-emacs@gnu.org>
2007-02-11 21:26 ` *background color* Stefan Monnier
2007-02-12  7:33 ` Mathias Dahl
2007-02-12 13:36   ` rgb [this message]
2007-02-11 18:15 A Soare

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=1171287392.073501.191390@m58g2000cwm.googlegroups.com \
    --to=rbielaws@i1.net \
    --cc=help-gnu-emacs@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.
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).