mutt-kz November 2013

mutt-kz@lists.fedoraproject.org

10 participants
12 discussions

rename: No such file or directory (errno = 2)
by Vladimir Marek 20 Nov '13

20 Nov '13

Hi, Since I'm usually using several mail clients (from phone, old mutt, mutt-kz) it happens quite often that mutt complains. rename: No such file or directory (errno = 2) and the only thing I can do about it is to kill whole mutt. What I believe is happening is that if I view unread mail, mutt remembers that it has to move the mail once it leaves current inbox. But before that, someone else touches the mail (probably moving the message from 'new' directory to 'cur'. After that mutt-kz can't find the original file and complains with the error message. This seems to be problem in the mutt maildir handling rather than in the notmuch addon, still I wonder if you saw that or even better have some plans on tackling that :) Cheers -- Vlad

5 10

uncollapsed by default
by SGT. Garcia 20 Nov '13

20 Nov '13

it is very probable that i have missed this in the docs/manuals but i was wondering if there is a way to have threads (read/unread) uncollapsed by default? (and perhaps color the ones with unread). if not please consider this a feature request, if possbile. thanks. . ..:

3 4

unread is not mapped to 'new'
by SGT. Garcia 19 Nov '13

19 Nov '13

i'm still chasing funny behaviour :) so as i said before i have the first box as my *INBOX* and and the second one for 'recent' threads: [nm_query_type=threads] "drw [->]" "notmuch://?query=folder:drw AND tag:unread" \ " [..]" "notmuch://?query=folder:drw" \ now mark a msg in [..] 'N' but don't 'open' it. as soon as you change vfolder, it will be in [->]. now marking it 'N' anywhere, including in [..], that is after at least one change-vfolder, won't remove the 'unread' tag (it's still in [->] and if you have set nm_hidden_tags= then you see that it's still tagged 'unread') now mark something else 'N' in [..], then either 'open' it or mark it 'N' again, without changing vfolder and it won't pop up in [->]. so in this case 'N' did tag and untag 'unread'. so to summarise: hit NN on a msg, tagged unread then untagged unread hit N, then vfolder-change, then N on the same msg, first N tags it unread, second N doesn't do anything about unread tag.

2 2

unread is not mapped to 'new'
by SGT. Garcia 15 Nov '13

15 Nov '13

so i have this as my *INBOX*: "drw [ --> ]" "notmuch://?query=folder:drw AND tag:unread" \ simple enough, i guess. now when a 'new' msg arrives, it gets tagged by notmuch as unread, in fact without being explicitly indicated in .notmuch-config. now if i open this 'new' msg or use N to mark it as 'old' then it disappears from my *INBOX*. so flag 'new' is mapped properly in this direction. so far so good. or is it? if i don't _open_ the msg and don't mark it _old_ and simply modify-the-label with '-unread', it vanishes from *INBOX* but here is the catch, as soon as i vfolder-change it pops back into the 'unread' box. what is that? so mutt untags 'unread' then again tags it unread?

1 0

RPM repository for Fedora on copr
by Suvayu Ali 15 Nov '13

15 Nov '13

Hi, I have been building mutt-kz and notmuch packages for myself for a while. I discovered copr[1] today. This seemed like a great opportunity to share them reliably with others. You can find the repo files here: <http://copr-fe.cloud.fedoraproject.org/coprs/fatka/notmuch/> <http://copr-fe.cloud.fedoraproject.org/coprs/fatka/mutt-kz/> Initially I used the spec file from the Fedora package. Since then I have made some changes, including adding a few things from the spec file shared by Karel on this list. I also occasionally merge changes from the Fedora spec file. I try to update the packages when I see there are interesting changes in the Git repository. Hope people like it :). Cheers, Footnotes: [1] <https://fedorahosted.org/copr/wiki/UserDocs#FAQ> -- Suvayu Open source is the future. It sets us free.

2 2

unread is not mapped to 'new'
by SGT. Garcia 14 Nov '13

14 Nov '13

oops! explained that one backwards. let me try again: if a msg is tagged 'unread', then its tag will not be cleared by N if a msg is not tagged 'unread', it will be tagged 'unread' by N that's not consistent, me thinks. also opening/viewing a msg doesn't make it 'read', i.e. viewing takes the 'N' mark off the msg but doesn't take the 'unread' tag away.

