From: Thomas Hopfner <Thomas.Hopfner@lpr.e-technik.tu-muenchen.de>
To: zsh-workers@math.gatech.edu
Cc: fischer@meru.lpr.e-technik.tu-muenchen.de (Franz Fischer),
thielen@meru.lpr.e-technik.tu-muenchen.de (Herbert Thielen)
Subject: zsh-2.5.03
Date: Wed, 23 Aug 1995 11:41:07 +0200 (MET DST) [thread overview]
Message-ID: <199508230941.LAA14712@meru.lpr.e-technik.tu-muenchen.de> (raw)
Hello there!
Because I didn't like the behaviour of the bash in vi-mode, I recently
tried the zsh-2.5.03. It was _much_ better!
And the new features... perfect work guys! :-)
Unfortunately I found a (serious?) bug, which caused me stopping the use
of zsh. If I type in a line and do a ``cw'' with a more-than-one-char
new expression and then try to repeat that change immediately with `.'
before zsh updated the line, zsh hangs in an infinite loop allocating
lots of memory and when I interrupt it with ``Ctrl-C'' it dumps a core.
It seems to be a problem with the typeahead... ?
So I tried 2.6-beta10 and found out that repeating a ``cw'' doesn't work
anymore... It behaves like a bash in vi-mode. :-[ (only a littlebit
vi-like) Do you intend to implement a real vi-mode for it?
I compiled the zsh-2.5.03 just by a automatic ./buildzsh on
DEC alpha AXP OSF/1 V2.0
PC i586 Linux (Kernel 1.2.11)
Sun SunOS 4.1.3
IBM RS/6000 AIX 3.2.5
On a
mips RISC/os (UMIPS) 4.52B
it needed a littlebit more work, but was not too difficult. If you are
interested in a patch I will send it to you upon request.
Could you help me?
Thanks in advance, Tom.
Thomas.Hopfner@lpr.e-technik.tu-muenchen.de
http://www.lpr.e-technik.tu-muenchen.de/~hopfner/
======================================================================
`` The best way to accelerate a DOOF/WINDOOF-PC is at 9.81 m/s^2 '' ;)
reply other threads:[~1995-08-23 9:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199508230941.LAA14712@meru.lpr.e-technik.tu-muenchen.de \
--to=thomas.hopfner@lpr.e-technik.tu-muenchen.de \
--cc=fischer@meru.lpr.e-technik.tu-muenchen.de \
--cc=thielen@meru.lpr.e-technik.tu-muenchen.de \
--cc=zsh-workers@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).