From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-users@sunsite.auc.dk, Raju K V <raju.kurunkad@wipro.com>
Subject: Re: use vim to vi
Date: Tue, 09 May 2000 10:42:31 +0100 [thread overview]
Message-ID: <0FUA009H4DMVBA@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Tue, 09 May 2000 12:11:20 +0530." <20000509121120.A15491@wipro.com>
> When I say zsh uses vi mode for command line editing, does it actually
> use the vi editor or does it have a vi emulation inbuilt? if it calls
> the vi editor for command line editing, can i make it call vim instead?
No, it has its own built-in vi emulation.
> also in vi mode, how can I open the command line in vi (like 'v' command in
> ksh)?
I had a brief go at this (I'm not a vi mode expert) and there seem to be
all sorts of problems. I haven't got time to investigate, so I'm hoping
this will prompt some responses. This is unfortunately not an answer to
the original question.
- The traditional zsh way of doing this (needed for 3.0.x) would involve
pushing the current input somewhere, then running a command which uses
what's there. Where is `somewhere', buffer stack or history? Both seem
hard: if I use the history, it's hard to get the editor to stick something
there (as we've been discovering recently), if I use the buffer stack it's
hard to get a command to read it. What's an easy way of doing this? It
ought to be possible to stick something in the history and just run `fc -e
vi', which will pick that up, but writing bindkey -s applets (for want of a
better word) for vi mode seems pretty hairy.
- In 3.1.x you might hope you could run `fc -e vi' in an editing widget.
This doesn't seem to work. I don't think the history is set up right.
- Next attempt is to use the contents of $BUFFER (which certainly does work
and is a better way of doing it in zsh), dump it to a file and run vi on
that. vi is doing something very strange. I suspect (but haven't checked)
it's having all sorts of problems with the terminal being set up for
command line editing.
I can only hope Bart's got some answers.
--
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2000-05-09 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-09 6:41 Raju K V
2000-05-09 9:42 ` Peter Stephenson [this message]
2000-05-09 11:00 ` 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=0FUA009H4DMVBA@la-la.cambridgesiliconradio.com \
--to=pws@cambridgesiliconradio.com \
--cc=raju.kurunkad@wipro.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).