unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: casouri@gmail.com, 38485@debbugs.gnu.org
Subject: bug#38485: Customizing glyph widths
Date: Wed, 4 Dec 2019 15:55:38 -0500	[thread overview]
Message-ID: <ad220d06-053b-aa24-9ea4-8b26d6317fb7@gmail.com> (raw)
In-Reply-To: <83r21khquw.fsf@gnu.org>

On 2019-12-04 13:45, Eli Zaretskii wrote:
>> Cc: casouri@gmail.com, 38485@debbugs.gnu.org
>> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
>> Date: Wed, 4 Dec 2019 13:14:19 -0500
>>
>>>> I'm thinking something like `:display-width 3' or maybe `display-width "~~>"' (the former would mean "as wide as three spaces in the default font"; the later, "as wide as `~~>' in the default font").
>>>> These properties would be applied by prettify-symbols-mode in addition to composition.
>>>
>>> I don't understand why would prettify-symbols-mode want to do this via
>>> a text property, instead of via a buffer-local variable.
>>
>> Would this buffer-local variable be an alist mapping each character to the desired width?
> 
> No, it will simply make each prettified symbol take up the same width
> as the original characters of the symbol that were composed.  Isn't
> that what everyone would want, and want for _all_ prettified symbols?

Another example: the nameless-mode pacakge uses prettification to display the name of the current file as :, so that in foo-bar.el the symbol foo-bar-xyz displays as :xyz (with a different color for the colon) to shorten lines and improve readability.  Widening this ':' would defeat the purpose of that package.

Clément.





  parent reply	other threads:[~2019-12-04 20:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04  4:22 bug#38485: Customizing glyph widths Clément Pit-Claudel
2019-12-04 15:52 ` Eli Zaretskii
2019-12-04 16:57   ` Clément Pit-Claudel
2019-12-04 17:05     ` Eli Zaretskii
2019-12-04 18:14       ` Clément Pit-Claudel
2019-12-04 18:45         ` Eli Zaretskii
2019-12-04 20:53           ` Clément Pit-Claudel
2019-12-05  3:34             ` Eli Zaretskii
2019-12-05 14:26               ` Clément Pit-Claudel
2019-12-05 15:19                 ` Eli Zaretskii
2019-12-05 19:50                   ` Clément Pit-Claudel
2019-12-05 20:06                     ` Eli Zaretskii
2019-12-05 20:53                       ` Clément Pit-Claudel
2019-12-06  4:15                         ` bug#38485: "prettified" symbols Richard Stallman
2019-12-06  5:51                           ` Clément Pit-Claudel
2019-12-06  7:58                           ` Eli Zaretskii
2019-12-07  4:42                             ` Richard Stallman
2019-12-04 20:55           ` Clément Pit-Claudel [this message]
2019-12-05  3:36             ` bug#38485: Customizing glyph widths Eli Zaretskii
2019-12-05 14:29               ` Clément Pit-Claudel
2019-12-05  3:57   ` Yuan Fu

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=ad220d06-053b-aa24-9ea4-8b26d6317fb7@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=38485@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=eliz@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.
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).