From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: shingo.fg8@gmail.com, 48148@debbugs.gnu.org
Subject: bug#48148: 27.2; ox-ascii breaks TITLE line wrongly when 2 width char is used
Date: Sun, 02 May 2021 12:11:41 +0300 [thread overview]
Message-ID: <8335v58ppu.fsf@gnu.org> (raw)
In-Reply-To: <87h7jla6ih.fsf@nicolasgoaziou.fr> (message from Nicolas Goaziou on Sun, 02 May 2021 10:23:34 +0200)
> From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> Cc: Shingo Tanaka <shingo.fg8@gmail.com>, 48148@debbugs.gnu.org
> Date: Sun, 02 May 2021 10:23:34 +0200
>
> > The accurate method of lining up in these cases is to use
> > window-text-pixel-size instead. That function will return the exact
> > width of a string as it will displayed, in pixels, because it uses the
> > same code as the display engine.
>
> Would you mind giving an example about `window-text-pixel-size' usage in
> this situation?
I'm not sure what kind of example is necessary. How about if you ask
specific questions about the arguments of that function which you
don't understand clearly how to use?
> AFAIU, `window-text-pixel-size' returns the size of the window
No, it returns the size of _text_ when displayed in a window.
> Note that `text-width' in the code above is not related to the width
> of the window, but is a maximum number of allowed characters on a
> line.
I didn't mean text-width, I meant the use of string-width: it should
be replaced by a call to window-text-pixel-size.
next prev parent reply other threads:[~2021-05-02 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h7jm2es2.wl-shingo.fg8@gmail.com>
2021-05-02 7:03 ` bug#48148: 27.2; ox-ascii breaks TITLE line wrongly when 2 width char is used Eli Zaretskii
2021-05-02 8:23 ` Nicolas Goaziou
2021-05-02 9:11 ` Eli Zaretskii [this message]
2021-05-02 11:33 ` Shingo Tanaka
2021-05-02 12:43 ` Eli Zaretskii
2021-05-02 12:18 ` Nicolas Goaziou
2021-05-02 12:48 ` Eli Zaretskii
2021-05-02 15:56 ` Nicolas Goaziou
2021-05-02 16:11 ` Eli Zaretskii
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8335v58ppu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48148@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=shingo.fg8@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).