From: Rui Tiago Matos <tiagomatos@gmail.com>
Subject: Re: simgle repeat?
Date: Tue, 12 Apr 2005 01:31:39 +0100 [thread overview]
Message-ID: <eae3b3410504111731c3c6e4@mail.gmail.com> (raw)
In-Reply-To: <85zmw4n92t.fsf@obelix.seki.fr>
On Apr 12, 2005 1:16 AM, Sébastien Kirche
<sebastien.kirche.no@spam.free.fr.invalid> wrote:
> You can prefix a command, or a single key press with the universal argument
> C-u :
[snip]
> For example : C-u 25 . gives 25 dots : .........................
Yes, I know about that one. But it is not the same.
next prev parent reply other threads:[~2005-04-12 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1120.1113260612.2895.help-gnu-emacs@gnu.org>
2005-04-12 0:16 ` simgle repeat? Sébastien Kirche
2005-04-12 0:31 ` Rui Tiago Matos [this message]
2005-04-12 1:01 ` Barry Margolin
2005-04-12 2:07 ` Angelina Carlton
[not found] ` <mailman.1129.1113271432.2895.help-gnu-emacs@gnu.org>
2005-04-12 11:52 ` Pascal Bourguignon
2005-04-12 18:28 ` kgold
2005-04-12 18:25 ` Rui Tiago Matos
2005-04-11 23:32 Rui Tiago Matos
2005-04-12 10:58 ` Peter Dyballa
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=eae3b3410504111731c3c6e4@mail.gmail.com \
--to=tiagomatos@gmail.com \
/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).