zsh-users
 help / color / mirror / code / Atom feed
From: Mircea Damian <dmircea@mail.kappa.ro>
To: Bart Schaefer <schaefer@brasslantern.com>,
	Mircea Damian <dmircea@mail.kappa.ro>,
	zsh-users@math.gatech.edu
Subject: Re: question
Date: Mon, 9 Mar 1998 19:42:08 +0200	[thread overview]
Message-ID: <19980309194208.A6635@fax-hk.kappa.ro> (raw)
In-Reply-To: <980309093033.ZM9449@candle.brasslantern.com>; from Bart Schaefer on Mon, Mar 09, 1998 at 09:30:33AM -0800

On Mon, Mar 09, 1998 at 09:30:33AM -0800, Bart Schaefer wrote:
> On Mar 9,  6:01pm, Mircea Damian wrote:
> } Subject: Re: question
> }
> } Another issue:
> }  There is a problem in zsh-3.0.5 which I can't reproduce it. Sometimes, not
> } very often, it happens to exit unexpectedly from my session.
> 
> Have you by any chance applied a patch for the HIST_REDUCE_BLANKS option?
> The most recently posted version of that patch -- which was quite a while
> ago, admittedly -- applies (IIRC) without rejections to zsh-3.0.x, but
> introduces a bug that causes the shell to exit as soon as the length of
> the history exactly equals HISTSIZE.  
> 
> However, I doubt that's the problem ... the only place in the code that
> I can find that would print the string "logout" on the same line as the
> prompt, like you showed here:
> 
> } dmircea@mail:/home/dmircea% logout
> 
> Is this bit of init.c:
> 
> 	if (!(isset(IGNOREEOF) && interact)) {
> #if 0
> 	    if (interact)
> 		fputs(islogin ? "logout\n" : "exit\n", stderr);
> #endif
> 	    zexit(lastval, 0);
> 	    continue;
> 	}
> 
> That would mean that (1) you've changed the `#if 0' to get that code to
> compile and (2) zsh is seeing end-of-file on the terminal.  You might want
> to try "setopt ignoreeof" and just to see what happens.
AFAIK the archive that I used was a clean one. I don't remember exactly
were I download it.

I'm sure that "setopt ignoreeof" will solve this problem but I do like to
exit from my session with ^D.

If it will happen again may be I'm gonna make some investigation(I'm very
busy... I'm student too).


-- 
Mircea Damian
Kappa Administrator
dmircea@roedu.net, dmircea@lbi.ro, dmircea@kappa.ro
MD65-RIPE, MD2225, MD1-6BONE
Phone: +40-1-7719245


  reply	other threads:[~1998-03-09 17:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-09 11:27 question Mircea Damian
1998-03-09 11:48 ` question Andrew Main
1998-03-09 14:35   ` question Geoff Wing
1998-03-09 16:01     ` question Mircea Damian
1998-03-09 17:30       ` question Bart Schaefer
1998-03-09 17:42         ` Mircea Damian [this message]
1998-03-10 11:04       ` question Stephen Marley
1998-03-09 18:46 question Niall Smart
     [not found] <CGME20180302035019epcas2p31b866a89661bbedcf2af60dbb038e091@epcas2p3.samsung.com>
2018-03-02  3:48 ` question Quolick
2018-03-02  4:34   ` question lilydjwg
2018-03-02 12:00     ` question Vincent Bernat
2018-03-02  4:38   ` question Ray Andrews
2018-03-02  9:05   ` question Peter Stephenson

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=19980309194208.A6635@fax-hk.kappa.ro \
    --to=dmircea@mail.kappa.ro \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@math.gatech.edu \
    /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).