zsh-users
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-users@sunsite.auc.dk
Subject: Re: New user questions
Date: Fri, 31 Mar 2000 09:42:19 +0200 (MET DST)	[thread overview]
Message-ID: <200003310742.JAA07133@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrew Morton"'s message of Fri, 31 Mar 2000 06:40:36 +0000


Andrew Morton wrote:

> Well thanks everyone for all the help.  Just about everything is working
> sweetly (better than the old shell, actually).
> 
> Trolling through the magic commands in
> /usr/share/zsh/3.1.6-dev-20/functions/Commands/ helped a lot.
> 
> A few more observations:
> 
> - The zshbuiltins manpage doesn't cover 'bindkey'

Because it's not defined by the shell core, but by the zle module. See 
zshzle(1).

> ...
> 
> - The _history-complete-older function does exactly what I wanted for
> searching back through word history!
> 
> - _history-complete-older has a bug.  In this example it is bound to ^R:
> 
> prompt> echo aa "bb" cc
> prompt> echo ^R			# OK, gives echo cc
> prompt> echo ^R^R               # oops.  gives echo aa
> 
> It is skipping quoted words in its search.

It's not a bug, it's intentional: it explicitly excludes words
starting with any of [$'"]. That was the behaviour shown by the
compctl option for history completion, but now that we have
ignored-patterns it indeed doesn't seem to make sense any more.

> ...
> 
> Question: How do I, within .zshrc, simply erase _all_ preexisting
> bindings and start afresh?  I've tried everything.
> 
> pwold011:/home/morton> bindkey -l
> .safe
> emacs
> main
> vicmd
> viins
> pwold011:/home/morton> bindkey -D emacs vicmd viins
> pwold011:/home/morton> bindkey -l
> .safe
> main
> pwold011:/home/morton> bindkey -D main
> No such keymap `main'

`main' is (internally) really only an alias or some kind of pointer to 
the keymap currently used. Keymap handling (or zle/widget stuff in
general) is one of the things we might have a look at after 3.2/4.0 is 
out. I think.

Besides... do you *really* want to remove all keymaps and begin from
scratch? Why? You would have to add all those self-insert bindings,
the cursor movement, etc etc etc. Rather tedious.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-03-31  7:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-31  7:42 Sven Wischnowsky [this message]
2000-03-31 10:42 ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2000-03-30  3:14 Andrew Morton
2000-03-30  5:20 ` Chmouel Boudjnah
2000-03-30  5:27 ` Friedrich Dominicus
2000-03-30 11:12   ` Oliver Kiddle
2000-03-30  6:50 ` Andrej Borsenkow
2000-03-30 18:22   ` Chmouel Boudjnah
2000-03-31  6:40     ` Andrew Morton
2000-03-31  7:45       ` Andrej Borsenkow
2000-03-31 10:33         ` Andrew Morton
2000-04-01 17:13       ` Zefram
2000-03-30  6:57 ` Andrej Borsenkow
2000-03-30 13:27 ` Zefram
2000-03-31 16:18   ` 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=200003310742.JAA07133@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).