From: "Joshua Symons" <vmcore@mysun.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@sunsite.dk
Subject: Re: Preexec & Printf
Date: Thu, 25 Apr 2002 20:07:20 -0500 [thread overview]
Message-ID: <1eed22689c.2689c1eed2@mysun.com> (raw)
From: Bart Schaefer <schaefer@brasslantern.com>
Date: Thursday, April 25, 2002 8:01 pm
Subject: Re: Preexec & Printf
> On Thu, 25 Apr 2002, Joshua Symons wrote:
>
> > I have a pretty generic problem, but I can't seem to make my way
> around> it.
>
> Re-read the documentation for the preexec function. In particular:
>
> > preexec () {
> > print -Pn "\e]0;%m:%l - $* \a"
> > }
>
> You almost certainly want to refer to $1 rather than to $*. To
> remove the
> quotes from the string, you probably want to use ${(z)1}.
>
> > $ZSH_VERSION = 3.1.9
>
> You might also want to upgrade to zsh 4.0.4, which has been out for a
> while now.
>
>
Same results:
[(ichirou:151:pts/33)~ %] which preexec
preexec () {
print -Pn "\e]0;%m:%l - ${(z)1} \a"
}
[(ichirou:152:pts/33)~ %] printf '^[[32;40mwith quotes\n'
[32;40mwith quotes
' with quotes
[(ichirou:153:pts/33)~ %] unfunction preexec
[(ichirou:154:pts/33)~ %] printf '^[[32;40mwith quotes\n'
with quotes
Additionally, I will upgrade to 4.0.4 as well, but I don't believe that
will fix this current issue.
-Josh-
next reply other threads:[~2002-04-26 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 1:07 Joshua Symons [this message]
2002-04-26 1:16 ` Bart Schaefer
2002-04-26 1:19 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 2:10 Joshua Symons
2002-04-26 1:54 Joshua Symons
2002-04-26 2:06 ` Bart Schaefer
2002-04-26 1:31 Joshua Symons
2002-04-26 1:47 ` Geoff Wing
2002-04-26 1:25 Joshua Symons
2002-04-26 1:45 ` Bart Schaefer
2002-04-26 9:21 ` Oliver Kiddle
2002-04-26 0:47 Joshua Symons
2002-04-26 1:01 ` Bart Schaefer
2002-04-26 1:22 ` Geoff Wing
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=1eed22689c.2689c1eed2@mysun.com \
--to=vmcore@mysun.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@sunsite.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).