From: Juri Linkov <juri@jurta.org>
To: lee <lee@yun.yagibdah.de>
Cc: 9084@debbugs.gnu.org
Subject: bug#9084: 24.0.50; displaying man pages splits the window and formats the text for the full width of the whole frame rather than for the width of the window the text is displayed in, which is only 1/2 the width of the frame
Date: Sun, 17 Jul 2011 02:18:36 +0300 [thread overview]
Message-ID: <87tyalilpf.fsf@mail.jurta.org> (raw)
In-Reply-To: <87aacerzv3.fsf@yun.yagibdah.de> (lee@yun.yagibdah.de's message of "Sat, 16 Jul 2011 17:48:00 +0200")
> When this is applied and the variable `Man-width' is set to some value,
> like 75, will the width of the window to display the manpage in be
> adjusted to the width of the text?
When you set `Man-width' to a positive integer, the manpage's text is
formatted to that width. This variable doesn't affect the window's width.
> Just splitting the current window in half when it is 230 characters
> wide gives you two windows each about 115 characters wide while you
> might rather want the window with the manpage to be `Man-width'
> characters wide and the other window as wide as the rest of the frame.
But what if you have manpage buffers in both of horizontally split
side-by-side windows?
> Then there's the documentation about `Man-frame-parameters':
>
> ,---- [ M-x describe-variable Man-frame-parameters ]
[...]
> `----
>
> (I had to look at man.el to find out that I can set `Man-width'.)
Do you think `Man-width' should be mentioned in the docstring of `man'?
> And when you proceed to customise `Man-frame-parameters', you don't have
> any idea what to enter to always get a frame that makes the window
> `Man-width' characters wide.
Maybe the docstring of `Man-frame-parameters' should provide an example
of using the frame parameter `width'?
> My understanding would be that `Man-frame-parameters' must be ignored
> when running emacs on the console because there are only windows and no
> frames available.
`Man-frame-parameters' is ignored unless `Man-notify-method' is set
to the value `newframe'. However, I don't know how the users
who prefer to set `pop-up-frames' to a non-nil value
specify the width of the manpage's frame
(when `Man-notify-method' is not `newframe')?
next prev parent reply other threads:[~2011-07-16 23:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 21:07 bug#9084: 24.0.50; displaying man pages splits the window and formats the text for the full width of the whole frame rather than for the width of the window the text is displayed in, which is only 1/2 the width of the frame lee
2011-07-15 0:46 ` Juri Linkov
2011-07-15 7:30 ` martin rudalics
2011-07-16 15:48 ` lee
2011-07-16 23:18 ` Juri Linkov [this message]
2011-07-17 13:12 ` bug#9084: 24.0.50; displaying man pages splits the window and formats the text forthe full width of the whole frame rather than for the width ofthe window the text is displayed in, which is only 1/2 thewidth " Drew Adams
2011-07-17 14:23 ` bug#9084: 24.0.50; displaying man pages splits the window and formats the text for the full width of the whole frame rather than for the width of the window the text is displayed in, which is only 1/2 the width " lee
2011-07-17 23:08 ` Juri Linkov
2011-07-18 17:56 ` lee
2011-07-19 0:34 ` Juri Linkov
2011-07-19 17:22 ` lee
2011-07-20 15:17 ` Juri Linkov
2011-07-20 17:36 ` martin rudalics
2011-07-21 12:53 ` bug#9084: 24.0.50; displaying man pages splits the window and formats the text forthe full width of the whole frame rather than for the width ofthe window the text is displayed in, which is only 1/2 thewidth " Drew Adams
2011-07-21 13:05 ` Drew Adams
2011-07-21 14:20 ` bug#9084: 24.0.50; displaying man pages splits the window and formats the text for the full width of the whole frame rather than for the width of the window the text is displayed in, which is only 1/2 the width " lee
2011-07-21 23:27 ` Juri Linkov
2011-07-22 6:29 ` martin rudalics
2011-07-25 11:18 ` Juri Linkov
2011-07-21 13:12 ` lee
2011-07-21 23:28 ` Juri Linkov
2011-07-22 8:44 ` lee
2011-07-16 23:08 ` 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=87tyalilpf.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=9084@debbugs.gnu.org \
--cc=lee@yun.yagibdah.de \
/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).