[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols
From: |
Sean Whitton |
Subject: |
bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols |
Date: |
Tue, 25 Jan 2022 01:50:35 -0700 |
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
Description: Text Data
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, (continued)
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Michael Albinus, 2022/01/24
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Sean Whitton, 2022/01/24
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Sean Whitton, 2022/01/24
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Lars Ingebrigtsen, 2022/01/24
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Sean Whitton, 2022/01/24
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Lars Ingebrigtsen, 2022/01/24
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Sean Whitton, 2022/01/24
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Lars Ingebrigtsen, 2022/01/24
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Jim Porter, 2022/01/24
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Sean Whitton, 2022/01/25
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols,
Sean Whitton <=
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Lars Ingebrigtsen, 2022/01/25
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Sean Whitton, 2022/01/25
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Jim Porter, 2022/01/26
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Lars Ingebrigtsen, 2022/01/26
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Jim Porter, 2022/01/25
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Sean Whitton, 2022/01/25
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Jim Porter, 2022/01/25
- bug#53518: 29.0.50; em-extpipe breaks input of sharp-quoted Lisp symbols, Sean Whitton, 2022/01/25
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Michael Albinus, 2022/01/25
- bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining, Jim Porter, 2022/01/25