From: Marcin Borkowski <mbork@mbork.pl>
To: Emanuel Berg <moasen@zoho.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: strange behaviour in keyboard macro
Date: Sun, 30 Jul 2017 22:19:47 +0200 [thread overview]
Message-ID: <877eyp3cf0.fsf@jane> (raw)
In-Reply-To: <86379e3umd.fsf@zoho.com>
On 2017-07-30, at 15:46, Emanuel Berg <moasen@zoho.com> wrote:
> Héctor Lahoz wrote:
>
>>> Rewrite it an Elisp function and voilà
>>> probably you can work out debugging without
>>> us :)
>>
>> Yes, it's not very long. But I wanted to do
>> it quickly without programming. Then, what's
>> the point of having keyboard macros?
>
> None whatsoever for people like you who know
> how to program.
Speed.
Best,
--
Marcin Borkowski
next prev parent reply other threads:[~2017-07-30 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 5:51 strange behaviour in keyboard macro Héctor Lahoz
2017-07-30 7:26 ` Emanuel Berg
2017-07-30 10:01 ` Héctor Lahoz
2017-07-30 13:46 ` Emanuel Berg
2017-07-30 20:19 ` Marcin Borkowski [this message]
2017-07-30 21:47 ` Emanuel Berg
2017-07-31 4:40 ` Marcin Borkowski
2017-07-31 9:19 ` Emanuel Berg
2017-08-09 6:18 ` Stefan Huchler
2017-07-30 13:50 ` Emanuel Berg
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=877eyp3cf0.fsf@jane \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
--cc=moasen@zoho.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).