How reliable is %x prompt expansion?

How reliable is %x prompt expansion?

[Sebastian Gniazdowski]

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

Hi , currently, I'm doing:

0=${${(M)${0::=${(%):-%x}}:#/*}:-$PWD/$0}

on entry to each function or script. It works well, however, I'm planning
to update the plugin standard recommendation for $0 support and I'm
thinking if there are any circumstances where it might fail? $0 is to point
to the script/function source.

Also, I'm looking for a way to disable the promptsubst/print -P for a
single variable, something like `print -P ${(!%)var}`, where !% is to
denote that prompt expansion should not be done.

-- 
Best regards,
Sebastian Gniazdowski

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

Re: How reliable is %x prompt expansion?

[Roman Perepelitsa]

On Mon, Feb 13, 2023 at 5:27 PM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> Hi , currently, I'm doing:
>
> 0=${${(M)${0::=${(%):-%x}}:#/*}:-$PWD/$0}
>
> on entry to each function or script.

FWIW, to get the name of the current file I use $ZSH_SCRIPT in
executable scripts and ${(%):-%x} in sourced files. To get the name of
the current function I use $0 (after `emulate -L zsh` to make sure
posix_argzero is not in effect).

> Also, I'm looking for a way to disable the promptsubst/print -P for
> a single variable, something like `print -P ${(!%)var}`, where !%
> is to denote that prompt expansion should not be done.

I do it like this:

    print -P -- ${var//\%/%%}

A more useful example would be:

  if [[ -e $file ]]; then
    print -Pru2 -- "%F{red}error%f: file already exists: %U${file//\%/%%}%f"
  fi

Note ${file//\%/%%}.

Roman.