Re: replace-regexp from A to B?

Re: replace-regexp from A to B?

[Emanuel Berg]

Rodolfo Medina wrote:

> Is it possible, and how?, to perform
> a replace-regexp from a certain point, e.g.
> the current one, or from a certain
> word/expression, up to the next occurrence of
> a certain other word/expression...? In my
> case, with MusiXTeX documents, the starting
> point should be the TeX command `\startpiece'
> and the final one `\Endpiece'. So I could
> replace strings/expressions within a single
> musical piece without going out of it.

You can set the region manually and then use
a function with

    (goto-char START)
    (while (re-search-forward REGEXP STOP t)
      (replace-match TO-STRING nil nil))

where START is (region-beginning) and STOP is
(region-end). First check if there is a region
with (use-region-p) !

Or if you want it fully automated make a search
for "\startpiece" and set START, then make
a search for "\Endpiece" and set STOP. Do this
in Elisp as well.

But then you'd have to supply them (the
delimitators) as arguments so it won't
necessarily be faster because you'd have to
type them each time rather than to set
the region.

If they (the delimitators) are always the same
you could hard-code them, of course. Then it'll
be very fast to invoke :)

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: replace-regexp from A to B?

[Rodolfo Medina]

Emanuel Berg <moasen@zoho.com> writes:

> Rodolfo Medina wrote:
>
>> Is it possible, and how?, to perform
>> a replace-regexp from a certain point, e.g.
>> the current one, or from a certain
>> word/expression, up to the next occurrence of
>> a certain other word/expression...? In my
>> case, with MusiXTeX documents, the starting
>> point should be the TeX command `\startpiece'
>> and the final one `\Endpiece'. So I could
>> replace strings/expressions within a single
>> musical piece without going out of it.
>
> You can set the region manually and then use
> a function with
>
>     (goto-char START)
>     (while (re-search-forward REGEXP STOP t)
>       (replace-match TO-STRING nil nil))
>
> where START is (region-beginning) and STOP is
> (region-end). First check if there is a region
> with (use-region-p) !
>
> Or if you want it fully automated make a search
> for "\startpiece" and set START, then make
> a search for "\Endpiece" and set STOP. Do this
> in Elisp as well.
>
> But then you'd have to supply them (the
> delimitators) as arguments so it won't
> necessarily be faster because you'd have to
> type them each time rather than to set
> the region.
>
> If they (the delimitators) are always the same
> you could hard-code them, of course. Then it'll
> be very fast to invoke :)


Thanks, Yuri and Emanuel...  I've seen that a single MusiXTeX piece can be
considered as a tex paragraph, because no blank line should be inserted into
it...  So I can perform my replace-regexp with the `M-h' prefix so applying it
only to the current paragraph/piece...

Rodolfo

Re: replace-regexp from A to B?

[Emanuel Berg]

Rodolfo Medina wrote:

> Thanks, Yuri and Emanuel... I've seen that
> a single MusiXTeX piece can be considered as
> a tex paragraph, because no blank line should
> be inserted into it... So I can perform my
> replace-regexp with the `M-h' prefix so
> applying it only to the current
> paragraph/piece...

So you can do this already with
`replace-regexp'! Writing my previous answer,
I had an itchy feeling it was already there
somewhere... But who would have thought to look
at replace-regexp of all places? Err, good that
you found it anyway :)

Technically speaking tho, and I think you
already know this, `M-h' isn't a prefix to the
next function but just a command to set the
region. Once there, replace-regexp acts on it,
but it doesn't matter in what manner you set it
prior to that.

Not to say there's anything wrong with using
M-h, of course.

-- 
underground experts united
http://user.it.uu.se/~embe8573

mixing argument types (was: Re: replace-regexp from A to B?)

[Emanuel Berg]

>> Thanks, Yuri and Emanuel... I've seen that
>> a single MusiXTeX piece can be considered as
>> a tex paragraph, because no blank line
>> should be inserted into it... So I can
>> perform my replace-regexp with the `M-h'
>> prefix so applying it only to the current
>> paragraph/piece...
>
> So you can do this already with
> `replace-regexp'! Writing my previous answer,
> I had an itchy feeling it was already there
> somewhere... But who would have thought to
> look at replace-regexp of all places? Err,
> good that you found it anyway :)
>
> Technically speaking tho, and I think you
> already know this, `M-h' isn't a prefix to
> the next function but just a command to set
> the region. Once there, replace-regexp acts
> on it, but it doesn't matter in what manner
> you set it prior to that.
>
> Not to say there's anything wrong with using
> M-h, of course.

This brings me to something I have thought
about a couple of times, namely what is the
right way to write the interactive
specification of a function that reads
argument(s) from the minibuffer, AND, if
available, act on the region as well?

(defun do-a-on-b (a b &optional start stop)
  (interactive
    ;; check (use-region-p)
    (list 
      ;; ask for a
      ;; ask for b
      start
      stop)
      ;; ...
      )
    ;; ...
  ;; do it
  )

?

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: mixing argument types

[Stefan Monnier]

> (defun do-a-on-b (a b &optional start stop)
>   (interactive
>     ;; check (use-region-p)
>     (list 
>       ;; ask for a
>       ;; ask for b
>       start
>       stop)
>       ;; ...
>       )

The interactive spec can't use `start` and `stop` like you did, since
it (the interactive spec) is what is used to find the arguments to pass
to the function (i.e. to find `start`, `stop, `a`, and `b`).

