From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-users@sunsite.dk
Subject: Re: zle-overwrite with 4.1.0-dev-0
Date: Mon, 25 Jun 2001 11:28:11 +0200 (MET DST) [thread overview]
Message-ID: <200106250928.LAA23199@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <200106250807.KAA68315@numa1.igpm.rwth-aachen.de>
Helmut Jarausch wrote:
> Hi,
>
> (I believe that) on my Linux system switching to 4.1.0-dev-0 (cvs one
> week ago) I get overwrite mode (for zle) per default and switching back
> to insert mode doesn't last for long.
> Is there a new option?
No. Hm, I've got no idea where the problem might be, I've never seen
something like that myself.
> Furthermore (I've just noticed it on my IRIX box at my office)
> I cannot use ^X* anymore to expand things like ~-
> This is with 4.0.1-pre-5 but I don't remember when it slipped in.
> Any ideas?
Oops. That was caused by your humble code-messer-upper. Ahem.
We have to copy that string for normal expansion, too, otherwise the
test on line 790 will succeed and the command line will be restored.
Apologies for posting a patch to -users. This will go into the
development branch and 4.0.2.
Bye
Sven
Index: Src/Zle/zle_tricky.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/Zle/zle_tricky.c,v
retrieving revision 1.29
diff -u -r1.29 zle_tricky.c
--- Src/Zle/zle_tricky.c 2001/06/24 03:42:09 1.29
+++ Src/Zle/zle_tricky.c 2001/06/25 09:25:36
@@ -752,7 +752,8 @@
inststr(x);
} else if (COMP_ISEXPAND(lst)) {
/* Do expansion. */
- char *ol = (olst == COMP_EXPAND_COMPLETE) ?
+ char *ol = (olst == COMP_EXPAND ||
+ olst == COMP_EXPAND_COMPLETE) ?
dupstring((char *)line) : (char *)line;
int ocs = cs, ne = noerrs;
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
prev parent reply other threads:[~2001-06-25 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 8:07 jarausch
2001-06-25 9:28 ` Sven Wischnowsky [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=200106250928.LAA23199@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-users@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).