GNU bug report logs - #29156
25.3; eshell/kill does not understand -<signal>

Previous Next

Package: emacs;

Reported by: Pierre Neidhardt <ambrevar <at> gmail.com>

Date: Sun, 5 Nov 2017 11:32:02 UTC

Severity: normal

Tags: confirmed, easy, fixed

Found in version 25.3

Fixed in version 27.1

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eric Skoglund <eric <at> pagefault.se>
To: 29156 <at> debbugs.gnu.org,  29156 <at> https:
Cc: Noam Postavsky <npostavs <at> gmail.com>, Pierre Neidhardt <ambrevar <at> gmail.com>
Subject: bug#29156: 25.3; eshell/kill does not understand -<signal>, [PATCH] Make eshell/kill handle -<signal> and -<SIGNALNAME>
Date: Sat, 17 Mar 2018 20:19:27 +0100
Noam Postavsky <npostavs <at> gmail.com> writes:
>>
>> Saw that Eli also agreed, for future reference when do we want to use
>> `make-symbol` vs `intern`?
>
> Usually, `make-symbol' is only for macros, where you want a symbol that
> is not `eq' to any other.  Sometimes it's handy for making a unique
> object at run-time.  In this case, since we only care about the symbol
> name, it doesn't really matter, it's just a bit surprising to see it
> because it's usually a mistake in a non-macro context.

Thanks for the clarification!

PS. Not sure why I'm not seeing my replies in debbugs-gnu so sorry for the
extra work in forwarding them. Tried changing the To header to the bug
mail adress, let's se if that works.




This bug report was last modified 7 years and 63 days ago.

Previous Next


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