Re: Understanding message deletion model
On Thu, Nov 10, 2022 at 07:18:26PM -0800, Kevin J. McCarthy wrote: > On Thu, Nov 10, 2022 at 08:47:44PM -0500, Jason Franklin wrote: > > Now, if I re-open mutt, the message is gone... completely. I'm confused > > as to why the message was removed even though I typed 'n' at the prompt > > for whether or not to proceed with the purge. > > > > Are "purging" and "deleting" not the same thing? > > According to the IMAP protocol, they are not. Deleting is marking the > message with the "deleted" flag, which normally doesn't automatically remove > it from the mailbox. Purging (expunging) will remove messages marked as > "deleted" from the mailbox. Very good to know. It looks like I'm marking deleted with 'd', exiting without purging via mutt, then my provider knows to purge the message anyway. It seems like an odd distinction to separate "purging" from "moving to trash folder." For example, let's say I mark a message to be deleted, and I have mutt set to say "yes" to the purge prompt at the end of my session, but my computer dies before I can properly close out my mutt process. Will I then lose those messages as I have done here? Thanks! -- Jason
Re: Understanding message deletion model
On Fri, Nov 11, 2022 at 11:17:06AM +0800, 謝晉凡 Hsieh Chin Fan via Mutt-users wrote: > > I already checked my trash folder, and it's not there. > > Based on http://www.mutt.org/doc/manual/#trash: > >If set, this variable specifies the path of the trash folder where >the mails marked for deletion will be moved, instead of being >irremediably purged. > > Did you realy set $trash ? Use the following command to take a look: > > :set ?trash Oh, sorry. I think I wasn't being clear. I meant that I checked my IMAP folder called "Trash", not the folder designated by $trash. That setting is empty in my new configuration, so mutt doesn't know anything about a trash folder. -- Jason
Re: Understanding message deletion model
On Fri, Nov 11, 2022 at 10:27:59AM +0800, 謝晉凡 Hsieh Chin Fan via Mutt-users wrote: > On Thu, Nov 10, 2022 at 08:47:44PM -0500, Jason Franklin wrote: > > Now, if I re-open mutt, the message is gone... completely. I'm confused > > as to why the message was removed even though I typed 'n' at the prompt > > for whether or not to proceed with the purge. > > > > Where did this message go? I already checked my trash folder, and it's > > not there. Unfortunately, I've been re-writing my configs, so the trash > > folder is not named yet. > > Did you read the message? Maybe it is moved to $mbox. It looks like my $mbox value has no effect since my configuration is using the default (which sets $move to no). I checked my home dir and found no ~/mbox file. :/ -- Jason Franklin
Understanding message deletion model
Greetings: My journey toward a better mutt configuration continues. :) Today, I noticed that, under the defaults, this happens... 1. Hit 'd' on the selected message in the index. 2. Hit 'q'. 3. Mutt prompts something like: "Purge messages selected for deletion?" 4. Hit 'n'. 5. Mutt quits. Now, if I re-open mutt, the message is gone... completely. I'm confused as to why the message was removed even though I typed 'n' at the prompt for whether or not to proceed with the purge. Are "purging" and "deleting" not the same thing? Where did this message go? I already checked my trash folder, and it's not there. Unfortunately, I've been re-writing my configs, so the trash folder is not named yet. Many thanks in advance for your help! -- Jason Franklin
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 09:26:04AM +0200, Jakub Jindra wrote: > Hi Jason, > > You're looking for config option [1]header_color_partial > > 1. http://www.mutt.org/doc/manual/#header-color-partial > > set header_color_partial = yes > color hdrdefault FG BG > color header FG BG "REGEX" > color header FG1 BG1 "REGEX1" > > tune the colors FG, BG and REGEX to your needs. I came across that option in the manual, but I couldn't make it work at the time. I will have to play around with it a bit. At least I was looking in the right place. Thanks, Jakub! -- Jason
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 09:51:29PM +1000, raf wrote: > On Sun, Jun 05, 2022 at 11:32:34AM +0200, Anton Sharonov > wrote: > > Will usage of display_filter option with your perl script below not be > > already sufficient solution even without procmail? > > Good thinking. I just tried it and it works great. > > set display_filter = /home/me/bin/fix-mail-headers-filter This is really helpful! Many thanks to Anton and raf. :) -- Jason
Two questions regarding header display
Greetings: I have two questions regarding header display... First, can the pager display header names in bold if the terminal supports it? Second some senders have weird capitalization of headers. Is it possible to display some canonical representation of any given standard header? To clarify, if the header is sent as "reply-to", I would like to always see "Reply-To" in the pager. Thanks! -- Jason
Re: Escape from prompt
On Mon, May 16, 2022 at 03:13:34PM +, Joel Buckley wrote: > control-g is the default "escape" sequence in Mutt. From the manual: > > ^G is the generic “abort” key in Mutt. In addition to the line > > editor, it can also be used to abort prompts. Generally, typing ^G > > at a confirmation prompt or line editor should abort the entire > > action. Awesome! There is a way to do it. I'm using Mutt v1.13.2 on Ubuntu 20.04, so my version is a bit old. The manual on my box does not have this section. There is a table showing that ^G -> abort, but I missed it when searching for it earlier. > According to this link, it is not possible to re-bind the ^g > operation... Well, fooey. I'll just have to get in the habit of using ^G. :) Many thanks! -- Jason
Escape from prompt
Greetings: I have another question! Let's say I am looking at the index and I hit the 'm' key to compose a new message. Mutt then issues a prompt like this... To: Hitting the key doesn't abort this process like I would expect. The way I get around this is to hit and then just tell Mutt "No" when it asks if I want to exit. That is, if I start a process that has a series of prompts, I would expect for the key to abort the action I'm performing. Is there a way to have the key get me out of a command-line prompt? Thanks! -- Jason
Re: Reading from IMAP folders with '.' in name
On Sun, May 15, 2022 at 12:43:45PM -0700, Kevin J. McCarthy wrote: > On Sun, May 15, 2022 at 03:18:44PM -0400, Jason Franklin wrote: > > How might I allow for folder names that match a normal email address > > including the '.' and '@' characters? > > Try putting: > set imap_delim_chars = '/' > set sidebar_delim_chars = '/' > in your muttrc and see if it helps. It works! Most excellent! > By default, Mutt treats both '/' and '.' as folder separator characters, and > that may be causing the issue. Good to know. I can now read all of my mail! :) Thanks so much! -- Jason
Reading from IMAP folders with '.' in name
Greetings: I am a new mutt user. I like it so far! One hurdle is giving me a real headache at the moment. My mail provider uses IMAP, and I use aliases with folders and routing rules to allow for multiple email addresses under one account. My folder layout is like this... Inbox/ |-- ja...@oneway.dev/ |-- o...@example.org/ `-- t...@example.org/ In the mutt sidebar (which I love!), it looks like this... INBOX INBOX/jason@oneway/dev INBOX/one@example/org INBOX/two@example/org When I attempt to open one of the subfolders with 'c' and then by selecting the folder, mutt tells me that the mailbox does not exist and stops there. Renaming the folders to something without '.' or '@' characters allows me to access them just fine. Thus, I think the folder name has something to do with it. How might I allow for folder names that match a normal email address including the '.' and '@' characters? This will at least get me to where I can read all of my mail easily. Many thanks in advance! -- Jason Franklin
