zsh-workers
 help / color / mirror / code / Atom feed
From: Sorin Ionescu <sorin.ionescu@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Mac OS X Prompt Bug
Date: Wed, 24 Nov 2010 16:14:28 -0500	[thread overview]
Message-ID: <2A1FA6CC-8EE8-4E01-AE40-5F02F4F340AE@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1011241242320.2792@hp>

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. Perhaps, they are invisible characters.

Output of zsh -l -x.

krustyroo% zsh -l -x
+/etc/zshenv:2> [ -x /usr/libexec/path_helper ']'
+/etc/zshenv:3> /usr/libexec/path_helper -s
+/etc/zshenv:3> eval 'PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Users/sorin/.local/bin:/Users/sorin/.local/sbin";' export 'PATH;'
+(eval):1> PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Users/sorin/.local/bin:/Users/sorin/.local/sbin 
+(eval):1> export PATH


On 24 Nov 2010, at 12:49, Benjamin R. Haskell wrote:

> On Wed, 24 Nov 2010, Sorin Ionescu wrote:
> 
>> Yes, iTerm2 does not have this problem. While unsetopt PROMPT_SP removes the %, the blank lines are still echoed. The easiest way to test this is to touch ~/.hushlogin and open Terminal.app. Notice the scrollbar.
>> 
>> So, PROMPT_SP is definitely not the problem. It seems the prompt is being pushed down by the blank lines. Hence why % is not being overwritten by the prompt in the screenshot.
> 
> So, figure out what's printing out the blank lines.
> 
> You mentioned /etc/zshenv.  What about /etc/zshprofile or /etc/zshrc? Or maybe even /etc/profile, which is often sourced by system Zsh startup files, depending on how Zsh is distributed.
> 
> Maybe see if something is set up with hook functions:
> 
> $ functions preexec precmd chpwd periodic TRAPDEBUG
> 
> As a last resort, try to run Zsh with tracing enabled:
> 
> zsh -x  (then Ctrl-d or quit)
> [produces lots of output, but maybe near the end you'll see something printing out some blank lines]
> 
> Might need: zsh -l -x
> (not sure how you start your commands in OS X terminal)
> 
> -- 
> Best,
> Ben


  reply	other threads:[~2010-11-24 21:14 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 [this message]
2010-11-24 23:49         ` Bart Schaefer

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=2A1FA6CC-8EE8-4E01-AE40-5F02F4F340AE@gmail.com \
    --to=sorin.ionescu@gmail.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).