zsh-users
 help / color / mirror / code / Atom feed
From: Gerald Skerbitz <gsker@lenti.med.umn.edu>
To: Timothy J Luoma <luomat@nerc3.nerc.com>
Cc: zsh-users@math.gatech.edu, comp-sys-next-software@antigone.com
Subject: Re: history commands coming out wrong
Date: Tue, 5 Nov 1996 07:48:20 -0600 (CST)	[thread overview]
Message-ID: <Pine.SOL.3.95.961105074535.14596B-100000@halfdan.med.umn.edu> (raw)
In-Reply-To: <199611050354.WAA01439@nerc3.nerc.com>

Yes. I'm having the screwed up lines all over the place when going through
history.  This problem has existed since 2.6-beta8 or so.  It got fixed for a
release or two (was great in 2.6-beta13) but it appears it's back again.


Gerry,
3.0.0 Sun Solaris 2.4
setopt:
allexport alwaystoend appendhistory autocd automenu autonamedirs autopushd
nobgnice cdablevars completeinword extendedglob globdots histignoredups
ignoreeof interactive interactivecomments listtypes menucomplete monitor
nonomatch pathdirs pushdignoredups pushdminus pushdsilent pushdtohome
shinstdin zle

 On Mon, 4 Nov 1996, Timothy J Luoma wrote:
> zsh-3.0.1 compiled fine, but it is still way too slow when drawing  
> the PROMPT and RPROMPT.
> 
> Also, using the UP arrow to go back through history commands ends  
> up with screwed up lines (mangled commands, old and new combined,  
> etc).
> 
> Anyone else having similar problems?
> 
> I'm using Stuart.app 2.6.3+ under NS 3.3 patch1
> 
> TjL, still using 2.6-beta13
--
Gerry
Gerald Skerbitz <gsker@med.umn.edu> U of MN Med School Admin 6-5379
Home St. Paul,Ramsey County,Minnesota, USA


  reply	other threads:[~1996-11-05 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-05  3:54 zsh-3.0.1 slow on NeXTStep 3.3 (m68k), " Timothy J Luoma
1996-11-05 13:48 ` Gerald Skerbitz [this message]
1996-11-07 17:44 greg haygood
1996-11-07 18:26 greg haygood

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=Pine.SOL.3.95.961105074535.14596B-100000@halfdan.med.umn.edu \
    --to=gsker@lenti.med.umn.edu \
    --cc=comp-sys-next-software@antigone.com \
    --cc=luomat@nerc3.nerc.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).