zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Cc: 579209@bugs.debian.org
Subject: Re: zsh: insert-last-word problem after completion
Date: Mon, 26 Apr 2010 23:38:40 +0100	[thread overview]
Message-ID: <20100426233840.67d4934c@pws-pc> (raw)
In-Reply-To: <20100426154210.GD25015@prunille.vinc17.org>

On Mon, 26 Apr 2010 17:42:10 +0200
Vincent Lefevre <vincent@vinc17.net> wrote:
> On 2010-04-26 13:11:39 +0100, Peter Stephenson wrote:
> > On Mon, 26 Apr 2010 12:53:31 +0200
> > Vincent Lefevre <vincent@vinc17.net> wrote:
> > > After a "zsh -f":
> > > 
> > > % alias my_echo=echo
> > > % false
> > > % true &
> > > % my_ech[TAB]
> > > 
> > > A succession of [ESC] . (bound to insert-last-word) gives:
> > > 
> > >   my_echo&
> > >   my_echo&&
> > >   my_echo&false
> 
> Actually I noticed the bug with the new completion system.

I've got there, too, eventually.

There are two ways to approach this: either have the "&" inserted as
now, with the space removed, which is the same as if the "&" was typed;
or fix the suffix when inserting the last word.  The drawback with the
former (which is what it's currently trying to do, but failing) is that
replacing the & with earlier words would leave the space before it
removed, and in most cases that won't be the right thing to do (you'd
get "my_echofalse" in this case).  So I think the latter is the right
answer---we know that what we're inserting always functions as a
complete word, hence fixing the space or whatever makes more sense even
if in the case of the first last word you happen not to need it.
This happens to be the simpler fix (though I have an implementation of
the other one, too).

By the way, as an alternative to smart-insert-last-word, what I do is
have the widget copy-earlier-word bound to ESC = so that I can get
earlier words from the line to which ESC . has taken me.

Index: Src/Zle/zle_hist.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/Zle/zle_hist.c,v
retrieving revision 1.64
diff -p -u -r1.64 zle_hist.c
--- Src/Zle/zle_hist.c	18 Mar 2010 16:03:20 -0000	1.64
+++ Src/Zle/zle_hist.c	26 Apr 2010 22:29:11 -0000
@@ -634,6 +634,7 @@ insertlastword(char **args)
 	}
     }
 
+    fixsuffix();
     metafy_line();
     if (lastinsert && lastlen &&
 	lastpos <= zlemetacs &&

-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


  reply	other threads:[~2010-04-26 22:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 10:53 Vincent Lefevre
2010-04-26 11:34 ` Mikael Magnusson
2010-04-26 12:11 ` Peter Stephenson
2010-04-26 15:42   ` Vincent Lefevre
2010-04-26 22:38     ` Peter Stephenson [this message]
2010-04-27 14:24       ` Vincent Lefevre

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=20100426233840.67d4934c@pws-pc \
    --to=p.w.stephenson@ntlworld.com \
    --cc=579209@bugs.debian.org \
    --cc=zsh-workers@zsh.org \
    /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).