On Wed, Dec 26 2012, David Bremner wrote:
> Mark Walters writes:
>
>>> I can imagine that people would want/like the "open in other window"
>>> effect of the current code, even if the reason is a bug.
>>
>> That's definitely possible. I generally expect a mouse click to select
>> the window I
On Thu, Jan 03 2013, Austin Clements wrote:
> We recently switched to popping up a buffer to report CLI errors, but
> this was too intrusive, especially for transient errors and especially
> since we made fewer things ignore errors. This patch changes this to
> display a basic error message in
While one comment in generated .notmuch-config file looked good in the
source file notmuch-config.c, the generated output was inconsistently
wide -- even breaking the 80-column boundary.
---
notmuch-config.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/notmuch-config.c
LGTM.
On Sat, 05 Jan 2013, Tomi Ollila wrote:
> While one comment in generated .notmuch-config file looked good in the
> source file notmuch-config.c, the generated output was inconsistently
> wide -- even breaking the 80-column boundary.
> ---
> notmuch-config.c | 5 +++--
> 1 file changed, 3
On Sat, Jan 05 2013, Albin Stjerna wrote:
> Hi!
>
> When forwarding an email containing (what I think is) unicode characters
> (primarily umlauts), these are incorrectly re-entered as strange escaped
> characters (? becomes \344, ? becomes \345 and so on). Then, when I try
> to send the email, I
Tomi Ollila wrote:
> On Sat, Jan 05 2013, Albin Stjerna wrote:
> What version of notmuch are you using? There has been some fixes
> in this front done since 0.14 (i.e. currently only available from git)
I'm using 0.14. Might try to upgrade to the latest version from git then and
see if it
Hi!
When forwarding an email containing (what I think is) unicode characters
(primarily umlauts), these are incorrectly re-entered as strange escaped
characters (? becomes \344, ? becomes \345 and so on). Then, when I try to send
the email, I get an error about the message containing
Hi!
When forwarding an email containing (what I think is) unicode characters
(primarily umlauts), these are incorrectly re-entered as strange escaped
characters (ä becomes \344, å becomes \345 and so on). Then, when I try to send
the email, I get an error about the message containing
On Sat, Jan 05 2013, Albin Stjerna albin.stje...@gmail.com wrote:
Hi!
When forwarding an email containing (what I think is) unicode characters
(primarily umlauts), these are incorrectly re-entered as strange escaped
characters (ä becomes \344, å becomes \345 and so on). Then, when I try
to
Tomi Ollila wrote:
On Sat, Jan 05 2013, Albin Stjerna albin.stje...@gmail.com wrote:
What version of notmuch are you using? There has been some fixes
in this front done since 0.14 (i.e. currently only available from git)
I'm using 0.14. Might try to upgrade to the latest version from git
While one comment in generated .notmuch-config file looked good in the
source file notmuch-config.c, the generated output was inconsistently
wide -- even breaking the 80-column boundary.
---
notmuch-config.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/notmuch-config.c
LGTM.
On Sat, 05 Jan 2013, Tomi Ollila tomi.oll...@iki.fi wrote:
While one comment in generated .notmuch-config file looked good in the
source file notmuch-config.c, the generated output was inconsistently
wide -- even breaking the 80-column boundary.
---
notmuch-config.c | 5 +++--
1 file
On Thu, Jan 03 2013, Austin Clements amdra...@mit.edu wrote:
We recently switched to popping up a buffer to report CLI errors, but
this was too intrusive, especially for transient errors and especially
since we made fewer things ignore errors. This patch changes this to
display a basic error
On Wed, Dec 26 2012, David Bremner da...@tethera.net wrote:
Mark Walters markwalters1...@gmail.com writes:
I can imagine that people would want/like the open in other window
effect of the current code, even if the reason is a bug.
That's definitely possible. I generally expect a mouse
On Wed, Dec 26 2012, da...@tethera.net wrote:
From: David Bremner brem...@debian.org
This patch corrects several undesirable behaviours:
1) Empty files were not detected, leading to buffer read overrun.
2) An initial blank line cause restore to silently abort
3) Initial comment line
15 matches
Mail list logo
