SH_GLOB influence on a script and on an autoload function

SH_GLOB influence on a script and on an autoload function

[Sebastian Gniazdowski]

Hello
Below is a simple script (save to file rtest1) that works well despite
SH_GLOB should or could stop the pattern from parsing. The same
doesn't work for autoload. If one does:

setopt shglob
FPATH=$FPATH:`pwd`
autoload rtest1
rtest1

then error occurs:

rtest1:8: parse error near `('

Why does this happen? Probably no workaround for this?

Best regards,
Sebastian Gniazdowski

================================

#!/usr/local/bin/zsh-5.2-dev-1 --shglob

emulate -LR zsh
setopt extendedglob

tmp="something txt=1234 something"

if [[ "$tmp" = *txt=(#b)([0-9]##)(|[[:blank:]]*) ]]; then
    echo "Matched, match is: $match[1]"
else
    echo "No match"
fi

Re: SH_GLOB influence on a script and on an autoload function

[Bart Schaefer]

On Jun 11,  7:11am, Sebastian Gniazdowski wrote:
}
} Below is a simple script (save to file rtest1) that works well despite
} SH_GLOB should or could stop the pattern from parsing. The same
} doesn't work for autoload.

A script is executed line by line as it is parsed.  An autoloaded function
is fully parsed first, then executed.  Hence in the script, the "emulate"
command resets the parsing rules before the expression is encountered.

This is one of the drawbacks to attempting to accurately emulate parsing
rules that are inherently contradictory.

} setopt shglob
} FPATH=$FPATH:`pwd`
} autoload rtest1
} rtest1
} 
} Probably no workaround for this?

In "recent" zsh (since roughly 2009) you can do this:

    emulate zsh -c 'autoload rtest1'

but of course you have to know a priori what emulation mode the function
is going to want.

Re: SH_GLOB influence on a script and on an autoload function

[Sebastian Gniazdowski]

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

On 11 June 2016 at 19:14, Bart Schaefer <schaefer@brasslantern.com> wrote:

> This is one of the drawbacks to attempting to accurately emulate parsing
> rules that are inherently contradictory.


It seems that pat="<full-featured zsh pattern here>" and then using
GLOB_SUBST via $~pat with SH_GLOB temporarily turned off should solve this?
But what about (N[1]) etc. modifiers... I'm thinking about a far away
possibility that one could fully work with emulate sh, having completions
not reporting errors.

Best regards,
Sebastian Gniazdowski

Re: SH_GLOB influence on a script and on an autoload function

[Bart Schaefer]

On Sep 7, 12:39pm, Sebastian Gniazdowski wrote:
}
} It seems that pat="<full-featured zsh pattern here>" and then using
} GLOB_SUBST via $~pat with SH_GLOB temporarily turned off should solve this?
} But what about (N[1]) etc. modifiers...

If SH_GLOB is turned off, glob qualifiers are handled like any other
part of the pattern, so no difference here.

I'm thinking about a far away
} possibility that one could fully work with emulate sh, having completions
} not reporting errors.

I've lost track of this thread.  What present error is being addressed?
Seems to me that completion uses zsh syntax internally, so you'd be more
likely to have an error in the other direction, i.e., the command line
expects SH_GLOB but the internals treat it like zsh ...?

Re: SH_GLOB influence on a script and on an autoload function

[Sebastian Gniazdowski]

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

On 7 September 2016 at 20:28, Bart Schaefer <schaefer@brasslantern.com>
wrote:

> On Sep 7, 12:39pm, Sebastian Gniazdowski wrote:
> I'm thinking about a far away
> } possibility that one could fully work with emulate sh, having completions
> } not reporting errors.
>
> I've lost track of this thread.  What present error is being addressed?
> Seems to me that completion uses zsh syntax internally, so you'd be more
> likely to have an error in the other direction, i.e., the command line
> expects SH_GLOB but the internals treat it like zsh ...?
>

I sometimes think about making emulate sh a possible interactive setting.
Let it just be that one would be able to temporarily switch to sh to check
something and then switch back. Currently there are errors reported:

# zsh -f
% autoload compinit
% compinit
% cd<Tab>
Applications/                      PRINT/
Save/                              github/                            test/
...
<Ctrl-C>
% emulate sh
% cd<Tab>
_cd:63: bad math expression: operator expected at `tmpcdpath '
_description:63: bad math expression: operator expected at `comp_ignor...'
_next_label:63: bad math expression: operator expected at `funcstack ...'
_description:63: bad math expression: operator expected at `comp_ignor...'
_path_files:63: bad math expression: operator expected at `pfx '
_path_files:63: bad math expression: operator expected at `prepaths '
_path_files:63: bad math expression: operator expected at `ignore '
_path_files:63: bad math expression: operator expected at `ignore'
_main_complete:332: bad math expression: operator expected at `lastdescr'
_main_complete:372: bad math expression: operator expected at
`comp_color...'

Best regards,
Sebastian Gniazdowski

Re: SH_GLOB influence on a script and on an autoload function

[Bart Schaefer]

On Sep 7,  9:01pm, Sebastian Gniazdowski wrote:
}
} I sometimes think about making emulate sh a possible interactive setting.
} Let it just be that one would be able to temporarily switch to sh to check
} something and then switch back. Currently there are errors reported

Oh.  Try this:

    emulate zsh -c 'autoload compinit'

This makes zsh emulation "sticky" for all of the completion functions,
and all the functions loaded from the completion functions, etc., etc.,
which assures those functions are parsed in zsh native mode no matter
what setopts may end up in effect during their execution.