From: Dominik Vogt <dominik.vogt@gmx.de>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: time command with shell builtins
Date: Thu, 2 Feb 2023 19:10:26 +0100 [thread overview]
Message-ID: <Y9v8kuT3/Qyzxtj7@localhost> (raw)
In-Reply-To: <Y9Ko+7GqksX+LKww@localhost>
On Thu, Jan 26, 2023 at 05:23:23PM +0100, Dominik Vogt wrote:
> On Wed, Jan 25, 2023 at 01:42:43AM +0100, Dominik Vogt wrote:
> > On Tue, Jan 24, 2023 at 03:36:51PM -0800, Bart Schaefer wrote:
> > > On Tue, Jan 24, 2023 at 3:14 PM Dominik Vogt <dominik.vogt@gmx.de> wrote:
> > > >
> > > > As far as I understand there's no reliable access to
> > > > which command is being executed in preexec.
> > >
> > > There's reliable access to what the user typed and to what that
> > > expands to after alias replacement. What else would you be looking
> > > for?
> >
> > Well, it's more or less "if whatever is being executed is
> > interactive, I'm not interested in the time". This is impossible
> > to guess from the command name, except in some manually specified
> > cases. Maye a simple "if command is one of emacs, vi, vim, sleep,
> > mutt, visudo, bash, zsh, sh" is good enough. Or I just get used to
> > having unnecessary information in the prompt.
>
> Is there a more elegant way to chek if the command is in a
> blacklist than this one?
>
> -- snip --
> _zsh_recordtime_skip_list=( emacs vi vim zsh bash sh viduso mutt sleep xemacs )
> function preexec_recordtime() {
> if [[ -z "${1:|_zsh_recordtime_skip_list}" ]]; then
> psvar[2]=''
> ...
> }
> -- snip --
Well, is there a way to detect inside preexec() wether a command
is handled by the shell or some external binary? The usual
REPORTTIME mechanism works for external commands, so using
preexec/precmd to print run time for shell builtins is good enough.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
next prev parent reply other threads:[~2023-02-02 18:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 13:40 Dominik Vogt
2023-01-23 13:42 ` Roman Perepelitsa
2023-01-23 14:17 ` zeurkous
2023-01-23 14:23 ` Roman Perepelitsa
2023-01-23 14:40 ` zeurkous
2023-01-23 14:28 ` Dominik Vogt
2023-01-23 14:46 ` zeurkous
2023-01-23 16:31 ` Bart Schaefer
2023-01-23 18:31 ` Mikael Magnusson
2023-01-23 18:49 ` Dominik Vogt
2023-01-24 9:32 ` Mikael Magnusson
2023-01-24 10:48 ` Dominik Vogt
2023-01-24 23:12 ` Dominik Vogt
2023-01-24 23:36 ` Bart Schaefer
[not found] ` <Y9B7A8dWLiZNXKfW@localhost>
2023-01-26 16:23 ` Dominik Vogt
2023-01-26 16:56 ` Bart Schaefer
2023-01-26 17:26 ` Dominik Vogt
2023-01-26 17:40 ` Bart Schaefer
2023-02-02 18:10 ` Dominik Vogt [this message]
2023-02-02 18:28 ` Bart Schaefer
2023-02-02 19:15 ` Dominik Vogt
2023-02-02 19:15 ` Dominik Vogt
2023-02-02 19:31 ` Bart Schaefer
2023-01-24 23:32 ` Bart Schaefer
2023-01-25 7:43 ` Mikael Magnusson
2023-01-25 12:58 ` Dominik Vogt
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=Y9v8kuT3/Qyzxtj7@localhost \
--to=dominik.vogt@gmx.de \
--cc=zsh-users@zsh.org \
/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).