GNU bug report logs - #27726
26.0.50; plist functions give confusing errors on invalid plists

Previous Next

Package: emacs;

Reported by: Lars Ingebrigtsen <larsi <at> gnus.org>

Date: Sun, 16 Jul 2017 19:51:01 UTC

Severity: normal

Found in version 26.0.50

Done: Philipp Stephani <p.stephani2 <at> gmail.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 27726 in the body.
You can then email your comments to 27726 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#27726; Package emacs. (Sun, 16 Jul 2017 19:51:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Lars Ingebrigtsen <larsi <at> gnus.org>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sun, 16 Jul 2017 19:51:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 26.0.50; plist functions give confusing errors on invalid plists
Date: Sun, 16 Jul 2017 21:50:27 +0200
(plist-put '(:foo 1 :bar) :zot 2)

Debugger entered--Lisp error: (wrong-type-argument listp (:foo 1 :bar))
  plist-put((:foo 1 :bar) :zot 2)
  eval((plist-put '(:foo 1 :bar) :zot 2) nil)
  elisp--eval-last-sexp(nil)
  eval-last-sexp(nil)
  funcall-interactively(eval-last-sexp nil)
  call-interactively(eval-last-sexp nil nil)
  command-execute(eval-last-sexp)

The error seems to say that '(:foo 1 :bar) isn't a list.  But the
problem is that it's not a valid plist, since it has an odd number of
elements.

So I think there should be a different error being signalled here.  (And
there isn't really a backwards compatibility issue here of introducing a
new error symbol: Emacs 26.1 started signalling errors for these lists;
previously it was fine having odd plists.)


In GNU Emacs 26.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
 of 2017-07-16 built on mouse
Repository revision: 45892db6f53cccc045da9c7215b467617c067f04
Windowing system distributor 'The X.Org Foundation', version 11.0.11903000
System Description:	Ubuntu 17.04


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





Added indication that bug 27726 blocks24655 Request was from Glenn Morris <rgm <at> gnu.org> to control <at> debbugs.gnu.org. (Mon, 17 Jul 2017 00:11:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#27726; Package emacs. (Sat, 02 Sep 2017 12:46:01 GMT) Full text and rfc822 format available.

Message #10 received at 27726 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 27726 <at> debbugs.gnu.org
Subject: Re: 26.0.50; plist functions give confusing errors on invalid plists
Date: Sat, 02 Sep 2017 15:45:00 +0300
unblock 24655 by 27726
thanks

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Sun, 16 Jul 2017 21:50:27 +0200
> 
> 
> (plist-put '(:foo 1 :bar) :zot 2)
> 
> Debugger entered--Lisp error: (wrong-type-argument listp (:foo 1 :bar))
>   plist-put((:foo 1 :bar) :zot 2)
>   eval((plist-put '(:foo 1 :bar) :zot 2) nil)
>   elisp--eval-last-sexp(nil)
>   eval-last-sexp(nil)
>   funcall-interactively(eval-last-sexp nil)
>   call-interactively(eval-last-sexp nil nil)
>   command-execute(eval-last-sexp)
> 
> The error seems to say that '(:foo 1 :bar) isn't a list.  But the
> problem is that it's not a valid plist, since it has an odd number of
> elements.
> 
> So I think there should be a different error being signalled here.  (And
> there isn't really a backwards compatibility issue here of introducing a
> new error symbol: Emacs 26.1 started signalling errors for these lists;
> previously it was fine having odd plists.)

Would someone please look into this bug?

In any case, I don't see why this should block Emacs 26.1, so I'm
unblocking it.

Thanks.




Removed indication that bug 27726 blocks Request was from Eli Zaretskii <eliz <at> gnu.org> to control <at> debbugs.gnu.org. (Sat, 02 Sep 2017 12:46:02 GMT) Full text and rfc822 format available.

Reply sent to Philipp Stephani <p.stephani2 <at> gmail.com>:
You have taken responsibility. (Sat, 02 Sep 2017 19:12:01 GMT) Full text and rfc822 format available.

Notification sent to Lars Ingebrigtsen <larsi <at> gnus.org>:
bug acknowledged by developer. (Sat, 02 Sep 2017 19:12:01 GMT) Full text and rfc822 format available.

Message #17 received at 27726-done <at> debbugs.gnu.org (full text, mbox):

From: Philipp Stephani <p.stephani2 <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 27726-done <at> debbugs.gnu.org
Subject: Re: bug#27726: 26.0.50; plist functions give confusing errors on
 invalid plists
Date: Sat, 02 Sep 2017 19:10:47 +0000
[Message part 1 (text/plain, inline)]
Eli Zaretskii <eliz <at> gnu.org> schrieb am Sa., 2. Sep. 2017 um 14:46 Uhr:

> unblock 24655 by 27726
> thanks
>
> > From: Lars Ingebrigtsen <larsi <at> gnus.org>
> > Date: Sun, 16 Jul 2017 21:50:27 +0200
> >
> >
> > (plist-put '(:foo 1 :bar) :zot 2)
> >
> > Debugger entered--Lisp error: (wrong-type-argument listp (:foo 1 :bar))
> >   plist-put((:foo 1 :bar) :zot 2)
> >   eval((plist-put '(:foo 1 :bar) :zot 2) nil)
> >   elisp--eval-last-sexp(nil)
> >   eval-last-sexp(nil)
> >   funcall-interactively(eval-last-sexp nil)
> >   call-interactively(eval-last-sexp nil nil)
> >   command-execute(eval-last-sexp)
> >
> > The error seems to say that '(:foo 1 :bar) isn't a list.  But the
> > problem is that it's not a valid plist, since it has an odd number of
> > elements.
> >
> > So I think there should be a different error being signalled here.  (And
> > there isn't really a backwards compatibility issue here of introducing a
> > new error symbol: Emacs 26.1 started signalling errors for these lists;
> > previously it was fine having odd plists.)
>
> Would someone please look into this bug?
>

I've installed commit  71766a45f1 to improve the message.
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#27726; Package emacs. (Sat, 02 Sep 2017 19:25:02 GMT) Full text and rfc822 format available.

Message #20 received at 27726 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Philipp Stephani <p.stephani2 <at> gmail.com>
Cc: larsi <at> gnus.org, 27726 <at> debbugs.gnu.org
Subject: Re: bug#27726: 26.0.50; plist functions give confusing errors on
 invalid plists
Date: Sat, 02 Sep 2017 22:23:58 +0300
> From: Philipp Stephani <p.stephani2 <at> gmail.com>
> Date: Sat, 02 Sep 2017 19:10:47 +0000
> Cc: 27726-done <at> debbugs.gnu.org
> 
> I've installed commit 71766a45f1 to improve the message.

Thanks.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sun, 01 Oct 2017 11:24:05 GMT) Full text and rfc822 format available.

This bug report was last modified 6 years and 207 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.