zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Mark G. Sobell" <mark@sobell.com>
Cc: zsh-users@sunsite.auc.dk (Zsh users list)
Subject: Re: zsh questions
Date: Thu, 17 Aug 2000 15:46:39 +0000	[thread overview]
Message-ID: <1000817154639.ZM25711@candle.brasslantern.com> (raw)
In-Reply-To: <E13Onll-00002r-00.2000-08-15-21-57-09@cmailg2.svr.pol.co.uk>

} "Mark G. Sobell" wrote:
} > I'm revising my Linux book and have noticed that a couple of things have
} > changed in zsh. If you could tell me if these are changes, bugs, or
} > something else I would appreciate it.  If they are bugs, when do you
} > expect them to be fixed?
} > 
} > --------------------------------
} > 
} > Under Red Hat 6.2 i386 (kernel 2.2.14-5.0)
} > 
} > I have tried these on ZSH_VERSION=3.1.6-pws-9 and ZSH_VERSION=3.0.7.
} > 
} > after giving the command bindkey -v
} > 
} > ESCAPE = lists possible completions for partial filenames entered on
} > the command line. (fails on 3.1.6)

As far as I know, ESCAPE was *never* used to list possible completions
in zsh, in vi mode or otherwise.  Control-D is used in all cases, and
always has been.  ESCAPE switches from vi insert mode to vi command mode,
or acts as a prefix key for multi-key bindings when already in vi command
mode.

However, there is a difference -- and possibly a bug -- in the 3.1 series,
which was probably introduced fairly recently.  In vi command mode, it's
not possible to more the cursor to the right of the last character on the
line.  In 2.x and 3.0, therefore, completion in vi command mode always
begins using the character UNDER the cursor, rather than the character to
the LEFT OF the cursor.  In 3.1.6 and 3.1.9 (I haven't checked earlier
versions of 3.1), completion in vi command mode uses the character to the
left of the cursor, exactly as do vi insert mode and emacs mode in all
versions.

This of course means that the set of possible completions generated in vi
command mode will not be the same in 3.1.6+ as in 3.0.x, and in fact it
may appear not to be generating completions at all, depending on context.

} > TAB used to extend partial filenames as far as possible (fails on both
} > versions)

This is indeed a change.  In the 2.x series, TAB was bound to complete-word
in vi command mode and to expand-or-complete in insert mode and emacs mode.
As of 3.0, the vi command mode binding was dropped, so TAB is unbound in
that mode in 3.0.x and 3.1.x.  It should be unchanged as long as you have
not pressed ESCAPE to enter vi command mode.

On Aug 15,  9:57pm, Peter Stephenson wrote:
}
} I'd be happy to read through your chapter on zsh; there may be other
} takers.

I'd be willing to do so as well.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      reply	other threads:[~2000-08-17 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <005901c00600$5261ed50$19859dd1@zach.sobell.com>
2000-08-15 20:57 ` Peter Stephenson
2000-08-17 15:46   ` Bart Schaefer [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=1000817154639.ZM25711@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=mark@sobell.com \
    --cc=zsh-users@sunsite.auc.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).