unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Beginning Hobbyist Programmer Question
Date: Fri, 18 Jan 2008 10:02:07 +0100	[thread overview]
Message-ID: <200801181002.08486.andreas.roehler@online.de> (raw)
In-Reply-To: <44129c70-807a-4ef0-bc4f-e299caf5e334@k39g2000hsf.googlegroups.com>

Am Donnerstag, 17. Januar 2008 23:04 schrieb signups17@gmail.com:
> I'm
> starting with Python and I've built a few scripts that have increased
> my productivity tremendously at work, doing a lot of data crunching,
> etc.

Beside of regexp search and replace,
font-highlighting--where all valid editors are able
to--I see Emacs strength in integration to another
processes whose output might be edited or handled
afterwards.

For example you may get the output of the shell into
some buffer and editing it then. You may run
shell-commands directly on the buffers code.

Or browse the net with Emacs-w3m and have the output
ready for further editing, if not calling functions on
them.

With some Emacs-Lisp knowledge the tasks turn a lot
easier again. Because regexps tend to be complicated,
quite often it's faster to write a function addressing
the special case than relying at interactive regexp
search and replace alone.

With Emacs you may automatize this function-writing
again, using skeletons, templates etc.

Not to forget key-board macros: Even if operating with
interactive regexp-search and replace sometimes it's
useful to record your steps for further repeats.

Andreas Röhler

  parent reply	other threads:[~2008-01-18  9:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 22:04 Beginning Hobbyist Programmer Question signups17
2008-01-17 22:47 ` Rupert Swarbrick
2008-01-18  0:26 ` reader
2008-01-18  1:44 ` Nick Roberts
2008-01-18  9:02 ` Andreas Röhler [this message]
2008-01-18  9:04 ` Thien-Thi Nguyen
2008-01-18 10:05 ` Stefan Kamphausen
2008-01-18 11:11 ` Daniel Pittman
2008-01-18 23:22 ` Alan Mackenzie
2008-01-19  0:19 ` Mike Treseler
2008-01-21 16:33   ` rustom
2008-01-22 17:24 ` Sebastian Tennant
2008-01-22 18:10   ` Mike Mattie
2008-01-23  6:02 ` Bob McCormick

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=200801181002.08486.andreas.roehler@online.de \
    --to=andreas.roehler@online.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).