mutt-kz

mutt-kz@lists.fedoraproject.org

138 discussions

policy for upstream-sync
by Walter Rabus 03 Mar '15

03 Mar '15

Hi, I'd like to try mutt and mutt-kz sounds very good to me so far. I'd like to ask what the policy for mutt-kz is regarding upstream-development. Will upstream-development be merged into mutt-kz or is this definitely a separate project now? I saw the recent thread about upstream-patches merged into mutt-kz, but denoted as "(cherry-picked)", therefore I'm not sure about the policy in place here. This is especially interesting for me with regard to config-compatibility, as I am still in the testing-phase of mutt and different versions of it and I'm not sure how changing to a different mutt-[insert_patchset_here] might affect the reusability of the configuration. Therefore my second question: is mutt-kz fully config-compatible to mutt except for additional configurations that result from added patches? I would be very glad if someone could bring a little light into this. Thanks a lot, Walter

2 1

sync with upstream
by Karel Zak 12 Feb '15

12 Feb '15

I have merged (cherry-picked) ~40 patches from mutt upstream hg repository. Please, try update and test. Thanks. Karel -- Karel Zak <kzak(a)redhat.com> http://karelzak.blogspot.com

4 6

disabling two-column pager
by Danny O'Brien 30 Jan '15

30 Jan '15

I'm a huge fan of mutt-kz, and couldn't live without it. However I think it includes by default an email pager which takes advantage of terminasl with > 80 characters in width, to display two columns (in my case, separated by a red pipe | character). I'd like to disable this if possible, either at compile or run time. Does anybody know where I should look to do this? d.

2 1

Copr for Fedora 21
by Jeff Peeler 04 Jan '15

04 Jan '15

Is there a Copr repository for Fedora 21? I haven't been able to find it and the notmuch shipped with Fedora 21 isn't the same version as Fedora 20 (libnotmuch.so.3 vs libnotmuch.so.4). Just thought I would check before I go back to compiling again. Having the copr was pretty nice. Jeff

2 2

[ANNOUNCE] v1.5.23.1-rc1
by Karel Zak 02 Nov '14

02 Nov '14

The mutt-kzx release v1.5.23.1-rc is available at ftp://redcrew.org/pub/mutt-kz/v1.5.23.1/ For more information and binary packages see https://kzak.redcrew.org/doku.php?id=mutt:start Thanks to all contributors! Feedback and bug reports, as always, are welcomed. Karel -- Karel Zak <kzak(a)redhat.com> http://karelzak.blogspot.com

3 3

Security fix release
by J. Lewis Muir 05 Sep '14

05 Sep '14

Hello, mutt-kz Community. Thank you to those of you who are working on mutt-kz! I'm new to mutt-kz, but it looks quite interesting! There was a security bug fix in Mutt [1] that prompted the Mutt 1.5.23 security bugfix release on March 12, 2014. I see that this fix was imported into mutt-kz on March 13, 2014 [2]. The first official mutt-kz release, 1.5.22.1, was made on February 5, 2014 [3], and I inspected the copy.c source code, and it contains the security bug. However, there has not been a mutt-kz security bugfix release made for this security bug fix. I'm wondering, why is that? Thank you! Lewis [1] http://dev.mutt.org/hg/mutt/rev/9bf7593e3c08 [2] https://github.com/karelzak/mutt-kz/commit/044e86c3e395de87d92382fd72df8d34… [3] https://lists.fedoraproject.org/pipermail/mutt-kz/2014-February/000286.html

3 2

Highlight new mails in virtual folders
by Cédric Macquat 06 Aug '14

06 Aug '14

Hello, I have only virtual folders on the sidebar. When I receive new mails, the virtual folders containing new mails are not highlighted. Is it possible to change that ? If I use only regular folder, by starting mutt all regular folders containing new mails are highlighted. If I understand right, the virtual folders are the result of a notmuch query. My guess is: when I start mutt, I see the result of the last query. Only if change to a virtual folder the query is actualized. And it's what happens: when I change to a virtual folder containing new mail, just after changing the virtual folder is highlighted. How can I have the virtual folder highlight when I start mutt ? Thank you! Regards, Cédric

1 0

[slighly offtopic] use notmuch as the sole msg store?
by Douglas Campos 30 May '14

