From: dkcombs@panix.com (David Combs)
Subject: Re: Operate on region string
Date: Sat, 14 Oct 2006 22:23:30 +0000 (UTC) [thread overview]
Message-ID: <egro11$19m$1@reader1.panix.com> (raw)
In-Reply-To: 87lkogz0kj.fsf@thalassa.informatimago.com
In article <87lkogz0kj.fsf@thalassa.informatimago.com>,
Pascal Bourguignon <pjb@informatimago.com> wrote:
>Hadron Quark <hadronquark@gmail.com> writes:
>>> But if you want the best performances, emacs is optimized to work in
>>> the buffers, not on strings. So if you can do it, better to directly
>>> modify the buffer:
>>>
>>> (defun my-command (start end)
>>> (interactive "r")
>>> (do-work-on-region start end))
>>
>> this is what I wanted to know : what is the best way to "do-work-on-region"?
>
>You need to learn the emacs lisp functions, notably those who work on
>the buffers and on the strings.
>
>Most of the functions that work on the buffers are actually commands
>that are also bound to some keys and that you use.
>
>For example, if you want to remove every other character in the region,
>you can do it manually with C-f C-d C-f C-d ...
>
>You can know what functions are called when you type C-f or C-d:
>
> C-h k C-f
> C-h k C-d
>
Easy way to do that: define the seq as a macro,
then do "insert-macro" (or whatever it's called) --
that code shows the function-NAMES too.
David
prev parent reply other threads:[~2006-10-14 22:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 9:59 Operate on region string Hadron Quark
2006-09-18 10:37 ` Tassilo Horn
2006-09-18 12:28 ` Hadron Quark
2006-09-18 12:55 ` Tassilo Horn
2006-09-18 15:24 ` Hadron Quark
2006-09-20 10:14 ` robert.thorpe
2006-09-18 13:02 ` Mathias Dahl
2006-09-18 13:10 ` Hadron Quark
2006-09-19 22:20 ` John Sullivan
2006-09-18 11:13 ` Pascal Bourguignon
2006-09-18 12:21 ` Hadron Quark
2006-09-19 9:07 ` Pascal Bourguignon
2006-10-14 22:23 ` David Combs [this message]
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='egro11$19m$1@reader1.panix.com' \
--to=dkcombs@panix.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).