From: "Drew Adams" <drew.adams@oracle.com>
To: "Jason Rumney" <jasonrumney@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Emacs - Buffer List - Drop-Down-Menu
Date: Thu, 6 Dec 2007 10:53:57 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICIENFEBAA.drew.adams@oracle.com> (raw)
In-Reply-To: <1b21c8a6-1b00-423a-8a98-4c904c7e1a08@a39g2000pre.googlegroups.com>
> > BTW, this helps a lot with the organization, but it doesn't
> really respond
> > to the OP question about justification and alignment. I agree that the
> > alignment is not ideal.
>
> The alignment comes from the second nested format call in mouse-buffer-
> menu-alist. I think the intention is to align the flags and file name,
> but it also results in the buffer names being left padded, losing
> their left alignment. This looks completely messed up when the menus
> use a variable width font, as nothing ends up aligned.
>
> On Windows, the tab character can be used for alignment within the
> menu, xmenu.c seems to use spaces to align the key codes though, so it
> probably doesn't work cross-platform.
Yes. A variable-width font is what I see on Windows, by default - which is
good, IMO.
I think (so far) that the buffer name should just be flush left, and it
should be followed by a single space before the file name. That is, forget
about trying to align the file names. That is the best solution for a
variable-width font, IMO. Besides, there is no reason to align the file
names: they don't constitute a separate field or whatever here.
next prev parent reply other threads:[~2007-12-06 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4655.1196960992.18990.help-gnu-emacs@gnu.org>
2007-12-06 17:54 ` Emacs - Buffer List - Drop-Down-Menu Jason Rumney
2007-12-06 18:53 ` Drew Adams [this message]
2008-01-09 12:54 Will
2008-01-09 14:14 ` Jason Rumney
-- strict thread matches above, loose matches on Subject: below --
2007-12-06 15:00 Will
2007-12-06 16:37 ` Peter Dyballa
2007-12-06 17:08 ` Drew Adams
2007-12-06 17:28 ` Peter Dyballa
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=DNEMKBNJBGPAOPIJOOICIENFEBAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jasonrumney@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.
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.