zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Mac OS X Prompt Bug
Date: Wed, 24 Nov 2010 15:49:51 -0800	[thread overview]
Message-ID: <101124154951.ZM18369@torch.brasslantern.com> (raw)
In-Reply-To: <2A1FA6CC-8EE8-4E01-AE40-5F02F4F340AE@gmail.com>

On Nov 24,  4:14pm, Sorin Ionescu wrote:
}
} There is no /etc/zshprofile, /etc/zshrc or any other combination.
} /etc/profile is not sourced.
}
} I have found nothing in the output of zsh -l -x. Like I said, it's
} not a configuration issue. It's something in ZSH or Terminal.app or
} both. Nothing hooks on those functions. It's possible that ZSH outputs
} some sequences Terminal.app does not like and generates those lines.

Things that zsh might be doing when the window first opens include
closing and re-opening the standard I/O streams, reading the name
of the terminal device with ttyname(), setting the close-on-exec
flag on some descriptors, and reading the size of the terminal from
ioctl().  It might also repeat that last a few times if it receives
WINCH signals.

You could try putting a TRAPWINCH function in your ~/.zshenv file
to see if that's called when the blank lines are printed.  Otherwise
you're going to have to resort to some sort of debugger or system
call trace.


      reply	other threads:[~2010-11-24 23:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 13:58 Sorin Ionescu
2010-11-24 15:24 ` Peter Stephenson
2010-11-24 16:08   ` Vincent Lefevre
2010-11-24 16:53     ` Peter Stephenson
2010-11-24 19:04     ` Wayne Davison
2010-11-25 10:38       ` Peter Stephenson
2010-11-24 15:30 ` Vincent Lefevre
2010-11-24 16:59   ` Sorin Ionescu
2010-11-24 17:49     ` Benjamin R. Haskell
2010-11-24 21:14       ` Sorin Ionescu
2010-11-24 23:49         ` Bart Schaefer [this message]

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=101124154951.ZM18369@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@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).