all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Mon, 31 Jul 2017 06:40:15 +0200	[thread overview]
Message-ID: <874ltt2p8w.fsf@jane> (raw)
In-Reply-To: <868tj538ck.fsf@zoho.com>


On 2017-07-30, at 23:47, Emanuel Berg <moasen@zoho.com> wrote:

> Marcin Borkowski wrote:
>
>>>> 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.
>
> Not in the medium or long run as you get better
> with Elisp, and keyboard macros are much more
> difficult to adapt/debug.
>
> There is the ELPA and MELPA with readily
> transferable Elisp for a reason. But where do
> you guys get your keyboard macros?
> The port block?

A typical use case: I need to fix/edit/add something in a configuration
file, using the format VARIABLE=value, for 4-5 variables with similar
names (like PREFIX_SOMETHING=value, where value is somehow based on
SOMETHING).  I record a keybord macro, press F4 3-4 times, bam, done, in
10 seconds.  (Recently, I started to use multiple cursors for that kind
of stuff, too, but keyboard macros are a tad more powerful, I guess.)

> Learn to type really, really fast. Use Elisp
> whenever it isn't fast enough. Speed kills.

Typing fast would be fine, but keyboard macros don't make mistakes.

--
Marcin Borkowski



  reply	other threads:[~2017-07-31  4:40 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
2017-07-30 21:47         ` Emanuel Berg
2017-07-31  4:40           ` Marcin Borkowski [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ltt2p8w.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.