From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Subject: Re: Hard to switch from vi
Date: Tue, 10 Oct 2006 10:18:11 +0300 [thread overview]
Message-ID: <86ejtgiqq4.fsf@gothmog.pc> (raw)
In-Reply-To: 452b9f36$1@news.greennet.net
On Mon, 09 Oct 2006 09:28:29 -0400, Ken Goldman <kgold@watson.ibm.com> wrote:
> Wen Weng wrote:
>> 2. Is there a repeat last command command like the dot command in vi?
>
> You want to read about keyboard macros. IMHO, this single feature
> distinguishes emacs from any other editor.
>
> With keyboard macros, you save and then replay any key sequence, which
> can include insert and delete, but also search, edit and save,
> stepping through errors, cut and paste, etc. It's far more powerful
> than the vi dot.
Exactly :)
Keyboard macros are truly amazing. They are always the first feature of
Emacs that I demonstrate to people who have completed the basic keyboard
stuff of the tutorial. Everyone who sees keyboard macros `in action'
instantly loves them!
(This is probably why VIM and other modern vi(1) implementations have
keyboard macro features too, but I am not 100% sure.)
next prev parent reply other threads:[~2006-10-10 7:18 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 23:32 Hard to switch from vi Wen Weng
2006-10-09 0:12 ` Ignacio Mondino
2006-10-09 7:10 ` Lennart Borgman
2006-10-09 10:57 ` Jeremy Hankins
2006-10-09 14:47 ` Lennart Borgman
2006-10-09 17:49 ` Jeremy Hankins
[not found] ` <mailman.7914.1160393911.9609.help-gnu-emacs@gnu.org>
2006-10-10 13:03 ` Hadron Quark
2006-10-10 13:50 ` Pascal Bourguignon
2006-10-13 10:36 ` Hadron Quark
2006-10-10 14:11 ` Jeremy Hankins
[not found] ` <mailman.7909.1160377822.9609.help-gnu-emacs@gnu.org>
2006-10-10 1:39 ` Wen Weng
[not found] ` <mailman.7907.1160352764.9609.help-gnu-emacs@gnu.org>
2006-10-09 0:40 ` Wen Weng
2006-10-09 1:48 ` Ajit Mylavarapu
2006-10-09 2:03 ` ext-chunye.wang
2006-10-09 2:09 ` Pascal Bourguignon
2006-10-09 2:44 ` Wen Weng
2006-10-10 12:59 ` Hadron Quark
2006-10-09 2:04 ` Pascal Bourguignon
2006-10-10 11:53 ` Hadron Quark
2006-10-11 13:35 ` martin
2006-10-09 8:52 ` Markus Triska
2006-10-09 8:53 ` David Kastrup
2006-10-09 16:28 ` Harald Hanche-Olsen
2006-10-10 1:36 ` Wen Weng
2006-10-10 11:16 ` Markus Triska
2006-10-10 13:05 ` Hadron Quark
2006-10-10 14:02 ` Pascal Bourguignon
2006-10-10 12:20 ` Hadron Quark
2006-10-10 12:32 ` Pascal Bourguignon
2006-10-10 12:38 ` Markus Triska
2006-10-10 12:57 ` Hadron Quark
2006-10-09 12:01 ` lgfang
2006-10-10 1:17 ` Wen Weng
2006-10-09 13:28 ` Ken Goldman
2006-10-09 15:06 ` Malte Spiess
2006-10-10 7:18 ` Giorgos Keramidas [this message]
[not found] ` <45299CB0.5090003@speakeasy.net>
[not found] ` <4529A0E4.60403@charter.net>
2006-10-09 9:58 ` ken
2006-10-10 0:50 ` Stefan Monnier
[not found] ` <mailman.7911.1160387922.9609.help-gnu-emacs@gnu.org>
2006-10-10 1:22 ` Wen Weng
2006-10-10 2:23 ` Micha Feigin
2006-10-21 17:25 ` don provan
2006-10-22 19:36 ` Lennart Borgman
[not found] ` <mailman.132.1161545823.27805.help-gnu-emacs@gnu.org>
2006-10-23 17:15 ` don provan
2006-10-23 17:53 ` Lennart Borgman
2006-10-23 18:56 ` Floyd L. Davidson
2006-10-24 9:01 ` Mathias Dahl
2006-10-24 10:12 ` Floyd L. Davidson
2006-10-24 11:25 ` Mathias Dahl
2006-10-24 18:23 ` Floyd L. Davidson
2006-10-25 14:21 ` Mathias Dahl
2006-10-21 21:00 ` Dieter Wilhelm
2006-10-11 22:21 ` John Sullivan
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ejtgiqq4.fsf@gothmog.pc \
--to=keramida@ceid.upatras.gr \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).