From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21821 invoked by alias); 5 Dec 2012 14:35:27 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 17462 Received: (qmail 11217 invoked from network); 5 Dec 2012 14:35:24 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, RCVD_NUMERIC_HELO,SPF_HELO_PASS autolearn=no version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at m.gmane.org designates 80.91.229.3 as permitted sender) X-Injected-Via-Gmane: http://gmane.org/ To: zsh-users@zsh.org From: Yuri D'Elia Subject: Re: Problems with precmd/urxvt Date: Wed, 05 Dec 2012 15:35:07 +0100 Message-ID: References: <121203074835.ZM20740@torch.brasslantern.com> <121204080149.ZM22046@torch.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 193.106.183.18 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 In-Reply-To: <121204080149.ZM22046@torch.brasslantern.com> On 12/04/2012 05:01 PM, Bart Schaefer wrote: > Possibly the -t test is blocking until the terminal is ready. That > would synchronize the shell with the parent urxvt, which would also > explain this: > > } Strangely enough, not only I don't get the error anymore, but the > } terminal title also seem to be always correctly set on startup > > On the other hand I'd have expected zsh's internals to do the equivalent > of -t at some point during initialization, to decide whether the shell > is interactive in the first place, so maybe introducing a tiny delay > before the print is enough to break the race condition. I spoke too soon. I got another interrupted call today. It seems that, like you say, [ -t 0 ] just delays the call long enough for urxvt to be available most of the time, so it became very rare, but not absent. I just suppressed the error now. This is tricky to debug and I'm quite sure urxvt is at fault (probably the message is due to the window being mapped, but maybe not managed yet!?). Just don't have time to debug it properly now.