1 0

unread is not mapped to 'new'
by SGT. Garcia 14 Nov '13

14 Nov '13

so i have this as my *INBOX*: "drw [ --> ]" "notmuch://?query=folder:drw AND tag:unread" \ simple enough, i guess. now when a 'new' msg arrives, it gets tagged by notmuch as unread, in fact without being explicitly indicated in .notmuch-config. now if i open this 'new' msg or use N to mark it as 'old' then it disappears from my *INBOX*. so flag 'new' is mapped properly in this direction. so far so good. here is the problem, if i dig the same msg (now flagged 'old') and mark it with N as 'new', one would expect it to turn up in the *INBOX* by being tagged as 'unread'. one would be wrong! i.e. flag 'new' is not mapped properly, as it should IMHO, in the reverse direction. question, is this intended?

1 0

recent changes
by Karel Zak 14 Nov '13

14 Nov '13

I have merged some pending patches (please, git pull): * add "nm_exclude_tags" to not load messages from specified tags from notmuch DB at all. * add "tag-transforms" to transform tags to (for example) unicode symbols * add "tag-formats" to define a tag specific $index_format %Gx formatting sequences (where 'x' is configurable). For example transform "honey" tag to unicode heart symbol and display the symbol by tag specific %Gh formatting sequence. tag-transforms "honey" "❤" tag-formats "honey "Gh" set index_format = "%4C %Z %?Gh?%Gh& ? %[%d/%b] %-16.15F %s" Note that %G may display hidden tags too. * add index_tag color object to colorize %G tags, for example: color index_tag red default '(honey)' to colorize the symbol define in the previous example * add "Tags:" line to the email view * merge old index color patch to coloring individual columns in the index, supported objects: index_subject index_author index_collapsed index_date index_flags index_label index_number index_size index_tags - %g output index_tag - %Gx output for more details and screenshot see https://github.com/karelzak/mutt-kz/pull/49 * merge nested if-else conditional patch (%? conditions in index_format) * date conditional patch, so you can use relative times, etc., for example I use: %<[1y?%<[1w?%<[1d?%[ %H:%M]&%[%a %d]>&%[%b %d]>&%[%y%m%d]> to display "YYMMDD" for messages older than one year, "Mon DD" for messages from one week to one year, "Day DD" for messages from 1 to 7 days old, and the "HH:MM" time for messages under one day old. Thanks to Eric Davis! TODO: * merge the current mutt upstream patches (v1.5.22) to mutt-kz * status line color patch: https://thomas.glanzmann.de//mutt/#cstatus * improve save-message command to update notmuch DB Volunteers? ;-) Karel -- Karel Zak <kzak(a)redhat.com> http://karelzak.blogspot.com

4 12

entire-thread command implemented
by Karel Zak 14 Nov '13

14 Nov '13

Hi folks, I have implemented and pushed to git tree a new <entire-thread> command (and yes, it's cool thing:-). From README file: entire-thread: - add to the current list of the messages all messages that belongs to the same thread as the current message. This command is useful when you have a new email in your INBOX and you want to see the rest of the archived thread. - default key: + Karel -- Karel Zak <kzak(a)redhat.com> http://karelzak.blogspot.com

4 6

Re: keeping tags in sync with maildirs?
by Brendan Taylor 05 Nov '13

05 Nov '13

(Sorry for breaking the thread, I just subscribed so this is a manual reply.) Selene Scriven wrote: > One issue I've noticed is that notmuch forgets everything it > knows about a message (such as tags I've assigned) after that > message is [s]aved from one maildir to another in mutt... which > is probably because mutt actually does a copy-then-delete instead > of simply moving it. Any idea how to avoid this? I just started using mutt-kz and am having a similar problem. I'm trying to use this macro to archive mail that I'm done with to a different maildir, with different notmuch labels: macro index S "<modify-labels>-inbox\n<previous-entry><save-message>=archives\n<previous-entry><modify-labels>" "notmuch new" doesn't detect the rename, it treats it as a new file.

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

mutt-kz November 2013