Kurt Hackenberg wrote: >>I had `folder-hook '=lists/'` too, but `message-hook` has >>replaced that for me. I may not need `folder-hook .` >>anymore, but I haven't changed or tested it in several >>years. > > I think you don't need it. Looks like you used "folder-hook ." to > reset to the default key bindings for messages not from lists, and now > you do that with "message-hook ~A". Yes?
I checked and it is needed. If you read a list message and then move back to another folder and want to reply to a message without first opening it, you need the folder-hook to reset the default bindings. Otherwise you press 'r' and get an error that no list is found. That's not perfect, as you might store list and non-list mail in the same folder. I don't do that, so it isn't a problem I need to solve. >>Kurt wondered why you'd ever want this to behave differently >>per folder and, for me, the answer is that not all lists >>have the same customs. >> >>I want mutt to "do the right thing" when I start a reply >>without having to change my behavior based on the list to >>which I am replying. > > Sure, but you could identify the list from the headers List-*:, rather > than from what folder you stored the message in. In fact, it looks > like you do something similar above. Doesn't "message-hook ~C" detect > a message from a particular list, and set up custom key bindings for It does, but it requires that a message is read first. So if I change to a different mail folder and want to reply, the folder-hooks can be quite useful. I separate my list and non-list mail so it was pretty easy to take advantage of a folder-hook for that. I switched to message-hooks later when I joined some lists where list-reply was not the desired default. If I were to change to a list folder and then use 'r' without opening a message first, I'd have the opposite problem and I could perhaps use the folder-hook with '=lists/' again for that, but since not all lists want the same method of reply, that doesn't fully solve the issue for me. That's why I don't bother with it anymore (IIRC). I don't like to automate something unless I can fully automate it. Otherwise, I'm just setting myself up for failure when I forget I need to make some manual adjustment in some cases but not others. (That's a rough guideline and, like many guidelines, I don't apply it too stringently in life. :) It isn't perfect, but it saves me enough time and does the right thing by default in the most common cases that I haven't had to touch it in many years. -- Todd
signature.asc
Description: PGP signature
