From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 46472@debbugs.gnu.org
Subject: bug#46472: Make lisp/mail/uce.el obsolete
Date: Sat, 13 Feb 2021 16:00:01 +0200 [thread overview]
Message-ID: <83mtw8cbku.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=XPCv_3UTkK=2L66hj1-q-qM-2NtdtkUO5C3jvhWcw8g@mail.gmail.com> (message from Stefan Kangas on Sat, 13 Feb 2021 06:25:19 -0600)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 13 Feb 2021 06:25:19 -0600
> Cc: 46472@debbugs.gnu.org
>
> But I think we should be equally free to (strongly) recommend against
> bad practices.
The method of "recommendation" you propose is too strong for my
palate, sorry. In general, I believe that people should be left to
their devices unless what they do causes harm to others.
Second-guessing other people under the assumption that we know better
is something I don't like doing, and don't like others doing to me.
How about adding some warnings to uce.el instead, either in the
commentary or when the main entry point is invoked for the first time
in a session?
next prev parent reply other threads:[~2021-02-13 14:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 21:58 bug#46472: Make lisp/mail/uce.el obsolete Stefan Kangas
2021-02-13 7:58 ` Eli Zaretskii
2021-02-13 12:25 ` Stefan Kangas
2021-02-13 14:00 ` Eli Zaretskii [this message]
2021-03-04 19:27 ` Glenn Morris
2021-03-04 21:12 ` Eli Zaretskii
2021-03-06 17:14 ` Stefan Kangas
2021-03-06 17:25 ` Eli Zaretskii
2022-06-17 13:07 ` Lars Ingebrigtsen
2021-10-12 4:33 ` Stefan Kangas
2021-10-12 13:52 ` Eli Zaretskii
2021-10-12 16:12 ` Stefan Kangas
2021-10-12 16:44 ` Eli Zaretskii
2021-10-12 17:29 ` Stefan Kangas
2021-10-12 18:50 ` Eli Zaretskii
2021-10-14 20:45 ` Stefan Kangas
2021-10-15 6:12 ` Eli Zaretskii
2021-10-15 8:50 ` Stefan Kangas
2021-10-15 10:46 ` Eli Zaretskii
2021-10-16 12:48 ` Stefan Kangas
2021-10-16 12:50 ` Eli Zaretskii
2021-10-17 23:56 ` Stefan Kangas
2021-10-16 12:32 ` Stefan Kangas
2021-03-03 21:22 ` Stefan Monnier
2021-03-04 3:39 ` 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
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=83mtw8cbku.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46472@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).