unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: spacibba@aol.com, Emacs developers <emacs-devel@gnu.org>
Subject: Re: :extend face attribute at EOB without end-of-line char
Date: Tue, 15 Oct 2019 10:10:21 +0200	[thread overview]
Message-ID: <CAAeL0SSWhjVEma=fu6HKS1FL5PkuDA12fikNvuL435YEYuC=pg@mail.gmail.com> (raw)
In-Reply-To: <83zhi2h6up.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

On Tue, Oct 15, 2019 at 8:15 AM Eli Zaretskii <eliz@gnu.org> wrote:

> OK, but still, we'd need a rationale.

I'm not sure what rationale would satisfy you. In my mind, the idea of
extending a face up to the margin of the window seems quite decoupled from
whether that line has a newline at the end or not. It's purely visual. If
I'm using a face that extends in all lines, for example, I find weird that
it does or does not extend in the last one depending of a newline. (Again:
I agree that's how it is defined now, I'm not questioning that.)

> The use case is quite obscure, IMO,

Yes. I happen to use bs-show, and hl-line-mode in bs-show, so it's not
obscure for me, obviously. (Years ago I defined the format of my bs lines
to fill entirely the window with spaces to avoid this ugly "ragged" effect
on the last one.) But whether it will be useful in other cases will depend
on how frequent is to have buffers with a non-newline last line, I suppose.
No idea.

> and the implementation won't be trivial (I had my share of bugs
> from fiddling with display code past ZV, and you just had a taste of
> that with the ticks feature).

Yes. It was quite "entertaining", so to speak.

[-- Attachment #2: Type: text/html, Size: 1503 bytes --]

  reply	other threads:[~2019-10-15  8:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 16:02 :extend face attribute at EOB without end-of-line char Juanma Barranquero
2019-10-14 16:32 ` Ergus
2019-10-14 16:37   ` Juanma Barranquero
2019-10-14 17:07     ` Ergus
2019-10-14 17:52       ` Juanma Barranquero
2019-10-14 17:57         ` Juanma Barranquero
2019-10-14 17:58     ` Eli Zaretskii
2019-10-14 19:41       ` Juanma Barranquero
2019-10-14 19:47         ` Eli Zaretskii
2019-10-14 19:50           ` Juanma Barranquero
2019-10-14 20:04             ` Eli Zaretskii
2019-10-14 21:37               ` Juanma Barranquero
2019-10-15  6:15                 ` Eli Zaretskii
2019-10-15  8:10                   ` Juanma Barranquero [this message]
2019-10-15  8:27                     ` Eli Zaretskii
2019-10-15  8:50                       ` Juanma Barranquero
2019-10-15 13:23                         ` Stefan Monnier
2019-10-15 14:16                           ` Juanma Barranquero
2019-10-15 16:38                       ` Ergus
2019-10-15 16:49                         ` Eli Zaretskii
2019-10-16  0:23                           ` Ergus

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='CAAeL0SSWhjVEma=fu6HKS1FL5PkuDA12fikNvuL435YEYuC=pg@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.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).