unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Harald Jörg" <haj@posteo.de>
To: Akib Azmain Turja <akib@disroot.org>
Cc: Emacs Developer List <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: perl-doc
Date: Wed, 27 Jul 2022 17:59:53 +0000	[thread overview]
Message-ID: <871qu6a12e.fsf@hajtower> (raw)
In-Reply-To: <87lesetq9l.fsf@disroot.org> (Akib Azmain Turja's message of "Wed, 27 Jul 2022 23:32:54 +0600")

Akib Azmain Turja <akib@disroot.org> writes:

> Harald Jörg <haj@posteo.de> writes:
>
>> don't have 'man' (notably, Windows).  My own observation is that 'man'
>> (and also 'info') seem to be stuck at a fixed page width which is
>> particularly annoying if you want to use *less* than this width for a
>> documentation frame.
>
> Set "Man-width" to the width of documentation frame.  I don't know how
> to do it Info, however there is a user option "Info-refill-paragraphs".
> Any suggestion from Info hackers?

Ah, excellent.  Again and again I learn that it is wrong to say "Emacs
doesn't do X" but instead I should ask "How do I do X in Emacs"?
I also hadn't even noticed that man actually reformats the page when the
width changes.  I have failed to find a hook for a change of window
width, but man.el simply uses an idle timer to check for changes.  I'll
adopt that in my code.

-- 
Many Thanks!
haj



  reply	other threads:[~2022-07-27 17:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 16:16 [ELPA] New package: perl-doc Harald Jörg
2022-07-27 17:32 ` Akib Azmain Turja
2022-07-27 17:59   ` Harald Jörg [this message]
2022-07-28  7:24     ` Robert Pluim
2022-07-28  9:22       ` Harald Jörg
2022-07-28  9:39         ` Robert Pluim
2022-07-28 12:17           ` Harald Jörg
2022-07-28 12:34             ` Robert Pluim
2022-07-28 19:34         ` Juri Linkov
2022-07-28 20:58           ` Harald Jörg
2022-07-28 11:19     ` Gregor Zattler
2022-07-30  7:16       ` Akib Azmain Turja
2022-07-28  4:17 ` Visuwesh
2022-07-28  5:53   ` Eli Zaretskii
2022-07-28  8:57     ` Harald Jörg
2022-08-03 12:16 ` Alexander Adolf

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=871qu6a12e.fsf@hajtower \
    --to=haj@posteo.de \
    --cc=akib@disroot.org \
    --cc=emacs-devel@gnu.org \
    /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).