From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 12866@debbugs.gnu.org
Subject: bug#12866: 24.3.50; (elisp) `%-Constructs': padded with spaces to the right or left?
Date: Mon, 12 Nov 2012 17:45:24 +0200 [thread overview]
Message-ID: <83mwymx1t7.fsf@gnu.org> (raw)
In-Reply-To: <0CF50E0E288748AEA7AAD1F837E5EE36@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <12866@debbugs.gnu.org>
> Date: Sun, 11 Nov 2012 19:45:33 -0800
>
> > > (set (make-local-variable 'mode-line-position) '("%40l"))
> > >
> > > It seems to me that that pads the line number with spaces
> > > on the left, not the right. But perhaps I'm missing something.
> >
> > I think string formats, like %s, are padded to the right. IOW, the
> > padding behaves like in C.
>
> Dunno what that means. Are you drawing a contrast with what you think? Or with
> %s (subprocess status) vs %l for mode-line constructs? Something else?
>
> The padding for %l (in the mode line) is what this bug report is about. AFAICT,
> the padding is put on the left. Do you see something different from that?
The bug report contrasted the documentation with what the code does.
I pointed out that the documentation is only correct as far as string
formatting is concerned, but is incorrect wrt numerical formats, which
indeed pad on the left. Hopefully, this will help you know the truth,
and will help someone to fix the documentation.
next prev parent reply other threads:[~2012-11-12 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 0:35 bug#12866: 24.3.50; (elisp) `%-Constructs': padded with spaces to the right or left? Drew Adams
2012-11-12 0:44 ` Juanma Barranquero
2012-11-12 1:12 ` Drew Adams
2012-11-12 1:27 ` Juanma Barranquero
2012-11-12 2:29 ` Drew Adams
2012-11-12 3:38 ` Eli Zaretskii
2012-11-12 3:45 ` Drew Adams
2012-11-12 15:45 ` Eli Zaretskii [this message]
2012-11-12 15:55 ` Drew Adams
2012-11-23 8:33 ` Chong Yidong
2012-11-12 20:37 ` Andreas Schwab
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=83mwymx1t7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12866@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.