Mark Walters writes:
> Some messages are sent as multipart/alternative but the alternatives
> contain different information. This allows the user to cycle which
> part to view. By default this is bound to 'W'.
> ---
>
> This version at least uses the notmuch escaping for message-id which
> makes
Mark Walters markwalters1...@gmail.com writes:
Some messages are sent as multipart/alternative but the alternatives
contain different information. This allows the user to cycle which
part to view. By default this is bound to 'W'.
---
This version at least uses the notmuch escaping for
On Fri, Aug 10, 2012 at 1:10 AM, Mark Walters
wrote:
>
> Some messages are sent as multipart/alternative but the alternatives
> contain different information. This allows the user to cycle which
> part to view. By default this is bound to 'W'.
I've started using this, and quite like it. Only
On Fri, Aug 10, 2012 at 1:10 AM, Mark Walters markwalters1...@gmail.com wrote:
Some messages are sent as multipart/alternative but the alternatives
contain different information. This allows the user to cycle which
part to view. By default this is bound to 'W'.
I've started using this, and
On Aug 10, 2012 7:18 PM, "Jameson Graef Rollins"
wrote:
>
> On Fri, Aug 10 2012, Jani Nikula wrote:
> > How would this work together with something like [1] (rationale in [2])?
> >
> > [1] id:"
ab777cf0fa83778d3399ac52094df9230738819d.1328798471.git.jani at nikula.org"
> > [2]
On Fri, 10 Aug 2012, Jani Nikula wrote:
> On Aug 10, 2012 7:18 PM, "Jameson Graef Rollins" finestructure.net>
> wrote:
>>
>> On Fri, Aug 10 2012, Jani Nikula wrote:
>> > How would this work together with something like [1] (rationale in [2])?
>> >
>> > [1] id:"
>
On Fri, 10 Aug 2012, Mark Walters wrote:
> Some messages are sent as multipart/alternative but the alternatives
> contain different information. This allows the user to cycle which
> part to view. By default this is bound to 'W'.
> ---
>
> On Thu, 09 Aug 2012, Jameson Graef Rollins
> wrote:
>>
On Fri, Aug 10 2012, Jani Nikula wrote:
> How would this work together with something like [1] (rationale in [2])?
>
> [1] id:"ab777cf0fa83778d3399ac52094df9230738819d.1328798471.git.jani at
> nikula.org"
> [2] id:"cover.1328719309.git.jani at nikula.org"
>
> If you introduce a mechanism to
Some messages are sent as multipart/alternative but the alternatives
contain different information. This allows the user to cycle which
part to view. By default this is bound to 'W'.
---
On Thu, 09 Aug 2012, Jameson Graef Rollins
wrote:
> On Mon, Jun 18 2012, Mark Walters wrote:
>> I agree
Some messages are sent as multipart/alternative but the alternatives
contain different information. This allows the user to cycle which
part to view. By default this is bound to 'W'.
---
On Thu, 09 Aug 2012, Jameson Graef Rollins jroll...@finestructure.net wrote:
On Mon, Jun 18 2012, Mark
On Fri, 10 Aug 2012, Mark Walters markwalters1...@gmail.com wrote:
Some messages are sent as multipart/alternative but the alternatives
contain different information. This allows the user to cycle which
part to view. By default this is bound to 'W'.
---
On Thu, 09 Aug 2012, Jameson Graef
On Fri, Aug 10 2012, Jani Nikula j...@nikula.org wrote:
How would this work together with something like [1] (rationale in [2])?
[1]
id:ab777cf0fa83778d3399ac52094df9230738819d.1328798471.git.j...@nikula.org
[2] id:cover.1328719309.git.j...@nikula.org
If you introduce a mechanism to store
On Aug 10, 2012 7:18 PM, Jameson Graef Rollins jroll...@finestructure.net
wrote:
On Fri, Aug 10 2012, Jani Nikula j...@nikula.org wrote:
How would this work together with something like [1] (rationale in [2])?
[1] id:
ab777cf0fa83778d3399ac52094df9230738819d.1328798471.git.j...@nikula.org
On Fri, 10 Aug 2012, Jani Nikula j...@nikula.org wrote:
On Aug 10, 2012 7:18 PM, Jameson Graef Rollins jroll...@finestructure.net
wrote:
On Fri, Aug 10 2012, Jani Nikula j...@nikula.org wrote:
How would this work together with something like [1] (rationale in [2])?
[1] id:
On Fri, Aug 10 2012, Mark Walters markwalters1...@gmail.com wrote:
I am not sure I agree: I think maybe toggling parts is better. Either
the parts contain the same information and then the current behaviour is
probably fine, or they are not in which case we might want to see both
at once
If
On Tue, 19 Jun 2012, Jani Nikula wrote:
> Add function notmuch-show-toggle-multipart-alternative to toggle the
> value of notmuch-show-all-multipart/alternative-parts variable in the
> buffer, and redisplay the thread with either all or preferred
> alternative parts expanded.
>
> A small wrinkle
On Jun 23, 2012 1:34 AM, David Bremner da...@tethera.net wrote:
Jani Nikula j...@nikula.org writes:
A small wrinkle is that in order to make the variable survive
notmuch-show-refresh-view (which is required for expanding/collapsing
the parts, but ends up calling kill-all-local-variables
On Tue, 19 Jun 2012, Jani Nikula j...@nikula.org wrote:
Add function notmuch-show-toggle-multipart-alternative to toggle the
value of notmuch-show-all-multipart/alternative-parts variable in the
buffer, and redisplay the thread with either all or preferred
alternative parts expanded.
A
Jani Nikula writes:
>
> A small wrinkle is that in order to make the variable survive
> notmuch-show-refresh-view (which is required for expanding/collapsing
> the parts, but ends up calling kill-all-local-variables through
> notmuch-show-mode) it is necessary to give it the permanent-local
>
Jani Nikula j...@nikula.org writes:
A small wrinkle is that in order to make the variable survive
notmuch-show-refresh-view (which is required for expanding/collapsing
the parts, but ends up calling kill-all-local-variables through
notmuch-show-mode) it is necessary to give it the
On Tue, 19 Jun 2012, Jani Nikula wrote:
> Add function notmuch-show-toggle-multipart-alternative to toggle the
> value of notmuch-show-all-multipart/alternative-parts variable in the
> buffer, and redisplay the thread with either all or preferred
> alternative parts expanded.
I see that Mark has
Add function notmuch-show-toggle-multipart-alternative to toggle the
value of notmuch-show-all-multipart/alternative-parts variable in the
buffer, and redisplay the thread with either all or preferred
alternative parts expanded.
A small wrinkle is that in order to make the variable survive
On Tue, 19 Jun 2012, Jani Nikula j...@nikula.org wrote:
Add function notmuch-show-toggle-multipart-alternative to toggle the
value of notmuch-show-all-multipart/alternative-parts variable in the
buffer, and redisplay the thread with either all or preferred
alternative parts expanded.
I see
23 matches
Mail list logo
