zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: 2 questions of completion
Date: Sun, 04 Mar 2012 11:13:38 -0800	[thread overview]
Message-ID: <120304111338.ZM24681@torch.brasslantern.com> (raw)
In-Reply-To: <20120304144841.GB2090@pierre.localdomain>

On Mar 4,  3:48pm, Ranousse wrote:
}
} \gr tab (for completion) deletes the \ at the beginning of the line.
} Is there an option or something to avoid this.

No, there really isn't.  In order to do its work, completion reduces
the input word to its minimally escaped form; it doesn't know about
escapes that have been added for special effects beyond normal shell
syntax rules.

If you use quotes instead of a backslash, completion keeps those and
even adds the matching end quote for you.

You might be able to write a little wrapper function that looks for
(( CURRENT == 1 )) && [[ $WORDS[CURRENT] == \\* ]] and if so removes
the backslash, does completion, and then puts the backslash back.

} bindkey -M menuselect '^M' .accept-line
} 
} However I have a similar problem with backspace, and can't find
} solution. What can I do to make backspace works (I mean not pressing
} this key twice) ?

You aren't supposed to need anything special for backward-delete-char;
it's handled internally to menuselection.  In this case, however, the
first press of backward-delete-char is deleting the auto-appended space
following the completed word, which is why you seem to have to press
it twice.  You can see this better if you menu-select a directory, and
note that pressing backspace kills the trailing slash.

Assuming that you have both delete (^?) and backspace (^H) bound to
backward-delete-char, a quick workaround for you may be:

    bindkey -M menuselect -s '^H' '^?^?'

which just says that when a backspace is seen, send two deletes.  It
may be necessary to invert that if your keyboard sends ^? instead
of ^H when the key labeled backspace is pressed:

    bindkey -M menuselect -s '^?' '^H^H'

However, DO NOT use BOTH of those bindings -- only one or the other.
Using both will result in recursion as each expands the other.

On the other hand you'll find that for completions that do not auto-
append a space, this is deleting more than you want.  You'll just have
to try it out and see which behavior you find less bothersome.


  reply	other threads:[~2012-03-04 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 14:48 Ranousse
2012-03-04 19:13 ` Bart Schaefer [this message]
2012-03-04 22:55   ` Ranousse
2012-03-05  0:28     ` Bart Schaefer

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=120304111338.ZM24681@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).