From: Akib Azmain Turja <akib@disroot.org>
To: Emacs Developer List <emacs-devel@gnu.org>
Cc: "Gregor Zattler" <telegraph@gmx.net>, "Harald Jörg" <haj@posteo.de>
Subject: Re: [ELPA] New package: perl-doc
Date: Sat, 30 Jul 2022 13:16:31 +0600 [thread overview]
Message-ID: <878robjcj4.fsf@disroot.org> (raw)
In-Reply-To: <87edy5scvd.fsf@no.workgroup> (Gregor Zattler's message of "Thu, 28 Jul 2022 13:19:50 +0200")
[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]
Gregor Zattler <telegraph@gmx.net> writes:
> Hi Harald, Akib,
> * Harald Jörg <haj@posteo.de> [2022-07-27; 17:59]:
>> Akib Azmain Turja <akib@disroot.org> writes:
>>> 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?
I just found how to do this, just set "Info-refill-paragraphs" and
"Info-hide-note-references" to non-nil and set "fill-column" to the
desired text width.
>>
>> 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 used to setq Info-refill-paragraphs to t, but as the
> documentation says, "this only has an effect if
> Info-hide-note-references is non-nil"
That's non-nil by default.
> and then one should
> "be prepared for a few surprises if you enable this
> feature".
Yeah, sometimes you'll be surprised seeing a few too long or too short
lines, but these aren't so big problems IMHO.
>
> For me the refilling of info was not worth these surprises.
> And nowadays my display is wide enough anyway.
Yeah, now almost all computers have a wide enough display. But that
doesn't mean that someone will use the full display for a single task.
For example, I often have a Info window on the right side of my display
when I new try something new, and I want it to be as small as possible
while still allowing me to read text on that window without scrolling,
to give me more space for writing and other tasks.
>
> Ciao; Gregor
>
--
Akib Azmain Turja
Find me on Mastodon at @akib@hostux.social.
This message is signed by me with my GnuPG key. It's fingerprint is:
7001 8CE5 819F 17A3 BBA6 66AF E74F 0EFA 922A E7F5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-07-30 7:16 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
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 [this message]
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=878robjcj4.fsf@disroot.org \
--to=akib@disroot.org \
--cc=emacs-devel@gnu.org \
--cc=haj@posteo.de \
--cc=telegraph@gmx.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 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).