From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Sean Sieger <sean.sieger@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: buffer name face
Date: Sat, 19 Dec 2009 21:35:04 +0100 [thread overview]
Message-ID: <f7ccd24b0912191235g687fe927scefeab9cfcb33bf7@mail.gmail.com> (raw)
In-Reply-To: <AA00205A60E542CBA1B78D06E671CCBF@us.oracle.com>
On Sat, Dec 19, 2009 at 21:30, Drew Adams <drew.adams@oracle.com> wrote:
> Dunno about tty, but otherwise, customizing face `mode-line-buffer-id' should
> solve the problem.
Or you can do this, which is easier :-)
I use the other method because I do change also the length of the
buffer name, etc. i.e., I use "%b" instead of "%12b".
Juanma
next prev parent reply other threads:[~2009-12-19 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 19:57 buffer name face Sean Sieger
2009-12-19 20:30 ` Drew Adams
2009-12-19 20:35 ` Juanma Barranquero [this message]
2009-12-19 20:53 ` Sean Sieger
2009-12-19 20:33 ` Juanma Barranquero
2009-12-19 22:55 ` Peter Dyballa
2009-12-22 1:35 ` Sean Sieger
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=f7ccd24b0912191235g687fe927scefeab9cfcb33bf7@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sean.sieger@gmail.com \
/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).