From: Tomi Ollila <tomi.ollila@iki.fi>
To: inwit <inwit@sindominio.net>, notmuch@notmuchmail.org
Subject: Re: Folder+tags
Date: Sun, 27 Dec 2020 23:09:17 +0200 [thread overview]
Message-ID: <m2lfdjj6rm.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <C83QJSBIYB03.ARGFEBRYEMNY@bisio>
On Sun, Dec 27 2020, inwit@sindominio.net wrote:
> On Sun Dec 27, 2020 at 2:12 PM CET, Tomi Ollila wrote:
>> On Sun, Dec 27 2020, inwit@sindominio.net wrote:
>>
>> There sure is notmuch-after-tag-hook (in emacs MUA), but -hooks don't
>> take argument(s) so how does it know what was tagged (cannot remember
>> if there are let-bound (dynamically bound!) variables that could have
>> such information).
> Apparently (I'm a total noob wrt elisp), the hook should know what was
> tagged and how it was tagged. In its documentation it reads:
> «'tag-changes' will contain the tags that were added or removed as a
> list of strings of the form "+TAG" or "-TAG". 'query' will be a string
> containing the search query that determines the messages that were
> tagged."
nos that you said it, query is a variable the hook can access to know what
was tgged. filnames it doesn't contain. with the query you can find the
filenames with 'notmuch search --output=files query
(writing on mobiledvice in a moving train, therefore terse)
Tomi
>
>>
>> Whateveruuuuuuch way, tags are assigned to Message-Id:, so you'd need to find
>> the filename.
> Having the 'query' mentioned above should be enough to find the
> filename, shouldn't it?
>
>> With shell-command you can do notmuch | xargs pipeline
>> (plain 'mv' w/ 'shell-command' would have been easily replaced w/
>> 'rename-file' if that were enough).
> I'm not sure if I get what you're trying to say: is rename-file not
> enough?
>
> In any case, if there's really a way to pass 'tag-changes' and 'query'
> to such a hook, I could use that hook to move the file with either 'mv'
> with 'shell-command' or directly with rename-file, am I wrong?
>
> In any case, I first need to actually learn elisp. This seems as the
> right reason to finally get into it.
>
> Thanks for your help.
>
> Salud,
>
>>
>> >
>> > Salud,
>>
>> Tomi
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
next prev parent reply other threads:[~2020-12-27 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 11:53 Folder+tags inwit
2020-12-24 13:59 ` Folder+tags Alan Schmitt
2020-12-25 16:41 ` Folder+tags inwit
2020-12-25 8:04 ` Folder+tags Jaume Devesa
2020-12-25 17:27 ` Folder+tags inwit
2020-12-27 11:59 ` Folder+tags inwit
2020-12-27 13:12 ` Folder+tags Tomi Ollila
2020-12-27 17:14 ` Folder+tags inwit
2020-12-27 21:09 ` Tomi Ollila [this message]
2020-12-28 16:51 ` Folder+tags inwit
2021-01-03 18:09 ` Folder+tags inwit
2021-01-03 20:01 ` Folder+tags Tomi Ollila
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lfdjj6rm.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=inwit@sindominio.net \
--cc=notmuch@notmuchmail.org \
/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://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).