Re: Problems with save-hook
Hi Nicolas :)
* Nicolas Rachinsky <list@xxxxxxxxxxxx> dixit:
> > > > to.) the rest simply got ignored. I haven't a 'default_hook', because
> > > > I want more control on matching and because I like it. I've tested
> > > > with other expressions, like '^.*Movement.*$', etc... so it doesn't
> > > > seems to be a problem with regex. How can I debug it?
> > > ~A _is_ a default hook.
> > I was talking about the 'default_hook' variable, sorry O:)
> Ah. But if you use an expression like '^.*Movement.*$'
Again I was trying to confuse you, sorry O:))) I meant:
send-hook '~s ^.*Movement.*$' =Whatever
> you will use $default_hook.
Obviously ;)) But I use the full syntax, sorry. It was a typo. My
'$default_hook' variable is empty.
> > > And IIRC then the first matching save-hook terminates the search
> > > (unlike e.g. folder-hooks). Try reversing the order of the hooks.
> > Where in the manual can I consult the order of matching in the
> > hooks?
> Good question. I don't know it. But it seems I guessed right every
> time I had multiple matching hooks.
So I need to try and experiment...
> > Currently I don't know if the default hook must be the first
> > or the last :(
> You're using default hook for two different things in an attempt to
> confuse us, aren't you? :-)
You caught me O:) Now I was talking about a hook with '~A' (or
'.' if you have a non-empty '$default_hook' ;)
Thanks for all. I'll try my best to do things correctly with
hooks trying for different combinations ;)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/