unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gemini Lasswell <gazally@runbox.com>
Cc: 24779@debbugs.gnu.org
Subject: bug#24779: 26.0.50; Incorrect Edebug spec for define-skeleton
Date: Fri, 23 Aug 2019 02:22:07 +0200	[thread overview]
Message-ID: <878srkbuj4.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87v9vnhb4l.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Sat, 27 Jul 2019 15:15:22 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I'm able to reproduce that, too, and adding "|" to the list of strings
> in the spec seems to fix this.  I know nothing about any of this,
> though, so...  Is this the right thing to do?
>
> diff --git a/lisp/skeleton.el b/lisp/skeleton.el
> index bce73d6bfe..67fc4aae15 100644
> --- a/lisp/skeleton.el
> +++ b/lisp/skeleton.el
> @@ -105,8 +105,8 @@ skeleton-point
>  (defvar skeleton-regions)
>
>  (def-edebug-spec skeleton-edebug-spec
> -  ([&or null stringp (stringp &rest stringp) [[&not atom] def-form]]
> -   &rest &or "n" "_" "-" ">" "@" "&" "!" "resume:"
> +  ([&or null stringp (stringp &rest stringp) [[&not atom] sexp]]
> +   &rest &or "n" "_" "-" ">" "@" "&" "!" "|" "resume:"
>     ("quote" def-form) skeleton-edebug-spec def-form))
>  ;;;###autoload
>  (defmacro define-skeleton (command documentation &rest skeleton)

There weren't any comments, and this does seem to fix the test cases, so
I've applied this now.

But like I said, I don't really know this area, so if this is the wrong
thing to do, feel free to revert.

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





      parent reply	other threads:[~2019-08-23  0:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-23 20:37 bug#24779: 26.0.50; Incorrect Edebug spec for define-skeleton Gemini Lasswell
2019-07-27 13:15 ` Lars Ingebrigtsen
2019-07-27 13:17   ` Lars Ingebrigtsen
2019-08-23  0:22   ` Lars Ingebrigtsen [this message]

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=878srkbuj4.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=24779@debbugs.gnu.org \
    --cc=gazally@runbox.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).