zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: complete paths after non-space
Date: Wed, 03 Aug 2005 19:54:39 +0100	[thread overview]
Message-ID: <200508031854.j73IsdnN006237@news01.csr.com> (raw)
In-Reply-To: <7c737f3005080216113bd158da@mail.gmail.com>

Deliverable Mail wrote:
> I'm migrating to zsh and find it differs subtly from bash.  Three
> immediate look-'n-feel diffs I'd really need to reset to
> bash-compatible behavior...
> 
> 1.  completing path names with leading non-space
> 
> I often want to complete filenames in options where you have things
> like --file=/wrong/path/name, whereby you go back and fix it, or enter
> new things after the non-space-starting pathname sequence
> 
> Bash happily completed it while in my current zsh setup I have to
> insert/delete a space prior to the pathname.  An easy way to make it
> the same?

If you're using the new completion system (compinit), turn on the option
magicequalsubst.

  setopt magicequalsubst

(It's just possible it works with the old completion system, too.)

> 2.  in-place ^r search
> 
> -- zsh offers an underline, and I don't want it

You just have to ignore it.   It's unusual enough not to want to see
what your searching for that there's no option.

> 3.  completion offers must go away faster
> 
> -- zsh lists them in the underline(s) and they seem to linger there
> longer than in bash, can I banish them faster?

It's possible you can do something with zle -R in one of the completion
functions, which redisplays the stuff below the line using the string
you specify (which might be empty), but I've never played around with this.

You can force the shell to reprint the line below all completion
displays by

  unsetopt alwayslastprompt

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************


  parent reply	other threads:[~2005-08-03 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 23:11 Deliverable Mail
2005-08-03 17:57 ` Deliverable Mail
2005-08-03 18:15   ` Philippe Troin
2005-08-03 18:54 ` Peter Stephenson [this message]
2005-08-03 23:24   ` Deliverable Mail
2005-08-04  0:27     ` Wayne Davison
2005-08-05  2:43       ` Deliverable Mail
2005-08-05  8:30         ` Mikael Magnusson
     [not found]   ` <7c737f3005080313407fc2cdfa@mail.gmail.com>
     [not found]     ` <6249.1123141858@csr.com>
     [not found]       ` <7c737f3005080413226cb67cd4@mail.gmail.com>
     [not found]         ` <7374.1123234276@csr.com>
2005-08-05 17:22           ` Deliverable Mail
2005-08-05 17:50             ` Peter Stephenson

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=200508031854.j73IsdnN006237@news01.csr.com \
    --to=pws@csr.com \
    --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).