unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Couple of automation questions
Date: Wed, 27 Jul 2011 19:28:26 +0200	[thread overview]
Message-ID: <4E304ABA.7040003@easy-emacs.de> (raw)
In-Reply-To: <loom.20110727T184947-631@post.gmane.org>

Am 27.07.2011 18:52, schrieb fork:
> C K Kashyap<ckkashyap<at>  gmail.com>  writes:
>
>> Thanks Teemu ... I am aware of elisp. What I am looking for are general tips
> on how one goes about actually writing them in real time ( while editing some
> text) ... for example, if I do a kill and want to yank 10 times, What I'd do is
> M-:(dotimes (i 10) (yank))
>>
>> but is that the recommended way or would writing the script in the main buffer
> and executing it with C-x-e better ... or is there an even better way?
>
> What I do is to improvise a macro by C-x-( etc.  Then you can "M-x
> name-last-kbd-macro" to give it an identifier "M-x insert-kbd-macro" put the
> macro in your .emacs file for later.
>
> sed + awk + tr + shell scripting might be a better fit for automatically
> beautifying log files though
>
>
>

yes maybe, if the tasks repeat and are basically simple. Than you could 
use some python or perl too.

no, if it's seldom or tricky.

sed, awk etc. don't have such a thing like edebug for example.

Andreas



  parent reply	other threads:[~2011-07-27 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27  5:31 Couple of automation questions C K Kashyap
2011-07-27  7:16 ` Andreas Röhler
2011-07-27  7:27 ` Teemu Likonen
2011-07-27  8:11   ` C K Kashyap
2011-07-27  8:28     ` Teemu Likonen
2011-07-27 14:26     ` Memnon Anon
2011-07-27 16:52     ` fork
2011-07-27 17:06       ` Teemu Likonen
2011-07-27 17:23         ` fork
2011-07-27 17:28       ` Andreas Röhler [this message]
2011-07-28  2:40         ` C K Kashyap
2011-07-28  6:05           ` Teemu Likonen
2011-07-28  6:56           ` Andreas Röhler

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=4E304ABA.7040003@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=help-gnu-emacs@gnu.org \
    /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).