From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: Inadequate coding in hack-elisp-shorthands
Date: Thu, 30 Sep 2021 20:35:17 +0000 [thread overview]
Message-ID: <YVYfhRGGiViUxkRY@ACM> (raw)
Hello, Emacs.
In emacs -Q in the emacs-28 branch, create the following two line file,
foobar.el, and try to load it:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(defvar foo-baz "foobar-baz")
FOOBARELISP-SHORTHANDS: (("foo" . "foobar")))
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
This will throw an error, but that isn't important.
What is important is that the symbol foobar-baz is created by the
elisp-shorthands facility.
This shouldn't happen since:
1/- There is no Local Variables section.
2/- There is no variable elisp-shorthands in that non-existent section.
The following errors are evident in hack-elisp-shorthands:
1/- The code doesn't check for a correctly formatted Local Variables
section.
2/- The code, even if it did check, would only check the last 3000 bytes
in the file. The section can occur anywhere in the last 3000
CHARACTERS.
3/- The code doesn't do a case-sensitive search for "elisp-shorthands".
4/- The code doesn't check for "elisp-shorthands" being a complete
symbol.
5/- The code doesn't even check that "elisp-shorthands" is in a comment.
I would suggest that these errors be corrected. I would also suggest
that the entire code and documentation for this new facility be
carefully reviewed by somebody who isn't the original author.
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2021-09-30 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 20:35 Alan Mackenzie [this message]
2021-10-01 5:51 ` Inadequate coding in hack-elisp-shorthands Eli Zaretskii
2021-10-01 17:03 ` Alan Mackenzie
2021-10-01 21:32 ` João Távora
2021-10-02 0:53 ` 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=YVYfhRGGiViUxkRY@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
/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.