all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sun, 02 Sep 2018 16:55:25 +0200	[thread overview]
Message-ID: <87pnxwgd9e.fsf@himinbjorg.adminart.net> (raw)
In-Reply-To: <87d0twam5z.fsf@mail.linkov.net> (Juri Linkov's message of "Sun,  02 Sep 2018 01:27:20 +0300")

Juri Linkov <juri@linkov.net> writes:

> [...]
> Regarding the request for dynamic reformatting, I'm not sure if
> man pages should be reformatted on resizing windows (I remember
> seeing a window resize hook, but can't find it now).

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.  Then a problem is that the
number of lines varies with the width of the page, and instead of the
number of lines, the size in bytes (kB, MB ...) of the page might be
more relevant for reformatting it.

Unfortunately, users usually have no idea what the size of a manual page
in bytes is, and the pages are even stored compressed.  Users would have
to try out what size makes sense to dynamically reformat on their
particular hardware and may end up simply turning the feature off
because they do not resize windows while reading manual pages anyway.

Does it take longer to format the same manual page into 2500 lines or
into 5000 lines?

Would it be possible to do the reformatting in the background, and
delayed, like fontifying a buffer?





  parent reply	other threads:[~2018-09-02 14:55 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 [this message]
2018-09-02 22:12         ` Juri Linkov
2018-09-04  3:34           ` hw
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnxwgd9e.fsf@himinbjorg.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 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.