From: Eli Zaretskii <eliz@gnu.org>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Checking for loss of information on integer conversion
Date: Thu, 22 Feb 2018 19:01:22 +0200 [thread overview]
Message-ID: <83d10x557h.fsf@gnu.org> (raw)
In-Reply-To: <87zi41kmto.fsf@trurl.irif.fr> (message from Juliusz Chroboczek on Thu, 22 Feb 2018 17:31:47 +0100)
> From: Juliusz Chroboczek <jch@irif.fr>
> Date: Thu, 22 Feb 2018 17:31:47 +0100
>
> > However, I'd rather prioritize progress in computing horizontal
> > alignment and widths with variable-width fonts. That is something
> > we really need.
>
> I am tempted to argue that silently returning the wrong answer is a more
> serious (but admittedly less visible) issue than minor cosmetic limitations
> of the redisplay engine.
It's not a minor cosmetic limitation, it's a basic inability to line
up text displayed with a variable-pitch font. It makes Emacs look
ugly and basically unusable when variable-pitch fonts are used to
display program source code, formatted text, tables, etc. These are
all important and frequent use cases these days.
By contrast, silently returning a wrong result due to overflow is a
much more rare situation, especially since today 64-bit machines are
so ubiquitous.
next prev parent reply other threads:[~2018-02-22 17:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 1:27 Checking for loss of information on integer conversion Paul Eggert
[not found] ` <83y3jq9q4m.fsf@gnu.org>
2018-02-18 20:04 ` Paul Eggert
2018-02-18 20:24 ` Eli Zaretskii
2018-02-18 21:52 ` bug#30408: " Drew Adams
2018-02-18 22:31 ` Juliusz Chroboczek
2018-02-18 22:41 ` Stefan Monnier
2018-02-18 23:46 ` Juliusz Chroboczek
2018-02-19 1:47 ` Stefan Monnier
2018-02-19 2:22 ` Paul Eggert
2018-02-19 3:20 ` Drew Adams
2018-02-19 15:05 ` Richard Stallman
2018-02-22 16:31 ` Juliusz Chroboczek
2018-02-22 17:01 ` Eli Zaretskii [this message]
2018-02-22 19:31 ` Stefan Monnier
2018-02-23 9:49 ` Richard Stallman
2018-02-19 6:03 ` John Wiegley
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=83d10x557h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jch@irif.fr \
/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.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).