From: Eli Zaretskii <eliz@gnu.org>
To: Xiyue Deng <manphiz@gmail.com>
Cc: 67848@debbugs.gnu.org
Subject: bug#67848: 29.1; Fix usage of `setq-default' and add explanation
Date: Sat, 23 Dec 2023 13:20:41 +0200 [thread overview]
Message-ID: <83y1dlcghi.fsf@gnu.org> (raw)
In-Reply-To: <87jzp5fcx2.fsf@debian-hx90.lan> (message from Xiyue Deng on Sat, 23 Dec 2023 02:09:29 -0800)
> From: Xiyue Deng <manphiz@gmail.com>
> Cc: 67848@debbugs.gnu.org
> Date: Sat, 23 Dec 2023 02:09:29 -0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Xiyue Deng <manphiz@gmail.com>
> >> Date: Sat, 16 Dec 2023 03:18:20 -0800
> >>
> >>
> > Thanks, but I think it's wrong to use setq-default here, since that
> > makes Text mode the default major-mode (instead of Fundamental), which
> > is not what most people would want.
>
> Actually making text-mode the default mode for new files is exactly what
> the author intended based on the text from an earlier section[1].
I know, but I don't want that to be said without reservations, or not
at all. The author's hope was that there will be many readers of this
manual who are not programmers, and who would then prefer Text mode as
the default. We are now a few decades wiser, and we know that hope
didn't really materialize. So we should not advertise such a setting
without some explanations.
> Of course, whether this is a good advice is a slightly different matter,
> and may be worth discussing in a footnote if it sounds worth doing. But
> based on the text flow setting the new default major-mode should not be
> changed IMHO.
Sorry, I disagree, for the reasons explained above.
Thanks.
next prev parent reply other threads:[~2023-12-23 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 11:18 bug#67848: 29.1; Fix usage of `setq-default' and add explanation Xiyue Deng
2023-12-16 11:26 ` Xiyue Deng
2023-12-23 9:00 ` Eli Zaretskii
2023-12-23 10:09 ` Xiyue Deng
2023-12-23 11:20 ` Eli Zaretskii [this message]
2023-12-24 7:00 ` Xiyue Deng
2023-12-24 8:47 ` Eli Zaretskii
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=83y1dlcghi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67848@debbugs.gnu.org \
--cc=manphiz@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 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.