unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Inadequate coding in hack-elisp-shorthands
Date: Fri, 1 Oct 2021 17:03:44 +0000	[thread overview]
Message-ID: <YVc/cIDyoMEBnN39@ACM> (raw)
In-Reply-To: <83czopfg2x.fsf@gnu.org>

Hello, Eli.

On Fri, Oct 01, 2021 at 08:51:18 +0300, Eli Zaretskii wrote:
> > Date: Thu, 30 Sep 2021 20:35:17 +0000
> > From: Alan Mackenzie <acm@muc.de>

> > 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.

> Thanks, but why isn't this a full-blown bug report, submitted to
> debbugs?

The last sentence - I was hoping to recruit somebody (somebody more
enthusiastic about the feature than me) to do the reviewing, and this is
more likely on emacs-devel than debbugs.

But I'll resubmit it as a bug this evening.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2021-10-01 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 20:35 Inadequate coding in hack-elisp-shorthands Alan Mackenzie
2021-10-01  5:51 ` Eli Zaretskii
2021-10-01 17:03   ` Alan Mackenzie [this message]
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

  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=YVc/cIDyoMEBnN39@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --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 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).