From: john muhl <email@johnmuhl.mx>
To: Eli Zaretskii <eliz@gnu.org>, chad <yandros@gmail.com>
Cc: EMACS development team <emacs-devel@gnu.org>
Subject: Re: Variable pitch text filling
Date: Wed, 01 Dec 2021 12:14:07 -0600 [thread overview]
Message-ID: <1936048bd654a25b405e871fa75c2b3e400785fd.camel@johnmuhl.mx> (raw)
In-Reply-To: <018F05D6-2D20-4457-A8CA-1ED6A42D8634@gnu.org>
On Wed, 2021-12-01 at 08:52 +0200, Eli Zaretskii wrote:
> On December 1, 2021 7:39:42 AM GMT+02:00, chad <yandros@gmail.com>
> wrote:
> > On Tue, Nov 30, 2021 at 9:32 PM Eli Zaretskii <eliz@gnu.org>
> > wrote:
> >
> > > [...] a display spec that would enlarge the pixel width of every
> > > character
> > > with that display property by some number of pixels. The
> > > display spec can
> > > be called char-width.
> > >
> >
> > I know that the two great problems are naming, cache invalidation,
> > and
> > off-by-one errors, but in case it helps: if I understand the
> > concept
> > correctly, it's very close to what typesetting calls "tracking".
>
> Emacs users are not professional typographers, so something like
> "tracking" will confuse rather than help. We should use "spacing"
> or somesuch.
>
Some of us are (of course we don't use Emacs for our jobs but for all
the other stuff it is good at).
Eli is right that Emacs using terms like tracking (etc) would be more
confusing than inventing something; even (maybe especially) to those
with a background in typography since the likelihood of it doing what
we expect is probably slim.
"char-spacing" lines up well with "line-spacing".
next prev parent reply other threads:[~2021-12-01 18:14 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 14:45 Variable pitch text filling Lars Ingebrigtsen
2021-11-26 15:04 ` Eli Zaretskii
2021-11-26 15:10 ` Lars Ingebrigtsen
2021-11-26 16:22 ` Eli Zaretskii
2021-11-26 17:03 ` Stefan Monnier
2021-11-27 7:12 ` Lars Ingebrigtsen
2021-11-27 7:43 ` Eli Zaretskii
2021-11-27 8:04 ` Lars Ingebrigtsen
2021-11-27 8:35 ` Eli Zaretskii
2021-11-27 14:28 ` Lars Ingebrigtsen
2021-11-27 14:55 ` Eli Zaretskii
2021-11-27 19:36 ` Eli Zaretskii
2021-11-29 13:50 ` Lars Ingebrigtsen
2021-11-29 14:02 ` Eli Zaretskii
2021-11-29 15:09 ` Lars Ingebrigtsen
2021-11-29 15:20 ` Eli Zaretskii
2021-11-29 18:44 ` Lars Ingebrigtsen
2021-12-01 4:35 ` Lars Ingebrigtsen
2021-12-01 5:31 ` Eli Zaretskii
2021-12-01 5:38 ` Lars Ingebrigtsen
2021-12-01 12:28 ` Eli Zaretskii
2021-12-01 14:33 ` Lars Ingebrigtsen
2021-12-01 14:45 ` Eli Zaretskii
2021-12-01 15:10 ` Lars Ingebrigtsen
2021-12-01 16:42 ` Eli Zaretskii
2021-12-01 16:49 ` Lars Ingebrigtsen
2021-12-01 16:57 ` Eli Zaretskii
2021-12-01 17:02 ` Lars Ingebrigtsen
2021-12-01 17:22 ` Eli Zaretskii
2021-12-01 17:35 ` Lars Ingebrigtsen
2021-12-01 17:49 ` Eli Zaretskii
2021-12-01 17:52 ` Lars Ingebrigtsen
2021-12-01 17:56 ` Eli Zaretskii
2021-12-01 18:19 ` Lars Ingebrigtsen
2021-12-01 18:47 ` Eli Zaretskii
2021-12-01 18:52 ` Lars Ingebrigtsen
2021-12-01 19:15 ` Eli Zaretskii
2021-12-01 19:23 ` Lars Ingebrigtsen
2021-12-01 19:29 ` Eli Zaretskii
2021-12-01 19:34 ` Lars Ingebrigtsen
2021-12-01 19:58 ` Eli Zaretskii
2021-12-02 8:15 ` Lars Ingebrigtsen
2021-12-02 8:46 ` Eli Zaretskii
2021-12-02 8:56 ` Lars Ingebrigtsen
2021-12-02 9:34 ` Eli Zaretskii
2021-12-03 15:43 ` Lars Ingebrigtsen
2021-12-02 20:32 ` Jim Porter
2021-12-02 21:19 ` Stefan Kangas
2021-12-02 22:00 ` [External] : " Drew Adams
2021-12-02 22:32 ` Jim Porter
2021-12-03 7:08 ` Eli Zaretskii
2021-12-03 7:14 ` Po Lu
2021-12-03 18:15 ` Jim Porter
2021-12-03 18:53 ` Stefan Kangas
2021-12-03 0:41 ` Po Lu
2021-12-03 6:58 ` Eli Zaretskii
2021-12-03 15:45 ` Lars Ingebrigtsen
2021-12-01 19:30 ` Jim Porter
2021-12-02 17:53 ` Eli Zaretskii
2021-12-02 19:03 ` Yuan Fu
2021-12-02 19:38 ` Eli Zaretskii
2021-12-02 20:18 ` Eli Zaretskii
2021-12-03 8:10 ` Eli Zaretskii
2021-12-03 8:17 ` Feng Shu
2021-12-03 11:31 ` Eli Zaretskii
2021-12-03 11:55 ` Feng Shu
2021-12-03 12:23 ` Eli Zaretskii
2021-12-03 8:51 ` Feng Shu
2021-12-03 11:35 ` Eli Zaretskii
2021-12-03 11:44 ` Feng Shu
2021-12-03 11:52 ` Eli Zaretskii
2021-12-03 11:47 ` Feng Shu
2021-12-03 15:41 ` Lars Ingebrigtsen
2021-12-03 19:38 ` Eli Zaretskii
2021-12-04 0:35 ` Po Lu
2021-12-04 7:45 ` Eli Zaretskii
2021-12-04 5:41 ` Lars Ingebrigtsen
2021-12-04 8:02 ` Eli Zaretskii
2021-12-04 19:00 ` Lars Ingebrigtsen
2021-12-01 5:39 ` chad
2021-12-01 6:52 ` Eli Zaretskii
2021-12-01 6:59 ` Yuri Khan
2021-12-01 18:14 ` john muhl [this message]
2021-11-29 13:46 ` Lars Ingebrigtsen
2021-11-29 14:01 ` Eli Zaretskii
2021-11-29 14:09 ` Lars Ingebrigtsen
2021-11-29 14:14 ` Eli Zaretskii
2021-11-29 14:19 ` Lars Ingebrigtsen
2021-11-29 14:25 ` Eli Zaretskii
2021-11-29 14:27 ` Lars Ingebrigtsen
2021-11-29 18:44 ` Yuan Fu
2021-11-29 19:28 ` Eli Zaretskii
2021-11-29 20:15 ` Yuan Fu
2021-11-26 16:47 ` Yuan Fu
2021-12-01 17:07 ` Stefan Kangas
2021-12-01 17:26 ` Eli Zaretskii
2021-11-26 15:08 ` Ihor Radchenko
2021-11-26 15:11 ` Lars Ingebrigtsen
2021-11-30 1:09 ` 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
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=1936048bd654a25b405e871fa75c2b3e400785fd.camel@johnmuhl.mx \
--to=email@johnmuhl.mx \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yandros@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.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).