custom macro for "q" key
Hello, I have "q" key bound to "quit", and then I have custom macro bound to "c": macro index,pager c "?" When I start mutt, I automatically land in "Inbox", and "q" exits. When I press "c" anywhere in mutt, I get list of my folders, and can go into them. When inside any of the folder, "q" also exists mutt. I would like to change the behavior of "q", so that pressing "q" when I am inside any of the folders, mutt goes back to the list of folders (same as if I had pressed "c"). And only if I am already in the list of folders, then "q" exists mutt. What I want is similar to "q" behavior when in inbox, and composing message. When I cancel the compose with "q", I don't exit mutt, but instead land in Inbox again. I would like to keep that behavior. I guess, I will need to create custom macro for "q" ? Can anybody suggest how to do it? thank you,
Re: Preventing Deletion (Detachment) of the Main Message
On Sun, Aug 29, 2021 at 09:33:01PM -0400, sunnycemet...@gmail.com wrote: Hello. The command is detach-file (bound to D by default). I would like to prevent mutt from deleting the main message, as I will probably never find myself wanting to invalidate emails this way--but I *might* find myself accidentally pressing the wrong keyboard key and deleting with no recourse an entire, painstakingly composed message. Ah, that sucks. I'm sorry that happened. Mutt prevents deleting the very last message part, but that doesn't help when the message has other attachments. I'll add a prompt to confirm deleting the main message. In the mean time, perhaps consider 'bind compose D noop'. You could still manually ':exec detach-file' for the rare cases you need do that. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Preventing Deletion (Detachment) of the Main Message
Hello. The command is detach-file (bound to D by default). I would like to prevent mutt from deleting the main message, as I will probably never find myself wanting to invalidate emails this way--but I *might* find myself accidentally pressing the wrong keyboard key and deleting with no recourse an entire, painstakingly composed message. Not that such a thing happened five minutes ago or anything... Anyway, is there a way to do this? Ideally, I would like to prevent detachment of the main message completely (e.g. by never detaching attachment #1). If this is not possible, perhaps there is a quadoption to confirm before detaching *anything* (couldn't find one), a configurable list of MIME types that cannot be detached (likewise), or even just a way to force mutt to leave the main message in $tmpdir and not delete it immediately? Please help! Thank you.
Re: Headers in Editor
On Sun, Aug 29, 2021 at 06:02:43PM +0200, Rene Kita wrote: The idea behind this is, that can you view/edit the headers while replying. That's why the headers are cleared if you delete these lines. They want end up in the body of that mail. As already that said in another reply, 'set edit_headers=no' disables this feature. Just a brief addition: you can still use the header-editing functionality if in the send screen (the one where you press 'y' and the message gets sent) you press 'E'. That'll open the editor with the headers included. 'e' gets you to the regular editor. Cheers, -- José María (Chema) Mateos || https://rinzewind.org
Re: disable gpg in mutt
On Sun, Aug 29, 2021 at 07:27:37PM +0200, Fourhundred Thecat wrote: how can I show the message source? ie the message in its encrypted form You can use the attachment menu, reached by 'v' as the message suggests, and then one of the functions to view a message part. If you want to view the entire message in raw form, you can use '|' in the pager or message index, and pipe it to less, for example. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: disable gpg in mutt
> On 2021-08-29 18:27, Kevin J. McCarthy wrote: On Sun, Aug 29, 2021 at 06:49:31AM +0200, Fourhundred Thecat wrote: Why is mutt still trying to decrypt the message? Please, reread my responses in this thread: "you could try recompiling mutt using the '--disable-pgp' and '--disable-gpgme' configure options" Have you reconfigured with both of those options? "Check the output of mutt -v and look for -CRYPT_BACKEND_CLASSIC_PGP and -CRYPT_BACKEND_GPGME in the output." Do you see *both* of those strings in the output. Your most recent post still showed +CRYPT_BACKEND_CLASSIC_PGP, meaning you haven't disabled classic pgp mode (using --disable-pgp). indeed, I did have only --disable-gpgme. Now I recompiled with both --disable-gpgme and --disable-pgp When I open gpg encrypted message, I see this: [-- Attachment #1: PGP/MIME version identification --] [-- Type: application/pgp-encrypted, Encoding: 7bit, Size: 0.1K --] [-- application/pgp-encrypted is unsupported (use 'v' to view this part) --] [-- Attachment #2: OpenPGP encrypted message --] [-- Type: application/octet-stream, Encoding: 7bit, Size: 2.6K --] [-- application/octet-stream is unsupported (use 'v' to view this part) --] how can I show the message source? ie the message in its encrypted form
Re: disable gpg in mutt
On Sun, Aug 29, 2021 at 06:49:31AM +0200, Fourhundred Thecat wrote: Why is mutt still trying to decrypt the message? Please, reread my responses in this thread: "you could try recompiling mutt using the '--disable-pgp' and '--disable-gpgme' configure options" Have you reconfigured with both of those options? "Check the output of mutt -v and look for -CRYPT_BACKEND_CLASSIC_PGP and -CRYPT_BACKEND_GPGME in the output." Do you see *both* of those strings in the output. Your most recent post still showed +CRYPT_BACKEND_CLASSIC_PGP, meaning you haven't disabled classic pgp mode (using --disable-pgp). -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Headers in Editor
On Sun, Aug 29, 2021 at 09:24:36AM -0400, David J. Ring, Jr. wrote: > I have the strangest problem. > > When I reply to a message in a new installation of mutt, what will > eventually become the addresses, and subject, and In-Reply-To threading > informaton becomes the top lines of the editor! > > If I write over them, or delete them, I have no addresses when sending > the message. > > How do I fix this? The idea behind this is, that can you view/edit the headers while replying. That's why the headers are cleared if you delete these lines. They want end up in the body of that mail. As already that said in another reply, 'set edit_headers=no' disables this feature.
Re: Headers in Editor
How could I have missed that! Thank you - I have NO idea why it's working on one computer but not this one. But now thank to your help it's working fine. Thank you! David On 08/29/ , ಚಿರಾಗ್ ನಟರಾಜ್ wrote: > 12021/06/00 03:92.08 ನಲ್ಲಿ, "David J. Ring, Jr." ಬರೆದರು: > > I have the strangest problem. > > > > When I reply to a message in a new installation of mutt, what will > > eventually become the addresses, and subject, and In-Reply-To threading > > informaton becomes the top lines of the editor! > > > > If I write over them, or delete them, I have no addresses when sending > > the message. > > > > How do I fix this? > > > > I've reinstalled mutt, I've copied over my configuration files from one > > computer to this one. > > > > The only thing I can think of is that I edited a few files with pluma > > instead of nano. > > > > Also on the main screen of the message it says: > > > > Security: None (OppEnc mode) while all my other mutt programs say something > > pgp/mime. > > > > I am also running mutt inside Xorg MATE Desktop. > > > > Any suggestions? > > > > Thanks, > > > > David > > ' > > You'll want to set the variable edit_headers to no. That should fix it! > > HTH! > > - Chiraag > -- > ಚಿರಾಗ್ ನಟರಾಜ್ > Pronouns: he/him/his
Re: Headers in Editor
12021/06/00 03:92.08 ನಲ್ಲಿ, "David J. Ring, Jr." ಬರೆದರು: > I have the strangest problem. > > When I reply to a message in a new installation of mutt, what will > eventually become the addresses, and subject, and In-Reply-To threading > informaton becomes the top lines of the editor! > > If I write over them, or delete them, I have no addresses when sending > the message. > > How do I fix this? > > I've reinstalled mutt, I've copied over my configuration files from one > computer to this one. > > The only thing I can think of is that I edited a few files with pluma > instead of nano. > > Also on the main screen of the message it says: > > Security: None (OppEnc mode) while all my other mutt programs say something > pgp/mime. > > I am also running mutt inside Xorg MATE Desktop. > > Any suggestions? > > Thanks, > > David > ' You'll want to set the variable edit_headers to no. That should fix it! HTH! - Chiraag -- ಚಿರಾಗ್ ನಟರಾಜ್ Pronouns: he/him/his publickey - mailinglist@chiraag.me - b0c8d720.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Headers in Editor
I have the strangest problem. When I reply to a message in a new installation of mutt, what will eventually become the addresses, and subject, and In-Reply-To threading informaton becomes the top lines of the editor! If I write over them, or delete them, I have no addresses when sending the message. How do I fix this? I've reinstalled mutt, I've copied over my configuration files from one computer to this one. The only thing I can think of is that I edited a few files with pluma instead of nano. Also on the main screen of the message it says: Security: None (OppEnc mode) while all my other mutt programs say something pgp/mime. I am also running mutt inside Xorg MATE Desktop. Any suggestions? Thanks, David '
