On Tue, Sep 02 2014, Daniel Kahn Gillmor wrote:
> On 08/30/2014 03:37 AM, Jani Nikula wrote:
>> I'm inclined to think this is a bug in message-mode.
>
> I agree it's a bug in message-mode, not in notmuch itself.
I think it might be here:
http://bzr.savannah.gnu.org/lh/emacs/emacs-24/annotate/h
Dear All,
I have my emacs/notmuch installation setup such, that I send the emails
usually directly using local exim4 installation. For particular 'From:'
field however I need to use my work server. Nowadays I do that
manually. Hence if I write an email using my work address, I manually
call a func
default-value needs its argument to be quoted.
---
Slightly strangely default-value of 't or nil is 't or nil
respectively so the code didn't give an error but just did the wrong
thing.
Thanks to Jani for finding the bug.
Best wishes
Mark
emacs/notmuch-jump.el |2 +-
1 file changed, 1 ins
On Tue, 2014-09-02 at 14:26 +0200, David Belohrad wrote:
> could that scenario be somehow fitted automatically, so when I overwrite
> the default 'From:' address (by hand. is it possible to do some
> automatic cycling?) to work address, so that message sender in emacs
> would automatically use work
Tomi Ollila writes:
> Some (older) Doxygen versions do not create such a temporary file.
>
> ---
pushed.
d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Mark Walters writes:
> default-value needs its argument to be quoted.
> ---
Hi Mark,
I really appreciate you sending in a bug fix. Thanks!
I'd prefer to see the commit message describing the bug and the fix a
bit.
You do have some text here that would be a great addition to the commit
message:
default-value needs its argument to be quoted.
Slightly strangely default-value of 't or nil is 't or nil
respectively so the code
(default-value notmuch-search-oldest-first)
just gives the current value of notmuch-search-oldest-first rather
than intended default-value of this variable.
The sym
LGTM.
Quoth Mark Walters on Sep 02 at 7:56 pm:
> default-value needs its argument to be quoted.
>
> Slightly strangely default-value of 't or nil is 't or nil
> respectively so the code
>
> (default-value notmuch-search-oldest-first)
>
> just gives the current value of notmuch-search-oldest-fi
On Tue, 02 Sep 2014, Mark Walters wrote:
> default-value needs its argument to be quoted.
>
> Slightly strangely default-value of 't or nil is 't or nil
> respectively so the code
>
> (default-value notmuch-search-oldest-first)
>
> just gives the current value of notmuch-search-oldest-first rather
On Mon, 01 Sep 2014, Perttu Luukko wrote:
> Yes, upgrading to GMime 2.6.20 caused all the messages on my server
> classified as mail.
What was the old version? If it was 2.4 we should probably consider
dropping support for that in future notmuch.
> Even more reason to give a separate warning for
On 2014-09-02 23:37:12, Jani Nikula wrote:
> On Mon, 01 Sep 2014, Perttu Luukko wrote:
> > Yes, upgrading to GMime 2.6.20 caused all the messages on my server
> > classified as mail.
>
> What was the old version? If it was 2.4 we should probably consider
> dropping support for that in future notm
On Tue, Sep 02 2014, Austin Clements wrote:
> 48db8c8 introduced a disagreement between when
> notmuch_database_needs_upgrade returned TRUE and when
> notmuch_database_upgrade actually performed an upgrade. As a result,
> if a database had a version less than 3, but no new features were
> requir
ze: 949 bytes
Desc: OpenPGP digital signature
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20140902/f0656afa/attachment.pgp>
On Tue, 02 Sep 2014, Tomi Ollila wrote:
> On Tue, Sep 02 2014, Austin Clements wrote:
>
>> 48db8c8 introduced a disagreement between when
>> notmuch_database_needs_upgrade returned TRUE and when
>> notmuch_database_upgrade actually performed an upgrade. As a result,
>> if a database had a versi
On Tue, Sep 02 2014, Daniel Kahn Gillmor wrote:
> On 08/30/2014 03:37 AM, Jani Nikula wrote:
>> I'm inclined to think this is a bug in message-mode.
>
> I agree it's a bug in message-mode, not in notmuch itself.
I think it might be here:
http://bzr.savannah.gnu.org/lh/emacs/emacs-24/annotate/h
Dear All,
I have my emacs/notmuch installation setup such, that I send the emails
usually directly using local exim4 installation. For particular 'From:'
field however I need to use my work server. Nowadays I do that
manually. Hence if I write an email using my work address, I manually
call a func
default-value needs its argument to be quoted.
---
Slightly strangely default-value of 't or nil is 't or nil
respectively so the code didn't give an error but just did the wrong
thing.
Thanks to Jani for finding the bug.
Best wishes
Mark
emacs/notmuch-jump.el |2 +-
1 file changed, 1 ins
On Tue, 2014-09-02 at 14:26 +0200, David Belohrad wrote:
> could that scenario be somehow fitted automatically, so when I overwrite
> the default 'From:' address (by hand. is it possible to do some
> automatic cycling?) to work address, so that message sender in emacs
> would automatically use work
Tomi Ollila writes:
> Some (older) Doxygen versions do not create such a temporary file.
>
> ---
pushed.
d
default-value needs its argument to be quoted.
Slightly strangely default-value of 't or nil is 't or nil
respectively so the code
(default-value notmuch-search-oldest-first)
just gives the current value of notmuch-search-oldest-first rather
than intended default-value of this variable.
The sym
LGTM.
Quoth Mark Walters on Sep 02 at 7:56 pm:
> default-value needs its argument to be quoted.
>
> Slightly strangely default-value of 't or nil is 't or nil
> respectively so the code
>
> (default-value notmuch-search-oldest-first)
>
> just gives the current value of notmuch-search-oldest-fi
On Tue, 02 Sep 2014, Mark Walters wrote:
> default-value needs its argument to be quoted.
>
> Slightly strangely default-value of 't or nil is 't or nil
> respectively so the code
>
> (default-value notmuch-search-oldest-first)
>
> just gives the current value of notmuch-search-oldest-first rather
On Mon, 01 Sep 2014, Perttu Luukko wrote:
> Yes, upgrading to GMime 2.6.20 caused all the messages on my server
> classified as mail.
What was the old version? If it was 2.4 we should probably consider
dropping support for that in future notmuch.
> Even more reason to give a separate warning for
23 matches
Mail list logo