Unexpected globbing when expanding history

Unexpected globbing when expanding history

[Roman Perepelitsa]

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

This came my way via https://github.com/romkatv/zsh4humans/issues/313

    % zsh -f
    % fc -p =(print '\u30C7')
    % : "${history[@]}"
    zsh: no matches found: \M-c\n
    % noglob : "${history[@]}"

Roman

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

Re: Unexpected globbing when expanding history

[Mikael Magnusson]

On Fri, Jun 14, 2024 at 6:32 PM Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>
> This came my way via https://github.com/romkatv/zsh4humans/issues/313
>
>     % zsh -f
>     % fc -p =(print '\u30C7')
>     % : "${history[@]}"
>     zsh: no matches found: \M-c\n
>     % noglob : "${history[@]}"

That is a corrupted history file, which zsh will warn about when
debugging is enabled:
 hist.c:3771: bad(2) wordsplit reading history: \M-c\n
at: \M-c\n
word: \M-c^@

History files are stored in metafied form, this character probably
happens to correspond to the metafied form of the internal token for
some glob symbol.

-- 
Mikael Magnusson

Re: Unexpected globbing when expanding history

[Mark J. Reed]

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

On Fri, Jun 14, 2024 at 1:15 PM Mikael Magnusson <mikachu@gmail.com> wrote:

> History files are stored in metafied form,


But how does a literal character from the command turn into a token in the
metafied form? That seems like a confusion of levels that shouldn't be
possible.

FWIW, the problem goes away after starting a new shell, even keeping the
histfile. So the corruption doesn't seem to be happening on disk.
-- 
Mark J. Reed <markjreed@gmail.com>

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

Re: Unexpected globbing when expanding history

[Mikael Magnusson]

On Fri, Jun 14, 2024 at 10:37 PM Mark J. Reed <markjreed@gmail.com> wrote:
>
>
> On Fri, Jun 14, 2024 at 1:15 PM Mikael Magnusson <mikachu@gmail.com> wrote:
>>
>> History files are stored in metafied form,
>
>
> But how does a literal character from the command turn into a token in the metafied form? That seems like a confusion of levels that shouldn't be possible.

fc -p takes as the first argument the path to a zsh format histfile,
which on this command line is created with contents that are not a
valid zsh format histfile.

-- 
Mikael Magnusson