unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Enclosing text in a box
Date: Wed, 16 Nov 2022 21:55:29 +0700	[thread overview]
Message-ID: <CAP_d_8U8DwsG2=f36yXUyzBvkyTcxy=rmkYuNyOr1KQGKeGXrQ@mail.gmail.com> (raw)
In-Reply-To: <83y1sbez2r.fsf@gnu.org>

On Wed, 16 Nov 2022 at 21:48, Eli Zaretskii <eliz@gnu.org> wrote:

> > > Using 'length' to measure the width of text on display is not
> > > reliable, because there are characters of different width.  It is
> > > better to use 'string-width' or 'string-pixel-width' instead.
> >
> > The next stumbling point is going to be “make-string does the wrong
> > thing when passed 17.237 as the count”, without an explanation as to
> > what the right thing would be. (I don’t know either.)
>
> Why would sane code call make-string with such an argument?

My train of thought was:

* OP uses ‘length’ to measure the text, and ‘make-string’ to build a box.
* You point out that this fails for non-monospace fonts, and suggest
measuring with ‘string-width’ or ‘string-pixel-width’.
* OP tries to measure in pixels, realizes one has to divide by the
width of a box drawing character. The division result turns out
fractional.



  parent reply	other threads:[~2022-11-16 14:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 12:47 Enclosing text in a box Heime
2022-11-16 13:07 ` Heime
2022-11-16 13:34   ` Alexis Roda
2022-11-16 13:58     ` Eli Zaretskii
2022-11-16 14:11       ` Yuri Khan
2022-11-16 14:20         ` Heime
2022-11-16 14:47         ` Eli Zaretskii
2022-11-16 14:51           ` Heime
2022-11-16 14:55             ` Emanuel Berg
2022-11-16 20:56               ` Emanuel Berg
2022-11-16 16:44             ` Eli Zaretskii
2022-11-16 16:48               ` Heime
2022-11-16 16:53                 ` Heime
2022-11-16 19:20                 ` Eli Zaretskii
2022-11-16 19:35                   ` Heime
2022-11-16 19:42                     ` Emanuel Berg
2022-11-16 21:01                       ` Heime
2022-11-16 20:00                     ` Eli Zaretskii
2022-11-16 20:55                       ` Emanuel Berg
2022-11-18 14:48                         ` Eli Zaretskii
2022-11-18 15:10                           ` tomas
2022-11-18 19:18                           ` Emanuel Berg
2022-11-16 21:04                       ` Emanuel Berg
2022-11-16 14:55           ` Yuri Khan [this message]
2022-11-16 15:06             ` Yuri Khan
2022-11-16 16:12               ` tomas
2022-11-16 16:43                 ` Heime
2022-11-17  6:43 ` Jean Louis
2022-11-17  6:57   ` Emanuel Berg
2022-11-18 19:11     ` Jean Louis
2022-11-21 12:53       ` Emanuel Berg
2022-11-18 16:20   ` [External] : " Drew Adams

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='CAP_d_8U8DwsG2=f36yXUyzBvkyTcxy=rmkYuNyOr1KQGKeGXrQ@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).