mblaze, a Maildir-focused command line mail client
 help / color / mirror / code / Atom feed
From: John Flood <jfloodcsc@gmail.com>
To: mblaze <mblaze@googlegroups.com>
Subject: Re: Can msed write labels or label edits to the original mail file?
Date: Tue, 6 Jul 2021 13:00:35 -0700 (PDT)	[thread overview]
Message-ID: <66089c35-2552-4d4c-82f6-a9bb5d2aba87n@googlegroups.com> (raw)
In-Reply-To: <87mtrlsnlp.fsf@vuxu.org>


[-- Attachment #1.1: Type: text/plain, Size: 2340 bytes --]

Dear Leah,

Thanks very much for your response.  It answered my question and gives me a 
way forward.

This response is much delayed due to "circumstances beyond my control" 
(narrowly escaping from my country of residence to my home country for 
leave in the midst of spiking Covid, vaccine shortages, etc.)  I am just 
starting to go through the formail man page and seeing how I can figure out 
what might be blocking the effectiveness of the editlabel script. I will 
post again later. 

Thanks again,

John Flood

On Saturday, June 19, 2021 at 9:42:14 PM UTC+3 Leah Neukirchen wrote:

> John Flood <jflo...@gmail.com> writes:
>
> > One of the reasons I became interested in mblaze was failure to get the 
> > editlabel <https://blitiri.com.ar/p/other/mutt-labels/> script to work 
> with 
> > mutt. When, e.g., cleaning up my INBOX it was easy with mutt to tag and 
> > move emails from the same address to a folder, but I also had emails, 
> say, 
> > from various students that I would wish to move to a common "student" 
> > folder by first labeling them and then filtering for the label and 
> moving 
> > them at once.
> >
> > My question here is about msed which I was able to use to add a label 
> (but 
> > not edit and existing one used by Gmail like one with "\Important"). 
> > However, even though I could add a new label which would appear in the 
> > output of msed, the change did not seem to affect the actual email 
> itself. 
> > If I used mhdr, the change would not appear.
> >
> > So, am I expecting something that msed was not designed to do or is 
> there a 
> > way to write the output of msed to the email itself.
>
> Yes, indeed msed only prints the message to standard output.
>
> I would not recommend using it to manipulate persisted messages as it
> also unfolds the headers.
>
> You can use formail(1) like the editlabel script for that, it should
> only touch affected lines.
>
> -- 
> Leah Neukirchen <le...@vuxu.org> https://leahneukirchen.org/
>

-- 
You received this message because you are subscribed to the Google Groups "mblaze" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/66089c35-2552-4d4c-82f6-a9bb5d2aba87n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3699 bytes --]

      reply	other threads:[~2021-07-06 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 15:52 John Flood
2021-06-19 18:42 ` Leah Neukirchen
2021-07-06 20:00   ` John Flood [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=66089c35-2552-4d4c-82f6-a9bb5d2aba87n@googlegroups.com \
    --to=jfloodcsc@gmail.com \
    --cc=mblaze@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mblaze/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).