So you'd write:

    (defun do-a-on-b (a b &optional start stop)
      (interactive
        (list
          (completing-read "Give me A: " '("foo" "bar"))
          (read-file-name "Give me B:")
          (region-beginning)
          (region-end)))
      ...)


-- Stefan

Re: mixing argument types

[Emanuel Berg]

Stefan Monnier wrote:

> So you'd write:
>
>     (defun do-a-on-b (a b &optional start stop)
>       (interactive
>         (list
>           (completing-read "Give me A: " '("foo" "bar"))
>           (read-file-name "Give me B:")
>           (region-beginning)
>           (region-end)))
>       ...)

Great, thanks!

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: mixing argument types

[Rodolfo Medina]

Emanuel Berg <moasen@zoho.com> writes:

> Stefan Monnier wrote:
>
>> So you'd write:
>>
>>     (defun do-a-on-b (a b &optional start stop)
>>       (interactive
>>         (list
>>           (completing-read "Give me A: " '("foo" "bar"))
>>           (read-file-name "Give me B:")
>>           (region-beginning)
>>           (region-end)))
>>       ...)
>
> Great, thanks!


What does `A' stand for...?  And foo and bar...?  And region-beginning/end...?

Excuse my unexperienced requests of explanation...

Thanks...

Rodolfo

Re: mixing argument types

[Emanuel Berg]

Rodolfo Medina wrote:

> What does `A' stand for...? And foo and
> bar...? And region-beginning/end...?

A and B doesn't stand for anything in
particular, but it can stand for a lot of
things, anything that fits. Likewise with foo
and bar: programmers use them sort of like
x and y in algebra, but not in exactly the same
way, more like telling "don't mind us, this
piece of code is carrying some other point
across, only formally, without us, it won't
work".

Sometimes foo and bar make their way into real
software, because people forget to replace them
after first being lazy failing to come up with
a name that describes what is happening. It is
most often better not to use them at all when
writing real programs.

Here, we use it as a way to describe the
mechanism of a function and its arguments, i.e.
the function itself, without any connections to
what it would do in a real program in the
real world.

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: mixing argument types

[Emanuel Berg]

Rodolfo Medina wrote:

> And region-beginning/end...?

You can set the mark with C-SPC
(`set-mark-command'), and then move point (the
cursor) around with the usual keys. You should
now see the effect of this in the buffer.
The area covered is called the region. Often,
functions operate on this region because it is
a natural way to specify what part of the
buffer should be affected by a command: first
the user sets the region, then the command is
invoked, and because there is a region, the
command affects that, rather than the whole
buffer (or something else, depending on the
command).

In Elisp code, you can find out if there is
a region with (use-region-p). You can even,
right now reading this, evaluate that (with
`C-x C-e', `eval-last-sexp') with and without
a region: it should evaluate to t or nil
accordingly.

In the Elisp code, if there is a region you use
`region-beginning' and `region-end' to delimit
the part of the buffer it covers.

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: mixing argument types

[Rodolfo Medina]

Emanuel Berg <moasen@zoho.com> writes:

> Rodolfo Medina wrote:
>
>> And region-beginning/end...?
>
> You can set the mark with C-SPC
> (`set-mark-command'), and then move point (the
> cursor) around with the usual keys. You should
> now see the effect of this in the buffer.
> The area covered is called the region. Often,
> functions operate on this region because it is
> a natural way to specify what part of the
> buffer should be affected by a command: first
> the user sets the region, then the command is
> invoked, and because there is a region, the
> command affects that, rather than the whole
> buffer (or something else, depending on the
> command).
>
> In Elisp code, you can find out if there is
> a region with (use-region-p). You can even,
> right now reading this, evaluate that (with
> `C-x C-e', `eval-last-sexp') with and without
> a region: it should evaluate to t or nil
> accordingly.
>
> In the Elisp code, if there is a region you use
> `region-beginning' and `region-end' to delimit
> the part of the buffer it covers.


Thanks you...  Clear, now.

Rodolfo