GNU bug report logs -
#53518
29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols
Previous Next
Reported by: Sean Whitton <spwhitton <at> spwhitton.name>
Date: Tue, 25 Jan 2022 05:34:02 UTC
Severity: normal
Found in version 29.0.50
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #8 received at 53518 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello again,
On Mon 24 Jan 2022 at 06:39pm -08, Jim Porter wrote:
> I just noticed a small bit of breakage with this. It's no longer
> possible to refer to Lisp functions in Eshell like so:
>
> #'upcase
>
> Eshell explicitly supports this construct (see `eshell-lisp-regexp'),
> though it doesn't appear to be documented in the manual. Currently, this
> syntax is only occasionally useful, but I'm working on a patch series
> where it'll likely become a lot more common. My patches will add support
> for piping to Lisp functions, so that you can do the following, for example:
>
> $ echo hi | #'upcase
> HI
Out of curiosity, why is there a need for the sharpquote? Why not just
'echo hi | upcase'? Is it to do with requesting the new piping?
> It looks like the breakage in parsing #'upcase is the result of
> `eshell-parse-external-pipeline' trying to skip over args like '*|'
> (with the quotes). However, it sees the single-quote in #'upcase and
> then calls `eshell-parse-literal-quote', resulting in the error message:
>
> Expecting completion of delimiter ' ...
Here is a patch which has `eshell-parse-external-pipeline' try skipping
over sharp-quoted symbols before trying to skip over single-quoted
strings.
--
Sean Whitton
[0001-Fix-input-of-sharp-quoted-symbols-in-Eshell-with-em-.patch (text/x-diff, attachment)]
This bug report was last modified 3 years and 117 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.