Re: [SOLVED] set include=yes bypasses Compose Menu
Mon 15.Apr'13 at 10:18:43 -0700 Kevin J.
McCarthy
rj wrote:
On Mon 15 at 12:04 AM -0400, rj r...@panix.com wrote:
That would mean that although this line cures the problem, something else
is causing it.
What was causing it was this key binding:
bind index,pager { reply# Restored to 'r' in macro below.
combined with this macro:
macro index,pager r :set editor='vim +10'^M{^M reply with quoting
Great news that you figured it out!
I don't know if you are using the { binding too, or have done that
just to use inside your macro. In case it's the latter, note that you
can actually use enter and reply inside the macro instead:
macro index,pager r enter-commandset editor='vim +10'enterreply
reply with quoting
-Kevin
RJ, Kevin's macro here is the usual way macros are written, as opposed
to using control sequences as you've done. It's a lot clearer when
looking at it. And it's best to write the macro using explicit commands
rather than using key bindings you've set elsewhere in your muttrc. I
read further down thread you've still got some issues with your macro?
What exactly is happening or not happening that you would like to
change?
--
James Griffin: jmz at kontrol.kode5.net
jmzgriffin at gmail.com
A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: [SOLVED] writing macros correctly
On Tue 16 at 09:00 AM +0100, James Griffin j...@kontrol.kode5.net wrote:
RJ, Kevin's macro here is the usual way macros are written, as opposed
to using control sequences as you've done. It's a lot clearer when
looking at it. And it's best to write the macro using explicit commands
rather than using key bindings you've set elsewhere in your muttrc.
Thanks for your response and for the reality check. I've replaced the
following macros:
# Reply w/quoting, put cursor on line 10:
macro index,pager r :set editor='vim +10'^M{^M reply with quoting
# Reply w/out quoting, put cursor at line 10:
macro index,pager R :set editor='vim +10'^M{ reply without quoting
# List-reply w/quoting, put cursor on line 10:
macro index,pager p :set editor='vim +10'^M} list-reply with quoting
# List-reply w/out quoting, put cursor at line 10:
macro index,pager _R :set editor='vim +10'^M} list-reply without quoting
with these:
# Reply w/quoting, put cursor on line 10:
macro index,pager r enter-commandset editor='vim +10'enterreply
reply with quoting
# Reply w/out quoting, put cursor at line 10:
macro index,pager R enter-commandset editor='vim +10'enterreply
reply with quoting
# List-reply w/quoting, put cursor on line 10:
macro index,pager p enter-commandset editor='vim +10'enterreply
list-reply with quoting
# List-reply w/out quoting, put cursor at line 10:
macro index,pager _R enter-commandset editor='vim +10'enterreply
list-reply without quoting
And I've gotten rid of all the unnecessary key-bindings and any other
macros with the obscure-looking control sequences.
I read further down thread you've still got some issues with your macro?
What exactly is happening or not happening that you would like to change?
Actually, there are no more issues. What I *thought* was an issue was that
when I replied to a group with r (regular reply) instead of my defined
p (group-reply), I was startled to see the prompt:
Reply to name-of-mailing-list? ([yes]/no):
But I realized that's completely as it should be. I think I was previously
set up for r to work with lists also.
--
Energizer Bunny arrested - charged with battery.
Re: [SOLVED] writing macros correctly
rj wrote: # List-reply w/quoting, put cursor on line 10: macro index,pager p enter-commandset editor='vim +10'enterreply list-reply with quoting # List-reply w/out quoting, put cursor at line 10: macro index,pager _R enter-commandset editor='vim +10'enterreply list-reply without quoting Did you intend to use list-reply instead of reply for the two macros above? Otherwise, nice job cleaning them up. They look much more readable and less likely for a stray character to sneak into them. -Kevin signature.asc Description: Digital signature
Re: writing macros correctly
On Tue 16 at 12:15 PM -0700, Kevin J. McCarthy ke...@8t8.us wrote: rj wrote: macro index,pager p enter-commandset editor='vim +10'enterreply list-reply with quoting macro index,pager _R enter-commandset editor='vim +10'enterreply list-reply without quoting Did you intend to use list-reply instead of reply for the two macros above? Otherwise, nice job cleaning them up. They look much more readable and less likely for a stray character to sneak into them. Yes! I did, thank you. But the second one is identical to the first. I tried the following for reply without quoting, and it works, but after using it, if I want to reply *with* quoting, using r, I get no-quoting again, so this can't be right: macro index,pager R enter-commandset include='no'enterenter-commandset editor='vim +10'enterreply reply without quoting pgph4atoU0C7H.pgp Description: PGP signature
Re: writing macros correctly
Incoming from rj:
On Tue 16 at 12:15 PM -0700, Kevin J. McCarthy ke...@8t8.us wrote:
rj wrote:
macro index,pager p enter-commandset editor='vim +10'enterreply
list-reply with quoting
macro index,pager _R enter-commandset editor='vim +10'enterreply
list-reply without quoting
Did you intend to use list-reply instead of reply for the two macros
Yes! I did, thank you. But the second one is identical to the first.
I tried the following for reply without quoting, and it works, but
after using it, if I want to reply *with* quoting, using r, I get
no-quoting again, so this can't be right:
macro index,pager R enter-commandset
include='no'enterenter-commandset editor='vim +10'enterreply
reply without quoting
Forgive me if I'm doing a Department of Redundancy Department thing.
Why are you doing this? In mutt, I hit r, and emacs fires up with
the contents of the email I'm replying to. What are you doing that
improves or differs from that, and why are you needing to stuff a
macro to do it?
I'm just trying to understand the situation, and I'm not seeing why
you're going to such lengths for something that I think is already
there. :-|
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
signature.asc
Description: Digital signature
Re: writing macros correctly
rj wrote: Yes! I did, thank you. But the second one is identical to the first. I tried the following for reply without quoting, and it works, but after using it, if I want to reply *with* quoting, using r, I get no-quoting again, so this can't be right: The settings you change are not local to the macro. So when you turn off include, it will stay off even after you finish replying. If you have other macros where you want it on, you'll have to turn it back on for each of those. By the way, you can combine various setting changes into a single set command to make your macro less lengthy: macro index,pager r enter-commandset include=yes editor='vim +10'enterreply reply with quoting macro index,pager R enter-commandset include=no editor='vim +10'enterreply reply without quoting macro index,pager p enter-commandset include=yes editor='vim +10'enterlist-reply list-reply with quoting macro index,pager _R enter-commandset include=no editor='vim +10'enterlist-reply list-reply without quoting -Kevin signature.asc Description: Digital signature
Re: writing macros correctly
On Tue 16 at 04:43 PM -0600, s. keeling keel...@nucleus.com wrote: Why are you doing this? In mutt, I hit r, and emacs fires up with the contents of the email I'm replying to. What are you doing that improves or differs from that, and why are you needing to stuff a macro to do it? For reply with quoting, you're absolutely right. I can comment-out the two macros for RWQ and list-RWQ and get the exact thing I get with them. So I'll get rid of them. (And thanks for your prodding.) I think when I set them long ago, the cursor wasn't placing itself where I wanted it, and instead of fixing that correctly, I wrote a quick macro to be done with it, since that was what I knew how to do (incorectly, as it turns out, but enough to get them to work). It was a quick fix. There may also, for all I know, be a one-keypress solution for reply with *no* quoting, but until I find out what it is, I'll leave my macros for that in place. I'm just trying to understand the situation, and I'm not seeing why you're going to such lengths for something that I think is already there. :-| No, that's fine -- I appreciate it. --- Experience is something you don't get until just after you need it.
Re: writing macros correctly
On Tue 16 at 04:21 PM -0700, Kevin J. McCarthy ke...@8t8.us wrote: The settings you change are not local to the macro. So when you turn off include, it will stay off even after you finish replying. If you have other macros where you want it on, you'll have to turn it back on for each of those. I did just get that and was about to post: macro index,pager R enter-commandset editor='vim +10'enterenter-command\ set include=noenterreplyenter-commandset include=yesenter\ reply without quoting I may also be able to get rid of the '+10' setting as, which s. keeling pointed out, seems to be unneccesary. By the way, you can combine various setting changes into a single set command to make your macro less lengthy: macro index,pager r enter-commandset include=yes editor='vim +10'enterreply reply with quoting macro index,pager R enter-commandset include=no editor='vim +10'enterreply reply without quoting macro index,pager p enter-commandset include=yes editor='vim +10'enterlist-reply list-reply with quoting macro index,pager _R enter-commandset include=no editor='vim +10'enterlist-reply list-reply without quoting And that's what I was wondering about the syntax for, since my version above was getting very long. Thank you all.
Re: writing macros correctly
Incoming from rj:
On Tue 16 at 04:21 PM -0700, Kevin J. McCarthy ke...@8t8.us wrote:
I may also be able to get rid of the '+10' setting as, which s. keeling
pointed out, seems to be unneccesary.
I did not say that. I didn't even mean to imply it. I just wondered
why you were banging your head on macros, which appear to be
unnecessary. Whatever you want to do (including using vi(m) instead
of emacs :-) with mutt's fine by me.
Carry on.
Ya know, ...
There's a muttrc.el that makes mutt + emacs gorgious? Just sayin'.
:-) I do like vi(m) too; don't get me wrong.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
signature.asc
Description: Digital signature
Re: writing macros correctly
On Tue 16 at 06:25 PM -0600, s. keeling keel...@nucleus.com wrote: Incoming from rj: On Tue 16 at 04:21 PM -0700, Kevin J. McCarthy ke...@8t8.us wrote: I may also be able to get rid of the '+10' setting as, which s. keeling pointed out, seems to be unneccesary. I did not say that. I didn't even mean to imply it. Apologies, I think I included it by extension when I discovered that it also wasn't necessary in the sense you were talking about insofar as without the macro I still landed exactly at line 10.
[off-list] Re: writing macros correctly
Incoming from rj:
On Tue 16 at 06:25 PM -0600, s. keeling keel...@nucleus.com wrote:
Incoming from rj:
On Tue 16 at 04:21 PM -0700, Kevin J. McCarthy ke...@8t8.us wrote:
I may also be able to get rid of the '+10' setting as, which s. keeling
pointed out, seems to be unneccesary.
I did not say that. I didn't even mean to imply it.
Apologies, I think I included it by extension when I discovered that it
No problemo. :-) I was just playin' wit cha. I'm a geek, so I want
to start *everything* from the beginning. Okay, and then what
happens? etc.
also wasn't necessary in the sense you were talking about insofar as
without the macro I still landed exactly at line 10.
I just want to help people think. Understand the problem, what are
the options, where do we go from here, and what traps await us? We're
better than this stuff. All's necessary is for us to bang our heads
on it. It'll fall over; eventually.
De nada. Have fun. :-)
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
signature.asc
Description: Digital signature
Mutt secretly adds Content-Length headers?
I'm using Maildir. mutt -R against folder A makes no mods as expected. mutt -f against folder A moves new msgs to cur with no mods as expected. But mutt -f against A, operation of tagging messages and 'C'opying them to some other folder B causes Content-Length headers to be added to each message. mutt didn't need that header to operate well in the original folder. In general, can't think of any reason to modify any Maildir message on disk and view this as tainting the msgs with unecessary and un-asked-for mods. And it breaks external indexes of security/archive crypto hashes. I'm not referring to the msg filename (maildir spec) or its location (as instructed), just the content of the msg file itself. And it also appears to be lying by preserving the msg file modification time when it adds this header. [1] Why does mutt do this? What else is being surreptitiously modified during mutt operation? I'd like to ticket it. [1] Of course it should preserve the msg file mod time when merely copying or moving messages.
unsubscribe Mutt Users
--- ke...@8t8.us wrote: From: Kevin J. McCarthy ke...@8t8.us To: mutt-users@mutt.org Subject: Re: [SOLVED] writing macros correctly Date: Tue, 16 Apr 2013 12:15:04 -0700 rj wrote: # List-reply w/quoting, put cursor on line 10: macro index,pager p enter-commandset editor='vim +10'enterreply list-reply with quoting # List-reply w/out quoting, put cursor at line 10: macro index,pager _R enter-commandset editor='vim +10'enterreply list-reply without quoting Did you intend to use list-reply instead of reply for the two macros above? Otherwise, nice job cleaning them up. They look much more readable and less likely for a stray character to sneak into them. -Kevin
