From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: repeat vs. zap-to-char
Date: Wed, 30 Apr 2003 10:02:52 +0800 [thread overview]
Message-ID: <878yts68tv.fsf@jidanni.org> (raw)
There I was, all dressed in festive gear like rappers EPMD in their
"please listen to my demo" song, all ready to use:
C-x z runs the command repeat
to repeat
ESC z runs the command zap-to-char
when my luck ran out as one has to tell it again and again to zap the
same character. Anyway, as the Morris the Cat commercial said, "Big
expectations, big let down."
Yes, repeat takes an argument, but still...
--
http://jidanni.org/ Taiwan(04)25854780
next reply other threads:[~2003-04-30 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 2:02 Dan Jacobson [this message]
[not found] <mailman.5387.1051676511.21513.bug-gnu-emacs@gnu.org>
2003-04-30 6:33 ` repeat vs. zap-to-char Johan Bockgård
2003-04-30 23:31 ` Dan Jacobson
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=878yts68tv.fsf@jidanni.org \
--to=jidanni@dman.ddts.net \
/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.savannah.gnu.org/cgit/emacs.git
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).