Re: find all messages in threads where one message matches
On Sat, Nov 03, 2018 at 10:45:59PM +0100, Francesco Ariis wrote: > Hello Ben, > > On Sat, Nov 03, 2018 at 04:45:42PM -0400, Ben Fitzgerald wrote: > > is there any way to tag all messages in all threads where a search pattern > > matches one more messages in a thread? > > Sure, try > > ~(~f Ian) > > to get every thread were Ian posted a message. Is that what you want? perfect, many thanks! -- Ben Fitzgerald
Re: Composing blocks checking for new
On Sat, Nov 03, 2018 at 09:53:07AM +1100, Cameron Simpson wrote: > My composition mode always opens the composition in a new tmux session (or > screen Thank you for the detailed write up. I always enjoy reading these kinds of posts: nuggets of wisdom from long-time users. > mutt -e 'set editor=vim-flowed' -e 'unset signature' -H "$filename" Instead of "-e 'unset signature'", you may want to try "-e 'set resume_draft_files'" which turns off even more undesired processing, like user-defined headers. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mwahahaha! composing in a tmux split pane
On the topic of firing off composition in a separate window so that the main mutt can continue on immediately, monitoring for new email etc, I'm working on a change to my muttedit script to do all this inside tmux: Start the main mutt in a tmux session. Have muttedit: - spawn a detached tmux session for composition as at present, detached - split the current tmux window and attach to the composition session in the new pane This effectively "opens a composition window below the index view". Like an unadorned mutt reply does, but detachable. There are still some pain points :-( Cheers, Cameron Simpson
Re: Composing blocks checking for new
On 04Nov2018 09:22, Kevin J. McCarthy wrote: On Sat, Nov 03, 2018 at 09:53:07AM +1100, Cameron Simpson wrote: My composition mode always opens the composition in a new tmux session (or screen Thank you for the detailed write up. I always enjoy reading these kinds of posts: nuggets of wisdom from long-time users. Thanks. mutt -e 'set editor=vim-flowed' -e 'unset signature' -H "$filename" Instead of "-e 'unset signature'", you may want to try "-e 'set resume_draft_files'" which turns off even more undesired processing, like user-defined headers. Wayne Campbell: So, do you... come to Milwaukee often? Alice Cooper: Well, I'm a regular visitor here, but Milwaukee has certainly had its share of visitors. The French missionaries and explorers were coming here as early as the late 1600s to trade with the Native Americans. Pete: In fact, isn't "Milwaukee" an Indian name? Cooper: Yes, Pete, it is. Actually it's pronounced "mill-e-wah-que," which is Algonquin for, "the good land." Wayne: I was not aware of that. I see that my local copy of the 1.9.4 manual has 360 entries in section 3; it looks like I have some revising to do. Thanks! Cheers, Cameron Simpson
Re: Composing blocks checking for new
On 03Nov2018 10:59, Cameron Simpson wrote: On 03Nov2018 09:53, Cameron Simpson wrote: The tmux session is done thus: set editor=muttedit and muttedit is here: https://bitbucket.org/cameron_simpson/css/src/tip/biGn/muttedit Of course, that should be: https://bitbucket.org/cameron_simpson/css/src/tip/bin/muttedit Updated script a little: streamlines the tmux session setup versus the window programme, cleans up the temp file. Cheers, Cameron Simpson
