zsh-workers
 help / color / mirror / code / Atom feed
From: Dan Nelson <dnelson@emsphone.com>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: Juhapekka Tolvanen <juhtolv@st.jyu.fi>, zsh-workers@sunsite.auc.dk
Subject: Re: Weird behaviour with certain PS1-sequences
Date: Mon, 27 Sep 1999 17:06:47 -0500	[thread overview]
Message-ID: <19990927170647.A5674@dan.emsphone.com> (raw)
In-Reply-To: <990927195733.ZM17681@candle.brasslantern.com>

In the last episode (Sep 27), Bart Schaefer said:
> On Sep 27, 10:14pm, Juhapekka Tolvanen wrote:
> > If I have this in .zshrc or give this in command line, shell goes
> > to endless loop. Terminal is all blank and Ctrl-c and Ctrl-z does
> > not help at all.
> > 
> > export PS1='%h|%l|%n@%m:%/ %# '
> 
> I can't reproduce this on Linux.  I've tried various prompt-related
> setopts with no change in the behavior.

I can reproduce this easily with zsh 3.0.6 or 3.1.6 on FreeBSD (2.2.6
and 4.0).  The TERM variable has to be set to a 'dumb'-style terminal,
or blank.  I thought I could reproduce it on Solaris 2.6 but it doesn't
seem to be cooperating right now.

% zsh -f
% PROMPT="%m %n %/ %%"
dan dan /home/dan % TERM=dumb
dan dan /home/dan % 
                    ^ blanks start here and don't stop

Oddly enough, "%m%n%/" doesn't trigger the bug. "%m  %n" does. "%m %n"
does not.

Termcap entry for 'dumb':

dumb|un|unknown:am:co#80:do=^J:

-- 
	Dan Nelson
	dnelson@emsphone.com


  parent reply	other threads:[~1999-09-27 22:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-27 19:14 Juhapekka Tolvanen
1999-09-27 19:57 ` Bart Schaefer
1999-09-27 20:03   ` Juhapekka Tolvanen
1999-09-27 22:06   ` Dan Nelson [this message]
1999-09-28  8:54     ` Peter Stephenson
1999-10-03  8:15       ` PATCH: 3.1.6: promptexpand (Re: Weird behaviour with certain PS1-sequences) Bart Schaefer
1999-10-03  9:04       ` PATCH: 3.1.6* (Was: " Geoff Wing

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=19990927170647.A5674@dan.emsphone.com \
    --to=dnelson@emsphone.com \
    --cc=juhtolv@st.jyu.fi \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.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).