Mark Walters writes:
> Thus we add a debug variable notmuch-show-attachment-debug: it this is
> non-nil we create a new buffer for each viewer; if this variable is
> nil we just use a temp buffer which means all error output is
> discarded (this is the same behaviour as with emacs pre 24.3).
Mark Walters markwalters1...@gmail.com writes:
Thus we add a debug variable notmuch-show-attachment-debug: it this is
non-nil we create a new buffer for each viewer; if this variable is
nil we just use a temp buffer which means all error output is
discarded (this is the same behaviour as with
On Wed, Nov 13 2013, Mark Walters wrote:
> In emacs 24.3+ the stdout/stderr from externally displaying an
> attachment gets inserted into the show buffer. This is caused by
> changes in mm-display-external in mm-decode.el.
>
> Ideally, we would put this output in the notmuch errors buffer but
In emacs 24.3+ the stdout/stderr from externally displaying an
attachment gets inserted into the show buffer. This is caused by
changes in mm-display-external in mm-decode.el.
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know
On Wed, Nov 13 2013, Mark Walters markwalters1...@gmail.com wrote:
In emacs 24.3+ the stdout/stderr from externally displaying an
attachment gets inserted into the show buffer. This is caused by
changes in mm-display-external in mm-decode.el.
Ideally, we would put this output in the notmuch
On Thu, Sep 12 2013, Mark Walters wrote:
> On Thu, 12 Sep 2013, Tomi Ollila wrote:
>> On Thu, Sep 12 2013, Mark Walters wrote:
>>
>>> On Thu, 12 Sep 2013, Tomi Ollila wrote:
>
> Yes this is easy. There are several possibilities and I am not sure
> which is best (some are clearly
On Thu, Sep 12 2013, Mark Walters markwalters1...@gmail.com wrote:
On Thu, 12 Sep 2013, Tomi Ollila tomi.oll...@iki.fi wrote:
On Thu, Sep 12 2013, Mark Walters markwalters1...@gmail.com wrote:
On Thu, 12 Sep 2013, Tomi Ollila tomi.oll...@iki.fi wrote:
Yes this is easy. There are several
On Thu, 12 Sep 2013, Tomi Ollila wrote:
> On Thu, Sep 12 2013, Mark Walters wrote:
>
>> On Thu, 12 Sep 2013, Tomi Ollila wrote:
>>> On Thu, Sep 12 2013, Mark Walters wrote:
>>>
Hi
On Tue, 10 Sep 2013, David Bremner wrote:
>> Ideally, we would put this output in the notmuch
On Thu, 12 Sep 2013, Austin Clements wrote:
> Quoth Mark Walters on Sep 12 at 10:33 am:
>>
>> Hi
>>
>> On Tue, 10 Sep 2013, David Bremner wrote:
>> >> Ideally, we would put this output in the notmuch errors buffer but the
>> >> handler is called asynchronously so we don't know when the output
On Thu, Sep 12 2013, Mark Walters wrote:
> On Thu, 12 Sep 2013, Tomi Ollila wrote:
>> On Thu, Sep 12 2013, Mark Walters wrote:
>>
>>> Hi
>>>
>>> On Tue, 10 Sep 2013, David Bremner wrote:
> Ideally, we would put this output in the notmuch errors buffer but the
> handler is called
On Thu, Sep 12 2013, Mark Walters wrote:
> Hi
>
> On Tue, 10 Sep 2013, David Bremner wrote:
>>> Ideally, we would put this output in the notmuch errors buffer but the
>>> handler is called asynchronously so we don't know when the output will
>>> appear. Thus if we put it straight into the
On Thu, 12 Sep 2013, Tomi Ollila wrote:
> On Thu, Sep 12 2013, Mark Walters wrote:
>
>> Hi
>>
>> On Tue, 10 Sep 2013, David Bremner wrote:
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know when the output will
Quoth Mark Walters on Sep 12 at 10:33 am:
>
> Hi
>
> On Tue, 10 Sep 2013, David Bremner wrote:
> >> Ideally, we would put this output in the notmuch errors buffer but the
> >> handler is called asynchronously so we don't know when the output will
> >> appear. Thus if we put it straight into the
Hi
On Tue, 10 Sep 2013, David Bremner wrote:
>> Ideally, we would put this output in the notmuch errors buffer but the
>> handler is called asynchronously so we don't know when the output will
>> appear. Thus if we put it straight into the errors buffer it could get
>> interleaved with other
Mark Walters writes:
> 3) have a buffer for each part viewer but start its name with a space so
> it doesn't show up in buffer lists but is findable (maybe)
This, toggleable with a debug flag sounds good to me; if the debug flag
is nil, use a temp buffer. Or equivalently delete the named
Hi
On Tue, 10 Sep 2013, David Bremner da...@tethera.net wrote:
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know when the output will
appear. Thus if we put it straight into the errors buffer it could get
interleaved with
Mark Walters markwalters1...@gmail.com writes:
3) have a buffer for each part viewer but start its name with a space so
it doesn't show up in buffer lists but is findable (maybe)
This, toggleable with a debug flag sounds good to me; if the debug flag
is nil, use a temp buffer. Or equivalently
On Thu, Sep 12 2013, Mark Walters markwalters1...@gmail.com wrote:
Hi
On Tue, 10 Sep 2013, David Bremner da...@tethera.net wrote:
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know when the output will
appear. Thus if we
On Thu, 12 Sep 2013, Tomi Ollila tomi.oll...@iki.fi wrote:
On Thu, Sep 12 2013, Mark Walters markwalters1...@gmail.com wrote:
Hi
On Tue, 10 Sep 2013, David Bremner da...@tethera.net wrote:
Ideally, we would put this output in the notmuch errors buffer but the
handler is called
On Thu, Sep 12 2013, Mark Walters markwalters1...@gmail.com wrote:
On Thu, 12 Sep 2013, Tomi Ollila tomi.oll...@iki.fi wrote:
On Thu, Sep 12 2013, Mark Walters markwalters1...@gmail.com wrote:
Hi
On Tue, 10 Sep 2013, David Bremner da...@tethera.net wrote:
Ideally, we would put this output
Quoth Mark Walters on Sep 12 at 10:33 am:
Hi
On Tue, 10 Sep 2013, David Bremner da...@tethera.net wrote:
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know when the output will
appear. Thus if we put it straight into
On Thu, 12 Sep 2013, Tomi Ollila tomi.oll...@iki.fi wrote:
On Thu, Sep 12 2013, Mark Walters markwalters1...@gmail.com wrote:
On Thu, 12 Sep 2013, Tomi Ollila tomi.oll...@iki.fi wrote:
On Thu, Sep 12 2013, Mark Walters markwalters1...@gmail.com wrote:
Hi
On Tue, 10 Sep 2013, David Bremner
On Thu, 12 Sep 2013, Austin Clements amdra...@mit.edu wrote:
Quoth Mark Walters on Sep 12 at 10:33 am:
Hi
On Tue, 10 Sep 2013, David Bremner da...@tethera.net wrote:
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know
> Ideally, we would put this output in the notmuch errors buffer but the
> handler is called asynchronously so we don't know when the output will
> appear. Thus if we put it straight into the errors buffer it could get
> interleaved with other errors, otoh we can't easily tell when we
> have got
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know when the output will
appear. Thus if we put it straight into the errors buffer it could get
interleaved with other errors, otoh we can't easily tell when we
have got all
In emacs 24.3+ the stdout/stderr from externally displaying an
attachment gets inserted into the show buffer. This is caused by
changes in mm-display-external in mm-decode.el.
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know
In emacs 24.3+ the stdout/stderr from externally displaying an
attachment gets inserted into the show buffer. This is caused by
changes in mm-display-external in mm-decode.el.
Ideally, we would put this output in the notmuch errors buffer but the
handler is called asynchronously so we don't know
27 matches
Mail list logo
