unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 18 Jul 2011 02:08:04 +0300	[thread overview]
Message-ID: <87hb6kcx7z.fsf@mail.jurta.org> (raw)
In-Reply-To: <87zkkdouje.fsf@yun.yagibdah.de> (lee@yun.yagibdah.de's message of "Sun, 17 Jul 2011 16:23:33 +0200")

> To me, it would make sense if it did or if I could make it so that it
> does, for example by specifying a negative integer like -75 to have the
> page formatted 75 characters wide /and/ the width of the window adjusted
> accordingly.  Imho, there isn't much point in making the window wider
> than the text it displays when viewing manpages.

You are asking for functionality that is not specific to manpages.
Typical text width in all buffers that I see is no more than 75 characters:
in Dired buffers, in Info buffers, in source code buffers, etc.
Usually there is no point in making the window wider than the text
displayed in all these buffers.  I think the width of the window
and other parameters of window configurations should be specified
at more general level.

> When your window is 230 characters wide, you could set Man-width to 70
> and display three pages side by side?

There was a plan to implement functionality where you can define
arbitrary window layouts, e.g. you will be able to define a layout
to display three manpage dedicated buffers side by side, etc.

> Since there's the usual man command you run from a shell, it's not too
> obvious that "M-x man" is something very different.

`M-x man' is not much different.  For the usual man command you can
define the width by the environment variable `MANWIDTH' or `COLUMNS'.
And for `M-x man' there is a similar option `Man-width'.





  reply	other threads:[~2011-07-17 23:08 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
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 [this message]
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=87hb6kcx7z.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).