From: Bart Schaefer <schaefer@brasslantern.com>
To: Vincent Lefevre <vincent@vinc17.org>, zsh-users@sunsite.dk
Subject: Re: Problem with zip completion
Date: Wed, 17 Oct 2001 17:57:57 -0700 [thread overview]
Message-ID: <011017175757.ZM5134@candle.brasslantern.com> (raw)
In-Reply-To: <20011018011512.C17952@greux.loria.fr>
On Oct 18, 1:15am, Vincent Lefevre wrote:
> Subject: Re: Problem with zip completion
> On Wed, Oct 17, 2001 at 17:44:46 +0000, Bart Schaefer wrote:
> > Actually, having given it a moment's more thought, it would probably be
> > better to use
> >
> > TRAPCLD() { [[ -t 0 ]] && precmd }
> >
> > or even
> >
> > TRAPCLD() { [[ -o interactive && -t 0 ]] && precmd }
>
> Why? If TRAPCLD is called when stdout is redirected (thus, not necessarily
> attached to a tty), I still want to be able to write to the tty (here, to
> change the terminal title).
It depends on where and how you're defining the TRAPCLD function, I guess.
My assumption would be that if stdout is redirected, then the child that's
exiting must not be a child of the top-level interactive shell, and thus
changing the terminal title would at best be a waste of effort.
Remember, it's the stdout of the *parent* of the exiting job that we're
testing here.
next prev parent reply other threads:[~2001-10-18 0:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 14:47 Vincent Lefevre
2001-10-17 15:43 ` Bart Schaefer
2001-10-17 16:22 ` Oliver Kiddle
[not found] ` <20011017111333.A32235@dman.com>
2001-10-17 16:21 ` Vincent Lefevre
2001-10-17 16:49 ` Bart Schaefer
2001-10-17 17:11 ` Vincent Lefevre
2001-10-17 17:24 ` Bart Schaefer
2001-10-17 17:44 ` Bart Schaefer
2001-10-17 23:15 ` Vincent Lefevre
2001-10-18 0:57 ` Bart Schaefer [this message]
2001-10-18 2:13 ` Vincent Lefevre
2001-10-18 4:46 ` Sweth Chandramouli
2001-10-18 9:05 ` Vincent Lefevre
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=011017175757.ZM5134@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=vincent@vinc17.org \
--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).