unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: charles@aurox.ch (Charles A. Roelli)
To: Yegor Timoshenko <yegortimoshenko@gmail.com>
Cc: 28103@debbugs.gnu.org
Subject: bug#28103: M-x customize should use fill-column
Date: Wed, 16 Aug 2017 14:35:15 +0200	[thread overview]
Message-ID: <m28tijr8qk.fsf@aurox.ch> (raw)
In-Reply-To: <CAF4sQCNg3u989dNDOEwj-h_CF1ZcEc1MiXVvjOhuOf9YyYEvRQ@mail.gmail.com> (message from Yegor Timoshenko on Tue, 15 Aug 2017 20:05:46 +0000)

From emacs -q:

M-x load-library eshell RET
M-x customize-variable eshell-modules-list RET

gives something like this:

Eshell Modules List:
[X] eshell-alias -- Command aliases

Command aliases allow for easy definition of alternate commands.
 
[X] eshell-banner -- Login banner

This sample module displays a welcome banner at login.
It exists so that others wishing to create their own Eshell extension
modules may have a simple template to begin with.
 
[X] eshell-basic -- Basic shell commands

The "basic" code provides a set of convenience functions which
are traditionally considered shell builtins.  Since all of the
functionality provided by them is accessible through Lisp, they are
not really builtins at all, but offer a command-oriented way to do the
same thing.

[...]

Which lines are too long?

> From: Yegor Timoshenko <yegortimoshenko@gmail.com>
> Date: Tue, 15 Aug 2017 20:05:46 +0000
> 
> 
> 
> Hello! This is an enhancement request.
> 
> M-x customize sometimes produces very long lines (for example, try customizing eshell-modules-list). It'd be nice if M-x customize honored `fill-column` when pretty-printing.





  reply	other threads:[~2017-08-16 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 20:05 bug#28103: M-x customize should use fill-column Yegor Timoshenko
2017-08-16 12:35 ` Charles A. Roelli [this message]
2017-08-16 15:45   ` Yegor Timoshenko
2017-08-20 13:29     ` Charles A. Roelli
2021-08-13 13:11     ` Lars Ingebrigtsen

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=m28tijr8qk.fsf@aurox.ch \
    --to=charles@aurox.ch \
    --cc=28103@debbugs.gnu.org \
    --cc=yegortimoshenko@gmail.com \
    /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).