From: Bart Schaefer <schaefer@brasslantern.com>
To: zw <zsh-workers@sunsite.dk>
Subject: Re: jobs not listing all commands
Date: Wed, 18 Feb 2004 06:02:17 +0000 [thread overview]
Message-ID: <1040218060217.ZM12569@candle.brasslantern.com> (raw)
In-Reply-To: <20040218002553.GA1429@mail.guild.uwa.edu.au>
On Feb 18, 8:25am, James Devenish wrote:
} Subject: Re: jobs not listing all commands
}
} > Prompts don't update between two interactive commands, ever, no matter
} > what the reason. The prompt string is computed when ZLE initializes
} > (just before it is first printed) and is thereafter used verbatim until
} > the next re-initialize.
}
} I'm a bit confused by both of the both comments.
What I mean by "between two interactive commands" is "after one command
finishes (and the prompt is printed) but before the next one _begins_
(i.e. when accept-line is executed)."
The empty command is still a command for this purpose.
} Firstly, %j works "as a user would expect" for me in zsh v4.1.1 (i.e.
} I get the behaviour that Felix expects).
I suspect you really don't. Try this:
zsh -f
% PS1='njobs:%j %'
njobs:0 % sleep 60 &
njobs:1 % sleep 10 &
njobs:2 %
Now wait 10 seconds. You should see:
[2] + done sleep 10
njobs:2 %
Note that the prompt has not changed. If you now hit return, it should
change to:
njobs:1 %
} Secondly, %t, %@, %T, %*, %? (etc.) work as expected in PS1
I think you'll find they work the same as %j in the example above.
next prev parent reply other threads:[~2004-02-18 6:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 7:58 Felix Rosencrantz
2004-02-17 10:41 ` Peter Stephenson
2004-02-17 22:14 ` Bart Schaefer
2004-02-18 0:25 ` James Devenish
2004-02-18 0:41 ` Wayne Davison
2004-02-18 6:02 ` Bart Schaefer [this message]
2004-02-18 10:24 ` Peter Stephenson
2004-02-18 17:47 ` Bart Schaefer
2004-02-18 22:02 ` Peter Stephenson
2004-02-20 15:21 ` PATCH: ptmx part 2 Peter Stephenson
2004-02-19 15:22 ` jobs not listing all commands Felix Rosencrantz
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=1040218060217.ZM12569@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).