[debbugs-tracker] bug#21928: closed (25.0.50; verilog-mode.el fails to compile, Symbol’s function definition is void: \,@)

[GNU bug Tracking System]

Your message dated Tue, 17 Nov 2015 01:28:21 +0100
with message-id <address@hidden>
and subject line Re: bug#21928: 25.0.50; verilog-mode.el fails to compile, 
Symbol’s function definition is void: \,@
has caused the debbugs.gnu.org bug report #21928,
regarding 25.0.50; verilog-mode.el fails to compile, Symbol’s function 
definition is void: \,@
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
21928: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21928
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 25.0.50; verilog-mode.el fails to compile, Symbol’s function definition is void: \,@
>
>
>
>
> Date: 
>
> Sun, 15 Nov 2015 19:32:11 -0800
>
>
>
>
> Hi,
>
> There's a compile error in verilog-mode.el. I believe it was introduced
> by commit 353f5e76641c338dc4bfe0ac8e9aa84d23bac1fe.
>
> Fixed with the following path. Not sure if it's correct, stefan can
> probably tell tho.
>
> ----------------------------patch start
> diff --git a/lisp/progmodes/verilog-mode.el
> b/lisp/progmodes/verilog-mode.el
> index fa93633..3081060 100644
> --- a/lisp/progmodes/verilog-mode.el
> +++ b/lisp/progmodes/verilog-mode.el
> @@ -3237,7 +3237,7 @@ verilog-save-buffer-state
>    `(let ((inhibit-point-motion-hooks t)
>           (verilog-no-change-functions t))
>       ,(if (fboundp 'with-silent-modifications)
> -          (with-silent-modifications ,@body)
> +          `(with-silent-modifications ,@body)
>          ;; From c-save-buffer-state
>          `(let* ((modified (buffer-modified-p))
>                  (buffer-undo-list t)
> ----------------------------patch end
>
> Best,
> Samer
>
>
>
> --- End Message ---

--- Begin Message --- Subject: Re: bug#21928: 25.0.50; verilog-mode.el fails to compile, Symbol’s function definition is void: \,@ Date: Tue, 17 Nov 2015 01:28:21 +0100

On Mon, Nov 16, 2015 at 4:32 AM, Samer Masterson <address@hidden> wrote:

> Fixed with the following path. Not sure if it's correct, stefan can
> probably tell tho.

I hope it is the correct patch, as I fixed it yesterday with a patch identical to yours.

Commit 937565268a5dc3377d4c9bff6d48eb3645a77160

--- End Message ---