From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35338@debbugs.gnu.org
Subject: bug#35338: Line numbers lost despite line-number-display-limit
Date: Sun, 21 Apr 2019 06:00:08 +0800 [thread overview]
Message-ID: <875zr8e3rr.5.fsf@jidanni.org> (raw)
In-Reply-To: <87pnphtccl.5.fsf@jidanni.org>
Users who do C-f v line-number-display-limit will never learn about
line-number-display-limit-width, and vice versa. 100%!
Therefore each docstring needs to mention the other.
Else the user won't know about the secret second hidden factor,
and will be sure it is a bug.
By the way, line-number-display-limit-width's docstring should say what
nil will do, and/or how to always/never get numbers.
P.S., "If the average length of the lines near point is bigger than
this, then the line number may be omitted from the mode line."
"near", "may" ??! Well all I know is if we do
$ { perl -wle 'print "中華民國萬歲" x 99 for 9..99;' ; seq 1111;} > /tmp/9
we start out with fat lines, and then end up with thin lines,
and we get line numbers for the first few screens, and then it gives up.
If at the bottom we do (what-line) then it remembers again, until we go
back to the fat lines, where it forgets, even if we do (what-line).
Anyway I bet these days the rest of emacs' brain is actually rather
quite aware of what line we are actually on, and just this
line-number-display-limit-width is left over from some older era...
less -M and more's '=' have no problem.
prev parent reply other threads:[~2019-04-20 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 6:33 bug#35338: Line numbers lost despite line-number-display-limit 積丹尼 Dan Jacobson
2019-04-20 13:46 ` Eli Zaretskii
2019-04-20 13:48 ` Eli Zaretskii
2019-04-20 22:00 ` 積丹尼 Dan Jacobson [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=875zr8e3rr.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=35338@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.