all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: emacs-devel@gnu.org,Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Line height issues with display-line-number-mode
Date: Tue, 07 May 2019 21:49:30 +0200	[thread overview]
Message-ID: <ADFE5A93-383C-40A3-A2AE-51788898841A@aol.com> (raw)
In-Reply-To: <jwvftpqccin.fsf-monnier+emacs@gnu.org>

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

If you go for this solution then, please tell it here if you push the patch, to check if we don't have the same issue with the fill-column-indicator.

On May 7, 2019 9:09:23 PM GMT+02:00, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>> If you a re thinking about clipping characters on display in some
>way,
>> Or maybe we could have an option not to put a number on a screen line
>> that starts with a display or overlay string.
>
>Not sure what would be the ideal behavior for compact-docstrings (no
>line-number?  Truncated line-number?  smaller line-number?), but for
>those "text lines turned into thin graphical lines" as in
>describe-symbol, *vc-log*, and friends, I think the better behavior
>would be to not display a line number at all.
>
>Rather than try and guess it based on the presence of a
>display/overlay,
>maybe we could require a specific text-property like `no-line-number`?
>
>
>        Stefan
>        
>
>BTW: in nlinum-mode (and presumably linum-mode as well), the
>     line-numbers are clipped, so I guess this is a difference between
>     text-in-the-margin and text-in-the-"main"-area.

-- 
Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.

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

  parent reply	other threads:[~2019-05-07 19:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 16:40 Line height issues with display-line-number-mode Clément Pit-Claudel
2019-05-07 17:12 ` Noam Postavsky
2019-05-07 18:36   ` Eli Zaretskii
2019-05-07 19:00     ` Eli Zaretskii
2019-05-07 19:09       ` Stefan Monnier
2019-05-07 19:43         ` Eli Zaretskii
2019-05-07 20:30           ` Stefan Monnier
2019-05-08  6:43             ` Eli Zaretskii
2019-05-08 13:39               ` Stefan Monnier
2019-05-08 14:05                 ` Eli Zaretskii
2019-05-08 14:13                   ` Noam Postavsky
2019-05-08 15:04                     ` Stefan Monnier
2019-05-08 18:39                       ` Noam Postavsky
2019-05-08 18:54                         ` Eli Zaretskii
2019-05-10  6:15                           ` Kévin Le Gouguec
2019-05-10  7:58                             ` Eli Zaretskii
2019-05-10 13:24                             ` Stefan Monnier
2019-05-08 14:17                   ` Stefan Monnier
2019-05-08 17:30                     ` Eli Zaretskii
2019-05-08 17:46                       ` Stefan Monnier
2019-05-08 18:02                         ` Eli Zaretskii
2019-05-08 18:39                           ` Stefan Monnier
2019-05-08 18:48                             ` Eli Zaretskii
2019-05-08 19:03                               ` Stefan Monnier
2019-05-07 19:49         ` Ergus [this message]
2019-05-08  5:51           ` Eli Zaretskii
2019-05-08 13:40             ` Stefan Monnier
2019-05-08 14:07               ` Eli Zaretskii
2019-05-07 18:31 ` Eli Zaretskii
2019-05-07 21:08   ` Clément Pit-Claudel
2019-05-08  7:01     ` Eli Zaretskii
2019-05-08 12:24       ` Clément Pit-Claudel
2019-05-08 14:00         ` Eli Zaretskii
2019-05-08 18:04           ` Clément Pit-Claudel
2019-05-08 18:25             ` Eli Zaretskii
2019-05-08 18:45             ` Stefan Monnier

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=ADFE5A93-383C-40A3-A2AE-51788898841A@aol.com \
    --to=spacibba@aol.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.