On Tue, Aug 07 2012, Mark Walters wrote:
> On Tue, 07 Aug 2012, Michal Nazarewicz wrote:
[ ... ]
>> Mark Walters writes:
>>> As an alternative approach would allowing a list of tags (or even tag
>>> changes) to apply when a message is "read" do what you want and be more
>>> flexible?
>>
>>
On Tue, Aug 07 2012, Mark Walters wrote:
> On Mon, 06 Aug 2012, Michal Nazarewicz wrote:
>> From: Michal Nazarewicz
>>
>> Setting `notmuch-show-auto-mark-read' to nil stops notmuch-show from marking
>> the message as read (by removing the unread tag). Inteded for people who
>> like to mark
>> From: Michal Nazarewicz
>> @@ -1383,8 +1390,9 @@ current thread."
>>(notmuch-show-get-prop :headers-visible))
>>
>> (defun notmuch-show-mark-read ()
>> - "Mark the current message as read."
>> - (notmuch-show-tag-message "-unread"))
>> + "Apply `notmuch-show-mark-read-tags' to the
> On Mon, 06 Aug 2012, Michal Nazarewicz wrote:
>> @@ -1374,9 +1382,11 @@ current thread."
>>"Are the headers of the current message visible?"
>>(notmuch-show-get-prop :headers-visible))
>>
>> -(defun notmuch-show-mark-read ()
>> - "Mark the current message as read."
>> -
On Tue, 07 Aug 2012, Michal Nazarewicz wrote:
>> On Mon, 06 Aug 2012, Michal Nazarewicz wrote:
>>> @@ -1374,9 +1382,11 @@ current thread."
>>>"Are the headers of the current message visible?"
>>>(notmuch-show-get-prop :headers-visible))
>>>
>>> -(defun notmuch-show-mark-read ()
>>> -
On Mon, 06 Aug 2012, Michal Nazarewicz wrote:
> From: Michal Nazarewicz
>
> Setting `notmuch-show-auto-mark-read' to nil stops notmuch-show from marking
> the message as read (by removing the unread tag). Inteded for people who
> like to mark messages read explicitly.
> ---
>
On Mon, 06 Aug 2012, Michal Nazarewicz m...@google.com wrote:
From: Michal Nazarewicz min...@mina86.com
Setting `notmuch-show-auto-mark-read' to nil stops notmuch-show from marking
the message as read (by removing the unread tag). Inteded for people who
like to mark messages read explicitly.
On Mon, 06 Aug 2012, Michal Nazarewicz m...@google.com wrote:
@@ -1374,9 +1382,11 @@ current thread.
Are the headers of the current message visible?
(notmuch-show-get-prop :headers-visible))
-(defun notmuch-show-mark-read ()
- Mark the current message as read.
-
On Tue, 07 Aug 2012, Michal Nazarewicz m...@google.com wrote:
On Mon, 06 Aug 2012, Michal Nazarewicz m...@google.com wrote:
@@ -1374,9 +1382,11 @@ current thread.
Are the headers of the current message visible?
(notmuch-show-get-prop :headers-visible))
-(defun notmuch-show-mark-read
On Tue, Aug 07 2012, Mark Walters markwalters1...@gmail.com wrote:
On Mon, 06 Aug 2012, Michal Nazarewicz m...@google.com wrote:
From: Michal Nazarewicz min...@mina86.com
Setting `notmuch-show-auto-mark-read' to nil stops notmuch-show from marking
the message as read (by removing the unread
From: Michal Nazarewicz min...@mina86.com
@@ -1383,8 +1390,9 @@ current thread.
(notmuch-show-get-prop :headers-visible))
(defun notmuch-show-mark-read ()
- Mark the current message as read.
- (notmuch-show-tag-message -unread))
+ Apply `notmuch-show-mark-read-tags' to the
On Tue, Aug 07 2012, Mark Walters markwalters1...@gmail.com wrote:
On Tue, 07 Aug 2012, Michal Nazarewicz m...@google.com wrote:
[ ... ]
Mark Walters markwalters1...@gmail.com writes:
As an alternative approach would allowing a list of tags (or even tag
changes) to apply when a message is
Austin Clements writes:
> LGTM, though I wonder: Is this actually what you want, or would you be
> happy with automatic read marking if it followed a different pattern
> (perhaps a more predictable pattern)?
At the moment, I feel that's what I want. I have a few keys set up for
addings tags
LGTM, though I wonder: Is this actually what you want, or would you be
happy with automatic read marking if it followed a different pattern
(perhaps a more predictable pattern)?
Quoth Michal Nazarewicz on Aug 06 at 4:20 pm:
> From: Michal Nazarewicz
>
> Setting `notmuch-show-auto-mark-read' to
Austin Clements amdra...@mit.edu writes:
LGTM, though I wonder: Is this actually what you want, or would you be
happy with automatic read marking if it followed a different pattern
(perhaps a more predictable pattern)?
At the moment, I feel that's what I want. I have a few keys set up for
15 matches
Mail list logo
