From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] emacs: Fill package description in Info buffers.
Date: Tue, 14 Jul 2015 15:15:08 +0200 [thread overview]
Message-ID: <87vbdmswwz.fsf@gnu.org> (raw)
In-Reply-To: <87y4ijxhrf.fsf@gmail.com> (Alex Kost's message of "Tue, 14 Jul 2015 11:31:16 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Since there is a buffer-local 'fill-column' variable, I think we may use
> it instead of hard-coding '72', so that a user could change it, for
> example like this:
>
> (add-hook 'guix-package-info-mode-hook
> (lambda () (setq fill-column 60)))
Indeed, it’s better this way.
>> + (guix-format-insert val (and (facep face) face))
>> + (fill-region begin (point))
>
> I think it's better to use 'guix-get-filled-string' instead of
> (let ((begin (point))) ... (fill-region begin (point)))
Agreed, I hadn’t noticed that one.
> Actually, I think that preserving the original formatting used in
> "description" fields is a feature, not a bug, as it allows to find too
> long lines or other related things and then to fix those.
>
> (For example, I've just accidentally found that the first line of
> "pulseaudio" description is too long, and when I looked at the source, I
> also noticed that the description ends with a space. With your change
> it wouldn't be possible to notice :-))
I think I would turn to the source file when I want to nitpick on
description formatting. ;-)
> But as we can always add another option for a user to choose the variant
> he wants, I agree. What about the attached modified patch?
>
> Also as it may concern synopsis (when a current window is too small to
> fit the synopsis), I renamed the patch into "emacs: Fill package heading
> in Info buffers."
Your patch looks better indeed. Please push, thank you!
Ludo’.
prev parent reply other threads:[~2015-07-14 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 20:08 [PATCH] emacs: Fill package description in Info buffers Ludovic Courtès
2015-07-14 8:31 ` Alex Kost
2015-07-14 13:15 ` Ludovic Courtès [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbdmswwz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-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/guix.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).