From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 72b1379f079: Increase `emacs-lisp-docstring-fill-column` to 72
Date: Sat, 03 Feb 2024 13:18:02 +0200 [thread overview]
Message-ID: <86y1c13ifp.fsf@gnu.org> (raw)
In-Reply-To: <871q9tnaod.fsf@yahoo.com> (message from Po Lu on Sat, 03 Feb 2024 17:45:22 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 03 Feb 2024 17:45:22 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Po Lu <luangruo@yahoo.com>
> >> Date: Sat, 03 Feb 2024 15:43:46 +0800
> >>
> >> What problems came of the old value of 64, so urgent that it was
> >> necessary to install this change (which, let us not forget, affects
> >> _all_ Emacs users) on such short notice?
> >
> > And what problems do you envision from the new value?
>
> Doc strings in old code will be a different width from those in new
> code
No, they won't be, judging by what we already have. See my other
message which explains why.
> > I'm surprised that you are opposed to something that has close to no
> > effect on the doc strings. It sounds like another bikeshedding to me.
>
> Its effect will become visible over time
Over a very very very long time. Nothing to care about, really.
next prev parent reply other threads:[~2024-02-03 11:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170687730547.552.9673193819426474611@vcs2.savannah.gnu.org>
[not found] ` <20240202123506.0CEC7C0EFF5@vcs2.savannah.gnu.org>
2024-02-02 14:02 ` master 72b1379f079: Increase `emacs-lisp-docstring-fill-column` to 72 Po Lu
2024-02-02 14:23 ` Stefan Kangas
2024-02-03 3:00 ` Po Lu
2024-02-03 3:09 ` Emanuel Berg
2024-02-03 7:43 ` Po Lu
2024-02-03 8:02 ` Emanuel Berg
2024-02-03 8:53 ` Eli Zaretskii
2024-02-03 9:45 ` Po Lu
2024-02-03 10:33 ` Emanuel Berg
2024-02-03 11:18 ` Eli Zaretskii [this message]
2024-02-03 9:48 ` Emanuel Berg
2024-02-03 11:23 ` Eli Zaretskii
2024-02-03 11:57 ` Emanuel Berg
2024-02-03 12:17 ` Eli Zaretskii
2024-02-03 12:37 ` Emanuel Berg
2024-02-03 8:04 ` Adam Porter
2024-02-03 8:25 ` Emanuel Berg
2024-02-03 9:36 ` Po Lu
2024-02-03 10:06 ` Emanuel Berg
2024-02-03 10:28 ` Adam Porter
2024-02-03 10:45 ` Emanuel Berg
2024-02-03 11:04 ` Po Lu
2024-02-03 11:17 ` Emanuel Berg
2024-02-03 11:45 ` Adam Porter
2024-02-03 12:34 ` Emanuel Berg
2024-02-04 4:44 ` Richard Stallman
2024-02-04 5:17 ` Emanuel Berg
2024-02-07 3:12 ` Richard Stallman
2024-02-03 11:13 ` Emanuel Berg
2024-02-03 13:43 ` Eric S Fraga
2024-02-03 21:56 ` Stefan Kangas
2024-02-03 8:31 ` Eli Zaretskii
2024-02-03 10:02 ` Po Lu
2024-02-03 10:16 ` Alfred M. Szmidt
2024-02-03 11:20 ` Eli Zaretskii
2024-02-03 12:12 ` Emanuel Berg
2024-02-03 21:47 ` Stefan Kangas
2024-02-03 23:14 ` Po Lu
2024-02-04 1:28 ` Emanuel Berg
2024-02-04 1:25 ` Emanuel Berg
2024-02-02 14:35 ` Emanuel Berg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y1c13ifp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.