From: Alan Mackenzie <acm@muc.de>
To: "João Távora" <joaotavora@gmail.com>
Cc: 50946@debbugs.gnu.org
Subject: bug#50946: Emacs-28: Inadequate coding in hack-elisp-shorthands
Date: Sat, 2 Oct 2021 12:38:58 +0000 [thread overview]
Message-ID: <YVhS4qeDJmp5SFyM@ACM> (raw)
In-Reply-To: <87ee933bcj.fsf@gmail.com>
Hello, João.
On Sat, Oct 02, 2021 at 12:38:52 +0100, João Távora wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > clumsy messing around with temporary buffers, file-attributes, and
I stand by that description. It was accurate.
> Also, if you want to converse, be polite. Your petty posturing doesn't
> intimidate me. So go insult someone else.
I respectfully request you to deal with the issues I have raised. If
you want to direct disrespect at me, private email would probably be a
better place.
To be perfectly honest, I was shocked when I saw the state of the coding
in that defun. I have not said on this list what I really think about
it, and will not do so. I can only hope that you just threw something
together as a proof of concept, and then forgot to change it into
acceptable code before committing it. Or something like that. If so,
an apology would be appropriate.
You closed this bug without fixing it. There are corner cases the "fix"
doesn't handle, which I pointed out earlier and you ignored. You closed
the bug without even having the decency to ask me to check the patch
first. That is not polite, and not the normal way things are done,
here.
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.
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.
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.
> João
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2021-10-02 12:38 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 [this message]
2021-10-02 12:52 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YVhS4qeDJmp5SFyM@ACM \
--to=acm@muc.de \
--cc=50946@debbugs.gnu.org \
--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 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.