From: Eli Zaretskii <eliz@gnu.org>
To: "Paul W. Rankin" <hello@paulwrankin.com>
Cc: emacs-devel@gnu.org
Subject: Re: Making vertical-border char defcustom?
Date: Tue, 21 Jan 2020 17:30:39 +0200 [thread overview]
Message-ID: <83lfq0x1wg.fsf@gnu.org> (raw)
In-Reply-To: <03C83895-EF8F-4379-B41F-EF33926F376F@paulwrankin.com> (hello@paulwrankin.com)
> From: "Paul W. Rankin" <hello@paulwrankin.com>
> Date: Tue, 21 Jan 2020 16:25:52 +1000
> Cc: emacs-devel@gnu.org
>
> On 21 Jan 2020, at 4:08 am, Eli Zaretskii <eliz@gnu.org> wrote:
> > We don't offer customization of the display tables via defcustom, most
> > probably because it is "tricky" (as you yourself discovered). I
> > hesitate to offer just this one slot of the display table, and the
> > fact that it only affects TTY frames and requires UTF-8 capable
> > terminal on top of that doesn't provide additional motivation...
>
> Do you mean tricky from an implementation or user perspective?
The former. This is a low-level facility that Emacs itself uses on a
very low level. Naïvely customizing it will have global session-wide
effect, something many users won't want, and then they will want to
have user-level access to buffer- and window-local display tables,
something that is not trivial to get right.
> > display-fill-column-indicator-character is an entirely different
> > matter, it's a minor mode which lets users specify an indicator glyph.
>
> This I mean more from a user perspective, as in, "Oh I see I can customise this vertical line but I can't customise this vertical line next to it..."
The other one was never meant to be customized, not really.
prev parent reply other threads:[~2020-01-21 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 14:13 Making vertical-border char defcustom? Paul W. Rankin
2020-01-19 15:35 ` Eli Zaretskii
2020-01-19 23:49 ` Paul W. Rankin
2020-01-20 18:08 ` Eli Zaretskii
2020-01-21 6:25 ` Paul W. Rankin
2020-01-21 15:30 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lfq0x1wg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hello@paulwrankin.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.