On 2010-04-14, Michal Sojka wrote:
> On Tue, 13 Apr 2010, Servilio Afre Puentes wrote:
> > The current hardcoded behaviour will not take you to the next unread
> > thread when the sort order is set to newer-first from the default of
> > older-first.
>
> Is this really what we want? If I sort
On 14 April 2010 05:53, Sebastian Spaeth wrote:
> On 2010-04-14, Michal Sojka wrote:
>> On Tue, 13 Apr 2010, Servilio Afre Puentes wrote:
>> > The current hardcoded behaviour will not take you to the next unread
>> > thread when the sort order is set to newer-first from the default of
>> >
On Tue, 13 Apr 2010, Servilio Afre Puentes wrote:
The current hardcoded behaviour will not take you to the next unread
thread when the sort order is set to newer-first from the default of
older-first.
Is this really what we want? If I sort messages by newest first, it
menas that I want to
On 14 April 2010 05:53, Sebastian Spaeth sebast...@sspaeth.de wrote:
On 2010-04-14, Michal Sojka wrote:
On Tue, 13 Apr 2010, Servilio Afre Puentes wrote:
The current hardcoded behaviour will not take you to the next unread
thread when the sort order is set to newer-first from the default of
The current hardcoded behaviour will not take you to the next unread
thread when the sort order is set to newer-first from the default of
older-first.
Signed-off-by: Servilio Afre Puentes
---
emacs/notmuch.el |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git
The current hardcoded behaviour will not take you to the next unread
thread when the sort order is set to newer-first from the default of
older-first.
Signed-off-by: Servilio Afre Puentes servi...@gmail.com
---
emacs/notmuch.el |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff
