From: Jason Rumney <jasonr@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 12067@debbugs.gnu.org
Subject: bug#12067: 24.1; improper menu formatting with multiple \t chars
Date: Sat, 28 Jul 2012 00:19:54 +0800 [thread overview]
Message-ID: <87lii5yy51.fsf@gnu.org> (raw)
In-Reply-To: <8A9A3FFCBD5F433094079C3662EB3314@us.oracle.com> (Drew Adams's message of "Fri, 27 Jul 2012 08:06:11 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
>> > It turns out that using only a single \t does the right
>> > thing in terms of alignment in this case. But shouldn't
>> > multiple \t's let you tab (indent) further, as they do
>> > in text buffers, doc strings, etc.? And
>> > presumably \t\t should not draw a rectangle, in any case.
>>
>> No. A menu is not a buffer.
>
> No one said it is.
You seem to be requesting it to act like one above.
In Windows menus, a tab character is a not valid printing character,
hence is drawn as a rectangle. An exception is that if one, and only
one, tab character appears in a menu string, it is used as a separator
to separate the menu text (left aligned in most locales) from the key
shortcut (right aligned in those locales).
YMMV with menus on other platforms however.
next prev parent reply other threads:[~2012-07-27 16:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 6:49 bug#12067: 24.1; improper menu formatting with multiple \t chars Drew Adams
2012-07-27 14:53 ` Jason Rumney
2012-07-27 15:06 ` Drew Adams
2012-07-27 16:19 ` Jason Rumney [this message]
2012-07-27 16:33 ` Drew Adams
2012-07-27 15:49 ` Eli Zaretskii
2012-07-27 16:24 ` Drew Adams
2012-07-27 20:24 ` Michael Heerdegen
2012-07-28 6:56 ` Eli Zaretskii
2012-07-28 12:51 ` Michael Heerdegen
2012-07-28 19:58 ` Eli Zaretskii
2012-07-28 20:10 ` Drew Adams
2012-07-29 2:49 ` Eli Zaretskii
2014-02-09 3:29 ` Lars Ingebrigtsen
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=87lii5yy51.fsf@gnu.org \
--to=jasonr@gnu.org \
--cc=12067@debbugs.gnu.org \
--cc=drew.adams@oracle.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.