unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: Francis Litterio <franl@world.std.com>, emacs-devel@gnu.org
Subject: Re: PATCH: Don't mix faces in Buffer-menu header when Buffer-menu-use-header is nil
Date: Tue, 15 Jun 2004 21:34:56 -0400	[thread overview]
Message-ID: <20040616013456.GA16329@fencepost> (raw)
In-Reply-To: <87d640lu23.fsf@mail.jurta.org>

On Tue, Jun 15, 2004 at 06:28:19PM +0300, Juri Linkov wrote:
> Moreover, I don't understand why displaying text in the header line
> needs special treatment by adding the space and using special fonts?
> Why the header line can't start at the left fringe?  The header line
> is often used as a fixed part of the buffer that doesn't scroll,
> so it makes sense to line it up with the buffer and to use the same
> font in which its buffer is displayed.

I don't the space is necessary -- Kim's recent changes should do that in a
better way -- but I presume the use of the fixed-width font is so that the
single-letter headers for the first three `columns' _exactly_ line up with
the corresponding text.  Those headers are already kind of cryptic, so that
is important for anyone that uses a variable-pitch header face (which is not
uncommon).

The current solution is kind of bad be because the `fixed-pitch' face is
often jarringly different from the default face, but in practice it's
probably good enough for now.

For future releases I intend to add `attribute filtered' face-inheritance
(something which Stefan has also mentioned), which should make it easer to
get a face that just inherits the default face's font/size without screwing
up other attributes.

-Miles
-- 
Run away!  Run away!

      reply	other threads:[~2004-06-16  1:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 18:10 PATCH: Don't mix faces in Buffer-menu header when Buffer-menu-use-header is nil Francis Litterio
2004-06-10 20:15 ` Francis Litterio
2004-06-15 15:28   ` Juri Linkov
2004-06-16  1:34     ` Miles Bader [this message]

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=20040616013456.GA16329@fencepost \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=franl@world.std.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.
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).