zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: zsh bug-hang on startup after exec
Date: Wed, 28 Mar 2001 05:48:33 +0000	[thread overview]
Message-ID: <1010328054833.ZM14993@candle.brasslantern.com> (raw)
In-Reply-To: <XFMail.20010325143412.bobort@abacus.dorm.reed.edu>

On Mar 25,  2:34pm, Ryan Richter wrote:
} Subject: Re: zsh bug-hang on startup after exec
}
} Sorry, I lied about the bash version. While I do have that rpm
} installed, I compiled a newer bash release from source since
} then. From bash --version: GNU bash, version 2.03.0(1)-release
} (i686-pc-linux-gnu)

I just upgraded the OS on one of the machines at work, so I was able to set
my shell to:

GNU bash, version 2.03.8(1)-release (i386-redhat-linux-gnu)

Then I put "exec /bin/zsh" in both .bashrc and .bash_profile (because for
some reason, although the doc says that "all interactive shells" will read
the ~/.bashrc file, login shells do not).

I still wasn't able to reproduce the problem.

However, it's bad form to have a potentially infinite loop in the shell
startup.  Zsh should probably just give up after either some number of
loops or some length of time.  Anyone have a suggestion?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      reply	other threads:[~2001-03-28  5:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 21:25 Ryan Richter
2001-03-22  1:01 ` Bart Schaefer
2001-03-22  1:56   ` Ryan Richter
2001-03-22 16:56     ` Bart Schaefer
2001-03-22 17:02       ` Ryan Richter
2001-03-25 21:07         ` Bart Schaefer
2001-03-25 22:34           ` Ryan Richter
2001-03-28  5:48             ` 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=1010328054833.ZM14993@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@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).