30 May '14

Howdy! Happy mutt-kz user here. I'm wondering whether any of you thought on going further and using notmuch/xapian as the sole store for mail. Why am I asking this? Mutt does a bazillion file operations which is insanely slow under OSX; I'm wondering whether could we plug libetpan and feed mail directly to the database, sync the changes back. This would mean we would have all the mutt-kz awesomeness without having to muck with mbsync/offlineimap and having to use double storage space (Maildir + notmuch db). I'm not asking for anyone to do it, more interested in hearing if this is crazy talk and I'm insane of wanting this :) Thoughts? -- qmx

3 2

Please don't review virtual folder path might be longer than _POSIX_PATH_MAX
by Ondrej Balaz 29 May '14

29 May '14

Hi, please don't review the patch yet. I realized it's required to patch many more routines that use constant length of buffers in order to make it work properly. I'll send updated version soon. Regards, -- Ondrej Balaz e-mail: blami(a)blami.net

1 0

[PATCH] Virtual folder path might be longer than _POSIX_PATH_MAX.
by Ondrej Balaz 29 May '14

29 May '14

Since the path member of BUFFY struct is used to store notmuch queries it should be able to hold more than _POSIX_PATH_MAX characters. This patch changes it to dynamically allocated buffer and in case of virtual folder copies whole path token, not only first _POSIX_PATH_MAX characters. Signed-off-by: Ondrej Balaz <blami(a)blami.net> --- buffy.c | 24 ++++++++++++++---------- buffy.h | 2 +- 2 files changed, 15 insertions(+), 11 deletions(-) diff --git a/buffy.c b/buffy.c index 91bc480..7ef984f 100644 --- a/buffy.c +++ b/buffy.c @@ -203,7 +203,7 @@ static BUFFY *buffy_new (const char *path) BUFFY* buffy; buffy = (BUFFY *) safe_calloc (1, sizeof (BUFFY)); - strfcpy (buffy->path, path, sizeof (buffy->path)); + buffy->path = safe_strdup(path); buffy->next = NULL; buffy->magic = 0; @@ -212,8 +212,10 @@ static BUFFY *buffy_new (const char *path) static void buffy_free (BUFFY **mailbox) { - if (mailbox && *mailbox) + if (mailbox && *mailbox) { + FREE (&(*mailbox)->path); FREE (&(*mailbox)->desc); + } FREE (mailbox); /* __FREE_CHECKED__ */ } @@ -296,7 +298,7 @@ int mutt_parse_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, BUFFER *e int mutt_parse_virtual_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, BUFFER *err) { BUFFY **tmp; - char buf[_POSIX_PATH_MAX]; + char *buf; /* notmuch query might be longer than _POSIX_PATH_MAX */ while (MoreArgs (s)) { @@ -309,12 +311,12 @@ int mutt_parse_virtual_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, B continue; mutt_extract_token (path, s, 0); - strfcpy (buf, path->data, sizeof (buf)); - - /* Skip empty tokens. */ - if(!*buf) { - FREE(&desc); - continue; + if (path->data && *path->data) { + buf = safe_strdup(path->data); + } else { + /* skip empty tokens */ + FREE(&desc); + continue; } /* avoid duplicates */ @@ -322,7 +324,7 @@ int mutt_parse_virtual_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, B { if (mutt_strcmp (buf, (*tmp)->path) == 0) { - dprint(3,(debugfile,"vistual mailbox '%s' already registered as '%s'\n", buf, (*tmp)->path)); + dprint(3,(debugfile,"virtual mailbox '%s' already registered as '%s'\n", buf, (*tmp)->path)); break; } } @@ -335,6 +337,8 @@ int mutt_parse_virtual_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, B (*tmp)->newly_created = 0; (*tmp)->size = 0; (*tmp)->desc = desc; + + FREE(&buf); } return 0; } diff --git a/buffy.h b/buffy.h index 5cbc06f..10508a5 100644 --- a/buffy.h +++ b/buffy.h @@ -22,7 +22,7 @@ typedef struct buffy_t { - char path[_POSIX_PATH_MAX]; + char *path; char *desc; off_t size; struct buffy_t *next; -- 2.0.0.rc2

1 0

← Newer
1
2
3
4
5
6
7
...
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

mutt-kz