#3271: mutt 1.5.20 regression: not updating time fields on mbox
---+
Reporter: anto...@dyne.org | Owner: pdmef
Type: defect| Status: closed
Priority: minor | Milestone: 1.6
On Tue, Jun 23, 2009 at 09:00:20PM +0200, Moritz Barsnick wrote:
> I agree that keeping mails marked as "new" does not allow
> differentiation between "now but seen" and "new and not yet
> seen". But it has worked for me so well for such a long time. Like
> you, I don't go to the length to mark/fla
On Tuesday, 23 June 2009 at 23:17, Rocco Rutte wrote:
> Hi,
>
> * Derek Martin wrote:
>
> > For what it's worth, the way I would most prefer to process my mail
> > would be like this:
>
> > 1. start mutt
> > 2. enter first mailbox (in order listed in .muttrc) which contains
> > new mail.
>
On Tue, Jun 23, 2009 at 11:17:01PM +0200, Rocco Rutte wrote:
> Hi,
>
> * Derek Martin wrote:
>
> > For what it's worth, the way I would most prefer to process my mail
> > would be like this:
>
> > 1. start mutt
> > 2. enter first mailbox (in order listed in .muttrc) which contains
> > new
* Rocco Rutte [06-23-09 17:16]:
> * Patrick Shanahan wrote:
>
> > One think I find lacking is a flag in the
> > directory listing similar to the "N", new mail flag, showing folders
> > containing "O", old mail. I want to know where *unread* mail is, not
> > *just* new mail.
>
> This is not as e
Hi,
* Derek Martin wrote:
> For what it's worth, the way I would most prefer to process my mail
> would be like this:
> 1. start mutt
> 2. enter first mailbox (in order listed in .muttrc) which contains
> new mail.
> 3. move to the next mailbox in listed order *in a ring* containing
>
Hi,
* Patrick Shanahan wrote:
> One think I find lacking is a flag in the
> directory listing similar to the "N", new mail flag, showing folders
> containing "O", old mail. I want to know where *unread* mail is, not
> *just* new mail.
This is not as easy at it sounds. At least (unfortunately) n
On 2009-06-23 14:27:44 -0500, Derek Martin wrote:
> Actually I do flag e-mails... though it's somewhat rare. I currently
> use a 3-tier approach to marking the importance of mails I leave
> around. In order:
>
> 1. leave the messages marked new: I want to be positive I address
> these soon
On Tue, Jun 23, 2009 at 09:00:20PM +0200, Moritz Barsnick wrote:
> The new work model is a large change for myself.
But note that if you were using maildir, it wouldn't be. ;-)
> If I have no choice, I will have to go along and do it that way. I
> agree that keeping mails marked as "new" does no
* Moritz Barsnick [06-23-09 15:02]:
>
> P.S.: To mark all currently "N"ew mails as "O"ld, do I just set
> mark_old=yes and enter and leave a folder?
afaik, but you can do the same by viewing the mbox file with nail/mail
and immediately leaving via the "q" option which saves changes.
Opening the
Hi Derek, list,
On Tue, Jun 23, 2009 at 11:33:59 -0500, Derek Martin wrote:
> For what it's worth, the way I would most prefer to process my mail
> would be like this:
Thanks for this. It pretty much conforms to my work model.
> nagging the user about new mail in folders they visited recently (y
On Tuesday, June 23 at 08:21 PM, quoth Rocco Rutte:
So the only real issue is when the FS isn't accurate about the times
for the directory.
Yeah... Of course filesystem problems are always an issue, but I guess
my thought is: for just about all filesystems, keeping track of a
"last modified"
* Derek Martin [06-23-09 12:36]:
> On Tue, Jun 23, 2009 at 05:22:20PM +0200, Rocco Rutte wrote:
> > The mentioned $next_unread_mailbox is within some 3rd party patch and
> > IIRC makes change folder suggest the next in the list with new mail, not
> > the first. I haven't used it though.
>
> For w
Hi,
* Kyle Wheeler wrote:
> What about using the mtime/ctime timestamp on the cur directory to
> determine whether it's changed since the last time it was read? All
> flag changes, message deliveries, etc. *should* update the
> directory's inode atime/ctime. That way you don't need a
> configurat
On Tue, Jun 23, 2009 at 05:22:20PM +0200, Rocco Rutte wrote:
> The mentioned $next_unread_mailbox is within some 3rd party patch and
> IIRC makes change folder suggest the next in the list with new mail, not
> the first. I haven't used it though.
For what it's worth, the way I would most prefer to
On Tuesday, June 23 at 05:15 PM, quoth Rocco Rutte:
Yes, I see your point. The only thing I'm sure is that your
guarantee shouldn't be generalized. :) What not sure about is
whether we really want an option for it. Hacking this isn't exactly
trivial either given that the current code of two pas
#3148: Need local implementations for fgetwc, ungetwc, fputws
--+-
Reporter: brendan | Owner: mutt-dev
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: charse
Hi,
* Kyle Wheeler wrote:
> Wow, that is *crazy* annoying! Not every message should be treated
> like an error!
Sorry for that.
Rocco
Hi,
* Moritz Barsnick wrote:
> I applied these two on top of 1.5.20. But I think changeset
> 5922:9ae13dedb5ed doesn't make sense to me.
By (mutt's) definition a mailbox has new mail if it has as least one
message that is neither read, nor deleted, nor marked as old. That's the
way it works for
Hi,
* Andrea Arcangeli wrote:
> On Sun, Jun 21, 2009 at 11:05:28PM +0200, Rocco Rutte wrote:
> > points that would have to be solved to get the patch ready for
> > inclusion. For example test if posix_fadvise() is available, why only
>
> That requires a configure knob?
No, simply test for its
Hi,
* Vincent Lefevre wrote:
> First, there's a small typo: mutt -> Mutt.
Good catch.
> Also, I'd say simply (if I understand correctly):
> In case of parsing errors, Mutt will print error messages.
Done, thanks.
Rocco
Hi,
* Vincent Lefevre wrote:
> No, the fact that it seems to work doesn't mean that it is allowed.
> Never use undocumented features!
Well, actually this is documented for years (4713:9f3afe005e3d).
Rocco
On Tuesday, June 23 at 12:30 AM, quoth Brendan Cully:
I've just pushed Vincent's simple fix.
Many thanks!
~Kyle
--
This is my simple religion. There is no need for temples; no need for
complicated philosophy. Our own brain, our own heart is our temple;
the philosophy is kindness.
#3279: hcache.c with db.h failes to compile on AIX
--+-
Reporter: mislik| Owner: mutt-dev
Type: defect| Status: new
Priority: major | Milestone:
Component: header
#2827: deleting attachment on imap and sync removes message from index
---+
Reporter: Christoph Berg | Owner: mutt-dev
Type: defect| Status: new
Priority: major
#2827: deleting attachment on imap and sync removes message from index
---+
Reporter: Christoph Berg | Owner: mutt-dev
Type: defect| Status: new
Priority: major
On Tuesday, 23 June 2009 at 02:12, Kyle Wheeler wrote:
> On Tuesday, June 23 at 12:00 AM, quoth Brendan Cully:
> >http://dev.mutt.org/hg/mutt/rev/54bc1ef602e7
> >changeset: 5934:54bc1ef602e7
> >branch: HEAD
> >tag: tip
> >user:Rocco Rutte
> >date:Mon Jun 22 17:36:21
On Tuesday, June 23 at 12:00 AM, quoth Brendan Cully:
http://dev.mutt.org/hg/mutt/rev/54bc1ef602e7
changeset: 5934:54bc1ef602e7
branch: HEAD
tag: tip
user:Rocco Rutte
date:Mon Jun 22 17:36:21 2009 +0200
summary: Make mutt_curses_(error|message) format message t
4 new changesets in mutt:
http://dev.mutt.org/hg/mutt/rev/54bc1ef602e7
changeset: 5934:54bc1ef602e7
branch: HEAD
tag: tip
user:Rocco Rutte
date:Mon Jun 22 17:36:21 2009 +0200
summary: Make mutt_curses_(error|message) format message to COLS chars.
Closes #3278.
29 matches
Mail list logo
