zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Prompt expansion: $((%)foo} != $(print -P $foo)
Date: Mon, 20 Mar 2000 13:04:13 +0100 (MET)	[thread overview]
Message-ID: <200003201204.NAA10508@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 20 Mar 2000 06:45:19 +0000


Bart Schaefer wrote:

> The order in which parameter expansion vs. prompt %x expansion takes place
> appears to be reversed for ${(%)...} and $(print -P ...).  This is visible
> in this situation:
> 
> zsh% setopt promptsubst
> zsh% PS1='%$[COLUMNS-20]>...%% >some text here %% '
> some text here %
> 
> The prompt and the output of "print -P" are truncated at COLUMNS-20, so in
> that case the $[...] was expanded before %N>...> was parsed.  However:
> 
> some text here % echo ${(%)PS1}
> [COLUMNS-1]some text here %
> 
> There, %$ was taken as a prompt token (and ignored) before parameters were
> expanded.  A workaround is to use ${(%)${(e)PS1}}, but of course that's not
> right when promptsubst is NOT set.

Err... that's what (%%) is for. From the docs:

item(tt(%))(
Expand all tt(%) escapes in the resulting words in the same way as in
prompts (see noderef(Prompt Expansion)). If this flag is given twice,
full prompt expansion is done on the resulting words, depending on the 
setting of the tt(PROMPT_PERCENT), tt(PROMPT_SUBST) and
tt(PROMPT_BANG) options.
)


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-03-20 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 12:04 Sven Wischnowsky [this message]
2000-03-20 17:11 ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2000-03-20  6:45 Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200003201204.NAA10508@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).