unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Yegor Timoshenko <yegortimoshenko@gmail.com>
To: Drew Adams <drew.adams@oracle.com>, help-gnu-emacs@gnu.org
Subject: Re: M-x customize and long lines
Date: Tue, 15 Aug 2017 20:06:23 +0000	[thread overview]
Message-ID: <CAF4sQCNqxkmyAov5PLfxyfzwgMEsZr1Qq9E=7-ZjYZrJMbWxhw@mail.gmail.com> (raw)
In-Reply-To: <97613137-aade-430f-a04c-a385b2dabae9@default>

Thanks! I've sent an enhancement request.


On Sat, Aug 12, 2017 at 4:02 PM Drew Adams <drew.adams@oracle.com> wrote:

> > M-x customize sometimes produces very long lines (for example, try
> > customizing eshell-modules-list). Here's what I get:
> >
> > (custom-set-variables
> >  ;; custom-set-variables was added by Custom.
> >  ;; If you edit it by hand, you could mess it up, so be careful.
> >  ;; Your init file should contain only one such instance.
> >  ;; If there is more than one, they won't work right.
> >  '(eshell-modules-list
> >    (quote
> >     (eshell-alias eshell-cmpl eshell-dirs eshell-glob eshell-hist
> eshell-ls
> > eshell-term eshell-tramp eshell-unix)))
> >
> > How do I make M-x customize respect 80 chars per line limit? Is there a
> > hook? I couldn't find one.
>
> 1. I don't think there is one, out of the box.
>
> 2. If you define `custom-file' then you won't need to care about
>    how Customize writes to it.  You will likely never edit it
>    or even look at it.
>
> You might want to file an enhancement request
> (`M-x report-emacs-bug'), asking that Customize use `fill-column'
> when it pretty-prints.
>


      reply	other threads:[~2017-08-15 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-12 15:13 M-x customize and long lines Yegor Timoshenko
2017-08-12 16:02 ` Drew Adams
2017-08-15 20:06   ` Yegor Timoshenko [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://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='CAF4sQCNqxkmyAov5PLfxyfzwgMEsZr1Qq9E=7-ZjYZrJMbWxhw@mail.gmail.com' \
    --to=yegortimoshenko@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@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.
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).