From: Yegor Timoshenko <yegortimoshenko@gmail.com>
To: "Charles A. Roelli" <charles@aurox.ch>
Cc: 28103@debbugs.gnu.org
Subject: bug#28103: M-x customize should use fill-column
Date: Wed, 16 Aug 2017 15:45:56 +0000 [thread overview]
Message-ID: <CAF4sQCOMVfwGCO8eqoOSCXM=7Vje4G0arkMi8ptM4ikhR=Ep2g@mail.gmail.com> (raw)
In-Reply-To: <m28tijr8qk.fsf@aurox.ch>
[-- Attachment #1: Type: text/plain, Size: 126 bytes --]
> Which lines are too long?
I mean lines that are generated by M-x customize that end up in
~/.emacs.d/init.el (by default).
[-- Attachment #2: Type: text/html, Size: 174 bytes --]
next prev parent reply other threads:[~2017-08-16 15:45 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
2017-08-16 15:45 ` Yegor Timoshenko [this message]
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='CAF4sQCOMVfwGCO8eqoOSCXM=7Vje4G0arkMi8ptM4ikhR=Ep2g@mail.gmail.com' \
--to=yegortimoshenko@gmail.com \
--cc=28103@debbugs.gnu.org \
--cc=charles@aurox.ch \
/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).