#559 new
Vincent Danen

Custom keybindings should override defaults

Reported by Vincent Danen | December 29th, 2013 @ 12:11 AM

I created a Mutt.plist with custom keybindings, some of which redefine those found in the Standard.plist (the delete, for instance, I have changed to map to "archive:" rather than "deleteMessage:" for Gmail). However, unless I edit the Standard.plist and remove the default keybinding, mine will never take as it essentially is setting "Standard, Mutt" (when I just put "Mutt" into the Custom Key Bindings field in Preferences), as opposed to setting "Mutt, Standard" so that my Mutt settings will override anything previously defined in the Standard settings.

Hopefully that makes sense.

Comments and changes to this ticket

  • benny

    benny December 29th, 2013 @ 01:20 PM

    You should only put Mutt in the custom key bindings field and then your file should take precedence. Can you check again? Also by overriding a different key (since deleteMessage: may be a special case).

  • Vincent Danen

    Vincent Danen December 29th, 2013 @ 03:32 PM

    The only thing in the Custom Key Bindings field is: "Mutt". Just the one word, nothing else.

    I also tried overriding F+0 to "previousMessage:", so I used F+1 to set the flagged state, then used F+0. It moved to the previous message as expected.

    So either the deleteMessage: command, or the "\UF728" key, seems to be a special case.

    So it does seem that my Mutt is taking precedence over Standard, except in this one case.

    I then edited the Standard.plist and changed "\UF728"'s command to be "previousMessage:" as well, which my Mutt.plist has re-mapped to "archive:". Restarting MailMate and hitting my delete key results in the message going into the archive. Curious. So Mutt is overriding Standard in this case.

    I then editing the Standard.plist again and put back:

    "\UF728" = "deleteMessage:"; // ⌦ (forward-delete)

    and now it continues to archive, not delete. Very curious.

    My last step was to replace MailMate.app with a pristine one and ensure that Standard.plist was 100% original. My customized Mutt.plist is still taking precedence.

    Maybe this was nothing after all or had some syntax error or something in my Mutt.plist? Does MailMate silently ignore plists or entries in plists if they have a syntax error?

    I'll have to try on my laptop later (where I also have MailMate installed) and see if replacing MailMate.app with a pristine copy still lets me use my customized Mutt.plist instead.

    Sorry, it feels like I may have wasted your time and my own. =(

  • Vincent Danen

    Vincent Danen December 30th, 2013 @ 12:07 AM

    Yeah, I think you can close this. Just checked on the laptop by copying a new MailMate.app to replace the old one, so as to get the pristine Standard.plist and it archives as it should. Sorry for wasting your time, it works as expected after all! Perhaps I didn't restart MailMate the first time -- it seems you need to restart for any changes to kick in (though there is nothing in the UI to indicate this).

  • benny

    benny December 30th, 2013 @ 09:13 AM

    • State changed from “new” to “resolved”

    Thanks for the update. There is no GUI feedback if the syntax in a plist file is incorrect. I think there is some output in the Console, but I'm not quite sure. (This could be improved, but the proper fix is probably to provide a GUI to edit custom key bindings.)

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket