* Nick Wilson <[EMAIL PROTECTED]> [020124 22:13]:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> * and then Maarten den Braber blurted
> > > like this?
> > >
> > > set editor="vim +'/^$/' -c ':set textwidth=72'"
> >
> > Almost. You can only use the 'thingie' in a macro definitio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* and then Maarten den Braber blurted
> > like this?
> >
> > set editor="vim +'/^$/' -c ':set textwidth=72'"
>
> Almost. You can only use the 'thingie' in a macro definition,
> $editor is just the editor variable.
Thanks Maarten, got it now.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* and then David Champion blurted
> The "\n" terminates the ":set editor" command. It's the same action
> as pressing the ENTER key. "" inside a macro tells mutt to
> execute the function. This is bound to "m" by default. Most
> people probably
On 2002.01.24, in <[EMAIL PROTECTED]>,
"Nick Wilson" <[EMAIL PROTECTED]> wrote:
>
> * and then Maarten den Braber blurted
> > Maybe it's A Good Thing to give an example to ;-), here it is:
> >
> > bind index r noop
> > bind index m noop
>
> What's a noop?
No-op: no operation [on th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* and then Maarten den Braber blurted
> i don't get your question, do you mean how mutt knows when to reply or
> compose? that's in the 'm'ail and 'r'eply keys i use.
Yes, sorry. I put 2 and 2 together once I'd seen Wills post, and saw the
agai
* Nick Wilson <[EMAIL PROTECTED]> [020124 21:21]:
> > macro index m ":set editor=blah\n"
> > macro index r ":set editor=blah\n"
> > macro index R ":set editor=blah\n"
> > macro index L ":set editor=blah\n"
>
> Ah now I see a pattern, you can put the thingy in the set editor
> bit. So how might i
* Nick Wilson <[EMAIL PROTECTED]> [020124 21:17]:
> > bind index r noop
> > bind index m noop
>
> What's a noop?
noop means as much as 'do nothing' (no operation or something i guess),
i thought that the macros wouldn't work if i didn't do this, but maybe
they do. i don't know for sure.
> > mac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* and then Will Yardley blurted
> why not just use different macros for 'compose' and 'reply' - ie:
> (untested)
> macro index m ":set editor=blah\n"
> macro index r ":set editor=blah\n"
> macro index R ":set editor=blah\n"
> macro index L ":set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* and then Maarten den Braber blurted
> Maybe it's A Good Thing to give an example to ;-), here it is:
>
> bind index r noop
> bind index m noop
What's a noop?
> macro index m ":set editor=\"vim -c ':0;/Subject'\\\n"
> macro index r ":set edit
> I want to use a different $editor var whenever I either *reply* to or
> *compose* a message.
I don't know much about vi, but how about writing a function that greps for
/^in-reply-to:/ and takes it from there? Or a shell script like:
# untested
if grep -i ^in-reply-to $1; then vi --do-reply $1
Nick Wilson wrote:
> I want to use a different $editor var whenever I either *reply* to or
> *compose* a message. Reason being a different cursor starting point
> for each one (on the attribution for replying and on the top line for
> composing).
why not just use different macros for 'compose'
* Maarten den Braber <[EMAIL PROTECTED]> [020124 20:03]:
> * Nick Wilson <[EMAIL PROTECTED]> [020124 19:15]:
> > I want to use a different $editor var whenever I either *reply* to or
> > *compose* a message. Reason being a different cursor starting point for
> > each one (on the attribution for re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* and then Maarten den Braber blurted
> Can't you bind a macro to the key that you press when replying and when
> composing a message?
Well, I'm not sure hence the subject line to this thread. If I knew how
to do either one I would have done it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I want to use a different $editor var whenever I either *reply* to or
*compose* a message. Reason being a different cursor starting point for
each one (on the attribution for replying and on the top line for
composing).
I'm not sure how to d
* Nick Wilson <[EMAIL PROTECTED]> [020124 19:15]:
> I want to use a different $editor var whenever I either *reply* to or
> *compose* a message. Reason being a different cursor starting point for
> each one (on the attribution for replying and on the top line for
> composing).
> I'm not sure how
15 matches
Mail list logo