From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 50946@debbugs.gnu.org, joaotavora@gmail.com
Subject: bug#50946: Emacs-28: Inadequate coding in hack-elisp-shorthands
Date: Sat, 02 Oct 2021 15:52:29 +0300 [thread overview]
Message-ID: <83pmsnbnci.fsf@gnu.org> (raw)
In-Reply-To: <YVhS4qeDJmp5SFyM@ACM> (message from Alan Mackenzie on Sat, 2 Oct 2021 12:38:58 +0000)
> Date: Sat, 2 Oct 2021 12:38:58 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>, 50946@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> I think that with hack-elisp-shorthands having been coded without
> attention to detail, there is a good chance the rest of this feature is
> similarly lacking in attention to detail, which is why I asked for an
> independent person to check. Eli seems to think this isn't a problem.
If you want me to take your critique seriously, please be specific:
what are the aspects of that function that you think lack attention to
detail, and what detail? We _are_ having a technical discussion of a
Lisp program, and quite a short one at that, right? If so, it
shouldn't be hard for you to provide the details of what worries you
there. And while at that, please try to distinguish between general
problems of hack-local-variables--find-variables, which affect all of
Emacs, and hack-elisp-shorthands, which is specific to this feature.
> You haven't fixed this bug. When you first closed it this afternoon, I
> assumed you did so by accident, since the -done@debbugs.gnu.org was on
> the Cc:. Your recent closing of this unfixed bug was clearly
> deliberate.
Which bug (or bugs) is that?
> I'm not going to get into a childish game with you, opening and closing
> this bug repeatedly. Instead, I invite you to calm down, think it over
> over the next few days, and consider whether such unfixed bugs are
> really the right thing for Emacs.
I don't think you are calm enough, either. So the invitation to calm
down goes both ways here. Please focus on technical issues and leave
ad-hominem out of this, okay?
next prev parent reply other threads:[~2021-10-02 12:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 17:10 bug#50946: Emacs-28: Inadequate coding in hack-elisp-shorthands Alan Mackenzie
2021-10-01 17:53 ` Eli Zaretskii
2021-10-01 21:15 ` João Távora
2021-10-02 6:10 ` Eli Zaretskii
2021-10-02 0:48 ` João Távora
2021-10-02 10:50 ` Alan Mackenzie
2021-10-02 11:13 ` João Távora
2021-10-02 11:38 ` João Távora
2021-10-02 12:38 ` Alan Mackenzie
2021-10-02 12:52 ` Eli Zaretskii [this message]
2021-10-02 13:57 ` Alan Mackenzie
2021-10-02 14:19 ` Eli Zaretskii
2021-10-02 14:45 ` Alan Mackenzie
2021-10-02 15:00 ` Eli Zaretskii
2021-10-02 20:07 ` Alan Mackenzie
2021-10-03 11:45 ` Eli Zaretskii
2021-10-03 12:10 ` bug#50946: insert-file-contents can corrupt buffers. [Was: bug#50946: Emacs-28: Inadequate coding in hack-elisp-shorthands] Alan Mackenzie
2021-10-03 12:40 ` Eli Zaretskii
2021-10-03 13:33 ` Alan Mackenzie
2021-10-03 15:04 ` bug#50946: insert-file-contents can corrupt buffers Alan Mackenzie
2021-10-03 15:25 ` Eli Zaretskii
2021-10-03 17:21 ` Alan Mackenzie
2021-10-03 17:36 ` Eli Zaretskii
2021-10-03 18:19 ` Alan Mackenzie
2021-10-03 15:34 ` bug#50946: insert-file-contents can corrupt buffers. [Was: bug#50946: Emacs-28: Inadequate coding in hack-elisp-shorthands] João Távora
2021-10-03 15:42 ` João Távora
2021-10-03 15:56 ` Eli Zaretskii
2021-10-03 16:02 ` João Távora
2021-10-03 16:20 ` Eli Zaretskii
2021-10-03 17:05 ` João Távora
2021-10-03 17:56 ` Eli Zaretskii
2021-10-03 18:59 ` João Távora
2021-10-03 19:51 ` Eli Zaretskii
2021-10-03 19:59 ` João Távora
2021-10-02 15:02 ` bug#50946: Emacs-28: Inadequate coding in hack-elisp-shorthands João Távora
2021-10-04 0:14 ` Richard Stallman
2021-10-02 14:47 ` João Távora
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=83pmsnbnci.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50946@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=joaotavora@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 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).