Hi Anton,
thanks for answering. Finally I found it. My next problem is that I have
absolutely no idea how to use it.
I followed the instructions I have found in this mailing list and copied the
syntax files into my ~/.vim/syntax
and the two plugin files?into my ~/.vim/plugin folders.
Then I cal
It seems some messages trigger a segmentation fault in
`do_search_threads()`. It appears the problem occurs (at least) when
`authors` is NULL.
Program received signal SIGSEGV, Segmentation fault.
0x00415aa3 in json_string (sp=0x646c70, val=0x0) at
sprinter-json.c:121
121 j
On Mon, 6 Aug 2012 23:29:08 +0100 (BST), Sepp Tannhuber
wrote:
> Hi Anton,
>
> thanks for answering. Finally I found it. My next problem is that I have
> absolutely no idea how to use it.
> I followed the instructions I have found in this mailing list and copied the
> syntax files into my ~/.
Nice catch. I think the solution is either exactly this, or we should
strip "thread:" off notmuch-search-target-thread when we set it. I
would lean slightly toward the latter so we don't have to generate up
a new (identical) string on every notmuch-search-show-result call, but
I doubt it would ma
e: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20120806/5b15e7cd/attachment.pgp>
On Sun, 27 May 2012, Jason Ryan wrote:
> Ref: id:"20120527004107.GA4869 at Centurion"
>
> Please find attached the patch with a descriptive commit message?
Hi, this patch no longer applies to master, so I've tagged it as
notmuch::stale. (See http://nmbug.tethera.net/status/)
>
> /J
>
> --
>
>
Hi,
On Sun, 5 Aug 2012 14:52:44 +0100 (BST), Sepp Tannhuber wrote:
> Dear all,
>
> I would like to check the available vim plugins. At least I found three:
> - the original one
> - Felipe's ruby plugin
> - Anton's python plugin
>
> First of all can you tell me where I find the files of the pyt
On Sat, Jul 14 2012, Austin Clements wrote:
> Previously, notmuch-show-previous-message would move to the beginning
> of the message before the message containing point. This patch makes
> it instead move to the previous message *boundary*. That is, if point
> isn't already at the beginning of
Nice catch. I think the solution is either exactly this, or we should
strip "thread:" off notmuch-search-target-thread when we set it. I
would lean slightly toward the latter so we don't have to generate up
a new (identical) string on every notmuch-search-show-result call, but
I doubt it would ma
On Mon, Aug 06 2012, David Bremner wrote:
> It has been a few months since we last had a release.
>
> I'd like to to another release within the next few weeks. To this end
> I'd like to take a snapshot of master next Sunday (August 12), and
> release that plus urgent bugfixes a week later (August
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.
---
emacs/notmuch-show.el | 16 +---
1 files changed, 13 insertions(
Hi
I have found a small bug in the recent changes to notmuch search to use
the JSON output. If you refresh the search buffer "point" does not stay
on the same thread.
I think the problem is that notmuch-search-refresh-view calls notmuch
search with target-thread set to notmuch-search-find-threa
Hi Anton,
thanks for answering. Finally I found it. My next problem is that I have
absolutely no idea how to use it.
I followed the instructions I have found in this mailing list and copied the
syntax files into my ~/.vim/syntax
and the two plugin files into my ~/.vim/plugin folders.
Then I cal
I'm not sure it's worth updating the text format. There's already
plenty of disparity between the JSON and text formats, we're
considering deprecating the text format, and, from what I understand,
this might actually break consumers of the text format (the vim
frontend?) since the text format isn'
What's the overall goal of adding this? Are you planning to add size
information to one of the frontends?
Quoth Peter Wang on Aug 05 at 5:22 pm:
> If a leaf part's body content is omitted, return the content length in
> --format=json output. This information may be used by the consumer,
> e.g.
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 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 like
I'm not sure it's worth updating the text format. There's already
plenty of disparity between the JSON and text formats, we're
considering deprecating the text format, and, from what I understand,
this might actually break consumers of the text format (the vim
frontend?) since the text format isn'
What's the overall goal of adding this? Are you planning to add size
information to one of the frontends?
Quoth Peter Wang on Aug 05 at 5:22 pm:
> If a leaf part's body content is omitted, return the content length in
> --format=json output. This information may be used by the consumer,
> e.g.
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
Hi,
On Sun, 5 Aug 2012 14:52:44 +0100 (BST), Sepp Tannhuber
wrote:
> Dear all,
>
> I would like to check the available vim plugins. At least I found three:
> - the original one
> - Felipe's ruby plugin
> - Anton's python plugin
>
> First of all can you tell me where I find the files of the py
On Sun, 27 May 2012, Jason Ryan wrote:
> Ref: id:"20120527004107.GA4869@Centurion"
>
> Please find attached the patch with a descriptive commit message…
Hi, this patch no longer applies to master, so I've tagged it as
notmuch::stale. (See http://nmbug.tethera.net/status/)
>
> /J
>
> --
>
> htt
david at tethera.net writes:
> From: David Bremner
>
> The syntax --output=filename is a smaller change than deleting the
> output argument completely, and conceivably useful e.g. when running
> notmuch under a debugger.
I pushed these three patches. Let the angry howls from people running
produ
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.
---
emacs/notmuch-show.el | 16 +---
1 files changed, 13 insertions(
On Sun, 05 Aug 2012 14:37:02 -0700, Jameson Graef Rollins
wrote:
> On Sun, Aug 05 2012, Peter Wang wrote:
> > diff --git a/devel/schemata b/devel/schemata
> > index 9cb25f5..3df2764 100644
> > --- a/devel/schemata
> > +++ b/devel/schemata
> > @@ -69,7 +69,10 @@ part = {
> > # A leaf part's
On Sat, Jul 14 2012, Austin Clements wrote:
> Previously, notmuch-show-previous-message would move to the beginning
> of the message before the message containing point. This patch makes
> it instead move to the previous message *boundary*. That is, if point
> isn't already at the beginning of
On Mon, Aug 06 2012, David Bremner wrote:
> It has been a few months since we last had a release.
>
> I'd like to to another release within the next few weeks. To this end
> I'd like to take a snapshot of master next Sunday (August 12), and
> release that plus urgent bugfixes a week later (August
da...@tethera.net writes:
> From: David Bremner
>
> The syntax --output=filename is a smaller change than deleting the
> output argument completely, and conceivably useful e.g. when running
> notmuch under a debugger.
I pushed these three patches. Let the angry howls from people running
producti
> Quoth Michal Nazarewicz on Aug 03 at 4:29 pm:
>> I've just started using notmuch and am wondering if there is a way to
>> make message “inherit” some of the tags from messages they are written
>> in replay to (or in general are part of the same thread).
>>
>> I'm mostly thinking about a “mute”
Hi David, thanks for the review!
On Sun, 05 Aug 2012, David Bremner wrote:
> Jani Nikula writes:
>
>> +
>> +static enum field
>> +abs_to_rel_field (enum field field)
>> +{
>> +assert (field <= TM_ABS_YEAR);
>> +
>> +/* note: depends on the enum ordering */
>> +return field + (TM_REL
30 matches
Mail list logo
