From: Juri Linkov <juri@linkov.net>
To: hw <hw@adminart.net>
Cc: 32536@debbugs.gnu.org
Subject: bug#32536: displayed width of man pages
Date: Thu, 06 Sep 2018 01:20:12 +0300 [thread overview]
Message-ID: <874lf3y4bn.fsf@mail.linkov.net> (raw)
In-Reply-To: <87tvn43cjp.fsf@toy.adminart.net> (hw@adminart.net's message of "Wed, 05 Sep 2018 04:50:29 +0200")
>>> BTW, what is the default for the minimum length of the lines? Is the
>>> default for the maximum length the same?
>>
>> Like the new Man-width-max, we could also add Man-width-min as well.
>
> I thought the line length would be determined depending on Man-width,
> the new maximum width and the width of the window displaying the buffer.
> That would make Man-width what specifies the minimum length:
>
> If the width of the window suggests using a line length between
> Man-width and the new maximum length, use the suggested length.
> Otherwise use Man-width if the window is narrower than that, or the new
> maximum length if the window is wider than the new maximum length.
>
> Renaming Man-width to Man-width-min would make sense then, unless there
> were a third option: Always use the line length specified by
> Man-width. If this option would kick in when Man-width-min and
> Man-width-max are not set, the behaviour would not change for anyone who
> has set Man-width.
>
> The default for all of them would be nil, assuming that Man-width-min
> and Man-width-max do nothing when they are nil.
The value nil of Man-width means to dynamically calculate the line length
from the width of the window displaying the buffer.
next prev parent reply other threads:[~2018-09-05 22:20 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 [this message]
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
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=874lf3y4bn.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=32536@debbugs.gnu.org \
--cc=hw@adminart.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.