Quote of % in a completed func name?

Quote of % in a completed func name?

[Sebastian Gniazdowski]

[-- Attachment #1: Type: text/plain, Size: 277 bytes --]

Hi
I have created some %functs… I complete them to see that they cannot
execute:
14:56[/home/q]3# %exa
fg: job not found: exa

Could the % be somehow be quoted after completing? (\%exa works and calls
the %func functon)


-- 
Best regards,
Sebastian Gniazdowski

[-- Attachment #2: Type: text/html, Size: 896 bytes --]

Re: Quote of % in a completed func name?

[Bart Schaefer]

On Mon, Sep 18, 2023 at 6:42 AM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> Could the % be somehow be quoted after completing? (\%exa works and calls the %func functon)

Firstly, to prevent conflicts you can remove "jobs" from the same
completion zstyle I sent earlier for leading colons in command
completion.

For command execution, you're probably best going with a
zle-line-finish hook that does a search-and-replace, e.g.

BUFFER=${(*)BUFFER//#%(#b)(${(kj:|:)~functions[(I)%*]})/\\\\$match[1]}

(remove (*) and setopt extendedglob for older zsh)

Re: Quote of % in a completed func name?

[Bart Schaefer]

On Mon, Sep 18, 2023 at 7:56 AM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> BUFFER=${(*)BUFFER//#%(#b)(${(kj:|:)~functions[(I)%*]})/\\\\$match[1]}
>
> (remove (*) and setopt extendedglob for older zsh)

Oh, remove the #% too, that was a leftover from testing, you want to
match anywhere in the buffer not the whole buffer.

Re: Quote of % in a completed func name?

[Sebastian Gniazdowski]

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

it works, thanks. Question: what does the * flag do in ${(*)BUFFER … …?

On Mon, 18 Sept 2023 at 09:56, Bart Schaefer <schaefer@brasslantern.com>
wrote:

> On Mon, Sep 18, 2023 at 6:42 AM Sebastian Gniazdowski
> <sgniazdowski@gmail.com> wrote:
> >
> > Could the % be somehow be quoted after completing? (\%exa works and
> calls the %func functon)
>
> Firstly, to prevent conflicts you can remove "jobs" from the same
> completion zstyle I sent earlier for leading colons in command
> completion.
>
> For command execution, you're probably best going with a
> zle-line-finish hook that does a search-and-replace, e.g.
>
> BUFFER=${(*)BUFFER//#%(#b)(${(kj:|:)~functions[(I)%*]})/\\\\$match[1]}
>
> (remove (*) and setopt extendedglob for older zsh)
>


-- 
Best regards,
Sebastian Gniazdowski

[-- Attachment #2: Type: text/html, Size: 1458 bytes --]

Re: Quote of % in a completed func name?

[Bart Schaefer]

On Tue, Sep 19, 2023 at 8:06 AM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> it works, thanks. Question: what does the * flag do in ${(*)BUFFER … …?

Turns on extendedglob temporarily. See the NEWS file in 5.9

Re: Quote of % in a completed func name?

[Sebastian Gniazdowski]

[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]

other thing i've noted: you used ~ flag not in the idiomatic way, ie. not
as (~j:|:) but before the var: (j:|:)~functions. Why?

On Tue, 19 Sept 2023 at 17:08, Sebastian Gniazdowski <sgniazdowski@gmail.com>
wrote:

> it works, thanks. Question: what does the * flag do in ${(*)BUFFER … …?
>
> On Mon, 18 Sept 2023 at 09:56, Bart Schaefer <schaefer@brasslantern.com>
> wrote:
>
>> On Mon, Sep 18, 2023 at 6:42 AM Sebastian Gniazdowski
>> <sgniazdowski@gmail.com> wrote:
>> >
>> > Could the % be somehow be quoted after completing? (\%exa works and
>> calls the %func functon)
>>
>> Firstly, to prevent conflicts you can remove "jobs" from the same
>> completion zstyle I sent earlier for leading colons in command
>> completion.
>>
>> For command execution, you're probably best going with a
>> zle-line-finish hook that does a search-and-replace, e.g.
>>
>> BUFFER=${(*)BUFFER//#%(#b)(${(kj:|:)~functions[(I)%*]})/\\\\$match[1]}
>>
>> (remove (*) and setopt extendedglob for older zsh)
>>
>
>
> --
> Best regards,
> Sebastian Gniazdowski
>
>

-- 
Best regards,
Sebastian Gniazdowski

[-- Attachment #2: Type: text/html, Size: 2274 bytes --]

Re: Quote of % in a completed func name?

[Bart Schaefer]

On Tue, Sep 19, 2023 at 8:13 AM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> other thing i've noted: you used ~ flag not in the idiomatic way, ie. not as (~j:|:) but before the var: (j:|:)~functions. Why?

No reason other than that I forgot it was possible to put it inside
the parentheses.