From: hw <hw@adminart.net>
To: Juri Linkov <juri@linkov.net>
Cc: 32536@debbugs.gnu.org
Subject: bug#32536: displayed width of man pages
Date: Tue, 04 Sep 2018 05:34:58 +0200 [thread overview]
Message-ID: <87o9deorz1.fsf@toy.adminart.net> (raw)
In-Reply-To: <875zznmtud.fsf@mail.linkov.net> (Juri Linkov's message of "Mon, 03 Sep 2018 01:12:58 +0300")
Juri Linkov <juri@linkov.net> writes:
>> Perhaps if they /can/ be reformatted dynamically, have a variable like
>> `Man-dynamic-reformat-lines-max' so users can prevent the reformatting
>> for instances in which it takes too long.
> [...]
>> Would it be possible to do the reformatting in the background, and
>> delayed, like fontifying a buffer?
>
> Man pages are already formatted asynchronously in the background,
> so actually reformatting on window resize should be quite responsible
> even for large manuals (maybe an addition flag is needed to prevent
> updating when a previous update is in progress).
and maybe something that prevents multiple update requests piling up
while the window is being resized, unless the flag already takes care of
that
> You can try and see how fast it reformats, typing repeatedly the key `u'
> (Man-update-manpage).
Ah, hm, ok, that's maybe 0.25 seconds for the man page of fvwm with 9441
lines. It may not be a good test because the width does not change in
my case, and I have fast hardware.
Is there a reason for not to skip such an update when the length of the
lines did not change?
I didn't know you could update; this is like perfect because who prefers
dynamic updates can use those and who doesn't can use `u' if need be :)
next prev parent reply other threads:[~2018-09-04 3:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 12:42 bug#32536: 24.3; Feature Request: change defaults or behaviour hw
2018-08-30 23:35 ` bug#32536: displayed width of man pages Juri Linkov
2018-08-31 6:54 ` martin rudalics
2018-09-01 22:27 ` Juri Linkov
2018-09-02 7:14 ` martin rudalics
2018-09-02 22:19 ` Juri Linkov
2018-09-03 7:31 ` martin rudalics
2018-09-03 22:23 ` Juri Linkov
2018-09-04 7:51 ` martin rudalics
2018-09-04 21:27 ` Juri Linkov
2018-09-05 7:47 ` martin rudalics
2018-11-25 20:42 ` Juri Linkov
2018-11-26 9:32 ` martin rudalics
2018-11-27 0:01 ` Juri Linkov
2018-11-27 8:08 ` martin rudalics
2018-11-27 23:58 ` Juri Linkov
2018-09-04 5:46 ` hw
2018-09-04 21:20 ` Juri Linkov
2018-09-05 2:50 ` hw
2018-09-05 22:20 ` Juri Linkov
2018-09-07 14:03 ` hw
2018-09-02 22:30 ` Juri Linkov
2018-09-03 7:31 ` martin rudalics
2018-09-03 22:25 ` Juri Linkov
2018-09-04 7:51 ` martin rudalics
2018-09-02 14:55 ` hw
2018-09-02 22:12 ` Juri Linkov
2018-09-04 3:34 ` hw [this message]
2018-09-03 18:20 ` Filipp Gunbin
2018-12-26 23:36 ` Juri Linkov
2018-12-27 15:46 ` Eli Zaretskii
2018-12-27 20:54 ` Juri Linkov
2018-12-28 4:50 ` Eli Zaretskii
2019-12-07 22:37 ` Juri Linkov
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=87o9deorz1.fsf@toy.adminart.net \
--to=hw@adminart.net \
--cc=32536@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).