From: Eli Zaretskii <eliz@gnu.org>
To: Romanos Skiadas <rom.skiad@gmail.com>
Cc: 28533@debbugs.gnu.org
Subject: bug#28533: 26.0.60; Native line numbers move with show-paren-mode enabled
Date: Fri, 22 Sep 2017 10:22:41 +0300 [thread overview]
Message-ID: <83shffci4e.fsf@gnu.org> (raw)
In-Reply-To: <70f5d04e-48d5-bf0d-fff7-8e7107878d9a@gmail.com> (message from Romanos Skiadas on Thu, 21 Sep 2017 22:11:48 +0100)
> Cc: 28533@debbugs.gnu.org
> From: Romanos Skiadas <rom.skiad@gmail.com>
> Date: Thu, 21 Sep 2017 22:11:48 +0100
>
> In any case, I would expect line numbers not to move regardless of
> whatever reasonable condition the buffer is in, hence I still think that
> this bug should remain open.
Fine with me.
> If you think it is a WONTFIX kind of deal, I'm ok with closing it. As
> far as I can tell the customizations you suggested are not somewhere in
> the docs. Should they added in NEWS and in any other relevant documentation?
Not sure what you mean: the variables I mentioned are AFAIK documented
in the Emacs manual.
> >In modes that hide many lines from display, you should customize
> display-line-numbers-width-start to a non-nil value
>
> This only fixes the problem is the lines are already in the buffer. If
> you write and fold 100 lines in an empty buffer, the issue still shows up.
>
> >or manually set display-line-numbers-width to a value large enough to
> accommodate the last physical line of the file (e.g., in file-local
> variables).
>
> This works, but I expect Emacs to be able to calculate this correctly
> out of the box without any kind of intervention.
IMO, this should be brought up to the attention of the Org developers.
Org mode has special needs when non-relative line numbers are
displayed, and the solution should IMO be in Org, not in Emacs core,
because solving that in core would mean significant run-time penalties
for everyone who uses line-number display. I'm sure that these issues
can be quite easily fixed on the Lisp level by Org mode itself.
Thanks.
next prev parent reply other threads:[~2017-09-22 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 20:14 bug#28533: 26.0.60; Native line numbers move with show-paren-mode enabled Romanos Skiadas
2017-09-20 20:42 ` Romanos Skiadas
2017-09-21 9:11 ` Eli Zaretskii
2017-09-21 21:11 ` Romanos Skiadas
2017-09-22 7:22 ` Eli Zaretskii [this message]
[not found] ` <985db77a-8f22-34c8-a60c-45fe2c2999ea@gmail.com>
[not found] ` <83h8vtc3jf.fsf@gnu.org>
2017-09-23 8:49 ` Romanos Skiadas
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=83shffci4e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28533@debbugs.gnu.org \
--cc=rom.skiad@gmail.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).