zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: vi editting troubles
Date: Wed, 23 May 2001 09:08:37 +0200 (MET DST)	[thread overview]
Message-ID: <200105230708.JAA21752@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <1010523062822.ZM23346@candle.brasslantern.com>

Bart Schaefer wrote:

> ...
> 
> We can't ensure it, which is why I directed a question to zsh-workers
> about the reason for the choice of keybindings.  I'm a bit surprised that
> no one spoke up.

It wasn't me this time, but I think Adam modelled it after some Emacs
key bindings?


About the init code stuff: I could do that, I'm just not sure which way
we should go.  Repeating everything in every function is just too ugly. 
Putting it into the C-code is the opposite of what I wanted to achieve -- 
and I want to try to keep the basic C-code independent of the way the
completion system shell code is written.

So, I would prefer a solution that allows us to add just a bit of code
to the top level shell functions which sets everything up.  Be it an
array (so that we would add a line like `$_init_comp' to the functions)
or an alias or -- somewhat uglier because the setopt localoptions has to
be called separately -- a initialisation function to call.

I think we had a bit of discussion about this before when we added the
_comp_options array. But I have been very busy this week and didn't find
the time to look it up (and I'll be away from tomorrow till (not
including) monday, so everybody will have the possibility to be faster
in solving this than me).

Bye
  Sven


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


  reply	other threads:[~2001-05-23  7:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23  3:04 Paul Ackersviller
2001-05-23  4:41 ` 64-bit sparc instructions Bart Schaefer
2001-05-23  9:38   ` Andrej Borsenkow
2001-05-23 16:42     ` Clint Adams
2001-05-23 12:29   ` Clint Adams
2001-05-23  6:28 ` vi editting troubles Bart Schaefer
2001-05-23  7:08   ` Sven Wischnowsky [this message]
2001-05-23  9:42     ` Peter Stephenson
2001-05-23 18:18     ` Wayne Davison
2001-05-23 19:31       ` Bart Schaefer
2001-05-29  6:59         ` Sven Wischnowsky
2001-05-29 11:57           ` PATCH: " Sven Wischnowsky
2001-05-29 14:58             ` Bart Schaefer
2001-05-30  7:19               ` Sven Wischnowsky
     [not found] <20010521121334.A24931@flora01.SLAC.Stanford.EDU>
2001-05-21 19:43 ` Peter Stephenson
     [not found] ` <010521132805.ZM11030@candle.brasslantern.com>
2001-05-22  1:53   ` nce
2001-05-22  2:31     ` 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=200105230708.JAA21752@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@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).