unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 20 Jan 2020 20:08:00 +0200	[thread overview]
Message-ID: <83tv4qvw5b.fsf@gnu.org> (raw)
In-Reply-To: <135AF6D0-B520-496B-92F6-531CEDF2C932@paulwrankin.com> (hello@paulwrankin.com)

> From: "Paul W. Rankin" <hello@paulwrankin.com>
> Date: Mon, 20 Jan 2020 09:49:30 +1000
> Cc: emacs-devel@gnu.org
> 
> > I don't understand the difficulty.  AFAIU, all you need is augment
> > your prettify-vertical-border with a call to window-display-table, and
> > then no overriding could get in your way.  Or am I missing something?
> 
> Ah sorry, the issue seems to be with some interference from a global minor mode page-break-lines-mode... Your suggestion helped me find that. Thanks.

You are welcome.

> Would the net benefit from making the vertical-border char defcustom still make it worthwhile? It seems similar to the recently added display-fill-column-indicator-character, a vertical line that sits next to the vertical border and is customisable.

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...

display-fill-column-indicator-character is an entirely different
matter, it's a minor mode which lets users specify an indicator glyph.



  reply	other threads:[~2020-01-20 18:08 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 [this message]
2020-01-21  6:25       ` Paul W. Rankin
2020-01-21 15:30         ` Eli Zaretskii

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=83tv4qvw5b.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 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).