looking-at function behaviour

looking-at function behaviour

[Andrea Crotti]

I don't understand how I should use the looking-at function, from what I
see in the doc is not what I see happening.

--8<---------------cut here---------------start------------->8---
 (when (not (looking-at closing-char))
   (insert closing-char))
 (newline-force))))
--8<---------------cut here---------------end--------------->8---

With this code I would like to
- see if a char is before the end of line
- insert it if not

Is quite simple but it doesn't work.
And even trying now on the fly

(looking-at "a") ;; "a"

Is anyway always nil, how then am I supposed to do it given that this is
the function which reading at the info page should be used?

Re: looking-at function behaviour

[Lennart Borgman]

On Sun, Jun 6, 2010 at 4:59 PM, Andrea Crotti <andrea.crotti.0@gmail.com> wrote:
> I don't understand how I should use the looking-at function, from what I
> see in the doc is not what I see happening.

looking-at takes a regexp as argument. Is not that clear from the doc
(i.e. describe-function)?

You probably want to use char-after instead here.


> --8<---------------cut here---------------start------------->8---
>  (when (not (looking-at closing-char))
>   (insert closing-char))
>  (newline-force))))
> --8<---------------cut here---------------end--------------->8---
>
> With this code I would like to
> - see if a char is before the end of line
> - insert it if not
>
> Is quite simple but it doesn't work.
> And even trying now on the fly
>
> (looking-at "a") ;; "a"
>
> Is anyway always nil, how then am I supposed to do it given that this is
> the function which reading at the info page should be used?
>
>
>

Re: looking-at function behaviour

[Andrea Crotti]

Lennart Borgman <lennart.borgman@gmail.com> writes:

> On Sun, Jun 6, 2010 at 4:59 PM, Andrea Crotti <andrea.crotti.0@gmail.com> wrote:
>> I don't understand how I should use the looking-at function, from what I
>> see in the doc is not what I see happening.
>
> looking-at takes a regexp as argument. Is not that clear from the doc
> (i.e. describe-function)?
>
> You probably want to use char-after instead here.

Uhm no it looks like that char-after is not caring about the end of
line...

But maybe I should change my definition, since it's a string not a char
--8<---------------cut here---------------start------------->8---
(defconst default-closing-char ";"
  "default closing char, change in newline-force-close-alist if needed")
--8<---------------cut here---------------end--------------->8---

Or maybe I can just need something "string"->"regexp" corresponding,
which is even better

Re: looking-at function behaviour

[Lennart Borgman]

On Sun, Jun 6, 2010 at 6:42 PM, Andrea Crotti <andrea.crotti.0@gmail.com> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> On Sun, Jun 6, 2010 at 4:59 PM, Andrea Crotti <andrea.crotti.0@gmail.com> wrote:
>>> I don't understand how I should use the looking-at function, from what I
>>> see in the doc is not what I see happening.
>>
>> looking-at takes a regexp as argument. Is not that clear from the doc
>> (i.e. describe-function)?
>>
>> You probably want to use char-after instead here.
>
> Uhm no it looks like that char-after is not caring about the end of
> line...

Maybe i am just confusing you. Both looking-at and char-after can be
used, but I guess you have to be more careful since it did not do what
you expected.

> But maybe I should change my definition, since it's a string not a char
> --8<---------------cut here---------------start------------->8---
> (defconst default-closing-char ";"
>  "default closing char, change in newline-force-close-alist if needed")
> --8<---------------cut here---------------end--------------->8---
>
> Or maybe I can just need something "string"->"regexp" corresponding,
> which is even better
>
>
>