emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#71574: closed (30.0.50; [PATCH] Fix wrong-type-argument in php-ts-mo


From: GNU bug Tracking System
Subject: bug#71574: closed (30.0.50; [PATCH] Fix wrong-type-argument in php-ts-mode--webserver-read-args)
Date: Sat, 15 Jun 2024 18:59:02 +0000

Your message dated Sat, 15 Jun 2024 21:55:50 +0300
with message-id <86zfrmrq6h.fsf@gnu.org>
and subject line Re: bug#71574: 30.0.50; [PATCH] Fix wrong-type-argument in 
php-ts-mode--webserver-read-args
has caused the debbugs.gnu.org bug report #71574,
regarding 30.0.50; [PATCH] Fix wrong-type-argument in 
php-ts-mode--webserver-read-args
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
71574: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=71574
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 30.0.50; [PATCH] Fix wrong-type-argument in php-ts-mode--webserver-read-args Date: Sat, 15 Jun 2024 19:53:18 +0200
Ciao,
php-ts-mode-run-php-webserver throws an error if the current buffer is not 
associated with a file. This is due to php-ts-mode--webserver-read-args. php-
ts-mode--webserver-read-args now uses default-directory if buffer-file-name 
returns nil. 
The included patch fixes this.

Thanks.
Vincenzo

Attachment: 0001-Fix-wrong-type-argument-in-php-ts-mode-webserver-rea.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#71574: 30.0.50; [PATCH] Fix wrong-type-argument in php-ts-mode--webserver-read-args Date: Sat, 15 Jun 2024 21:55:50 +0300
> From: Vincenzo Pupillo <v.pupillo@gmail.com>
> Date: Sat, 15 Jun 2024 19:53:18 +0200
> 
> php-ts-mode-run-php-webserver throws an error if the current buffer is not 
> associated with a file. This is due to php-ts-mode--webserver-read-args. php-
> ts-mode--webserver-read-args now uses default-directory if buffer-file-name 
> returns nil. 
> The included patch fixes this.

Thanks, installed (but please note the minor changes I made in your
commit log message, and try to follow this style in the future).

I'm closing this bug.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]