Ian Main schrieb am 18:02 Freitag, 24.Oktober 2014:
> Interesting, good feedback. Is it the usage that is difficult or setup?
Installation was not a problem for me although the files ?notmuch.vim? and
?notmuch.txt? were not found by ?make install? for some reason. So I linked
them into the
On Fri, Oct 24 2014, Ian Main wrote:
This patch does not apply on top of notmuchmail master
(commit 38240d106139da8).
> This patch adds URI handling to the vim client. You can now press
Although insignificant, I'll start commenting on all sent patches
(that I look into) which talk like 'This
---
test/T160-json.sh| 9 +
test/T170-sexp.sh| 4 ++--
test/T470-missing-headers.sh | 8
3 files changed, 19 insertions(+), 2 deletions(-)
diff --git a/test/T160-json.sh b/test/T160-json.sh
index c1cf649..0a8df18 100755
--- a/test/T160-json.sh
+++
Rather than splitting the :authors attribute, which is error prone,
use the separate :authors_matched and :authors_non_matched attributes.
This improves the display of authors should one of them include a pipe
symbol (|) in their 'from' address.
---
emacs/notmuch.el | 64
In addition to the 'authors' attribute of each search result, include
'authors_matched' and 'authors_non_matched' attributes. Both
attributes are always included and are formatted as a list of
authors. If there are no matching authors, the 'authors_non_matched'
attribute is set to the empty list.
Improve the display of matching/non-matching authors.
Distinguishing between matching and non-matching authors in the emacs
interface is currently done by parsing the :authors attribute of a
search result. If one of the authors uses the pipe symbol (|) in their
'From' address this parsing
Hi
mboxviewfs is a FUSE filesystem program which shows mbox file
as a separate files under -MM directories in a mountpoint.
example usage transcript:
$ cd ~
$ mkdir notmuchmailbox
$ cd notmuchmailbox
$ wget https://raw.githubusercontent.com/domo141/nottoomuch/master/mboxviewfs.c
...
On Fri, Oct 24 2014, Eric Abrahamsen wrote:
> David Belohrad writes:
>
>> Dear All,
>>
>> i'm using org. And I'm using notmuch (that's why I address both mailing
>> lists). Now, writing an email in everyday bussiness requires a
>> non-significant time of your workhours. So I'd like to have this
Dear All,
i'm using org. And I'm using notmuch (that's why I address both mailing
lists). Now, writing an email in everyday bussiness requires a
non-significant time of your workhours. So I'd like to have this event
in my org agenda. So any time I send some email with a given subject,
I'd like to
Sepp Tannhuber wrote:
> Ian Main schrieb am 18:02 Freitag, 24.Oktober 2014:
>
> > Interesting, good feedback. Is it the usage that is difficult or setup?
> Installation was not a problem for me although the files ?notmuch.vim? and
> ?notmuch.txt? were not found by ?make install? for some
Hi Mark,
I mostly agree with your points mentioned in this and other your emails.
I'll prepare v4 based on that.
On Wed, Oct 22 2014, Mark Walters wrote:
> On Sun, 12 Oct 2014, Michal Sojka wrote:
>> The new outputs allow printing senders, recipients or both of matching
>> messages. The
On Fri, Oct 24 2014, Ian Main wrote:
> Add URI handling to the vim client. You can now press 'enter' by default and
> the client will parse the current line and find any 'Part's or URIs available
> for opening. If there are more than one it opens the one under the cursor or
> else it opens the
On Thu, Oct 23 2014, Mark Walters wrote:
> On Sun, 12 Oct 2014, Michal Sojka wrote:
>> The new outputs allow printing senders, recipients or both of matching
>> messages. The --output option is converted from "keyword" argument to
>> "flags" argument, which means that the user can use
On Fri, Oct 24 2014, David Bremner wrote:
> Apparently README.md overrides README, so this will show up instead of
> our generic README on github.
>
> If the user is already on github, then clicking a link for more
> information is not a hardship.
LGTM. although I'd prefer README.rst
Tomi
>
Tomi Ollila writes:
> On Fri, Oct 24 2014, David Bremner wrote:
>
>> Apparently README.md overrides README, so this will show up instead of
>> our generic README on github.
>>
>> If the user is already on github, then clicking a link for more
>> information is not a hardship.
>
> LGTM. although
On Thu, Oct 23 2014, Mark Walters wrote:
> Thinking about this some more how about printing the name and address as
> a structured pair/map (at least for all cases except text/text0 output):
> something like (in JSON)
> [name: "John Doe" address: "john.doe at example.com"]
>
> It seems wrong to me
On Fri, Oct 24 2014, Mark Walters wrote:
> What about having both authors_matched and authors_not_matched as lists
> of authors (ie one string for each author)?
That's a sensible idea. I will look into it.
> Then emacs, for example, wouldn't try and parse the string back into
> authors before
Apparently README.md overrides README, so this will show up instead of
our generic README on github.
If the user is already on github, then clicking a link for more
information is not a hardship.
---
README.md | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 README.md
Hi
I definitely like the idea: some comments below.
On Fri, 24 Oct 2014, David Edmondson wrote:
> In addition to the :authors attribute of each search result, include
> :authors_matched and :authors_non_matched attributes. Both attributes
> are always included. If there are no non-matching
Tomi Ollila wrote:
> On Fri, Oct 24 2014, Ian Main wrote:
>
> This patch does not apply on top of notmuchmail master
> (commit 38240d106139da8).
>
> > This patch adds URI handling to the vim client. You can now press
>
> Although insignificant, I'll start commenting on all sent patches
>
David Edmondson writes:
> On Fri, Oct 24 2014, Eric Abrahamsen wrote:
>> David Belohrad writes:
>>
>>> Dear All,
>>>
>>> i'm using org. And I'm using notmuch (that's why I address both mailing
>>> lists). Now, writing an email in everyday bussiness requires a
>>> non-significant time of your
Ian Main schrieb am 6:28 Freitag, 24.Oktober 2014:
> I wonder if you'd be willing to give the vim client a go. We've done a lot
> of work to it lately and I think it would handle all you listed here.
For me, it's hard to get familiar with it because I have not found a detailed
documentation.
---
test/T160-json.sh| 4
test/T170-sexp.sh| 4 ++--
test/T470-missing-headers.sh | 4
3 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/test/T160-json.sh b/test/T160-json.sh
index c1cf649..d3cf2e7 100755
--- a/test/T160-json.sh
+++
Rather than splitting the :authors attribute, which is error prone,
use the separate :authors_matched and :authors_non_matched attributes.
This improves the display of authors should one of them include a pipe
symbol (|) in their 'from' address.
---
emacs/notmuch.el | 64
In addition to the :authors attribute of each search result, include
:authors_matched and :authors_non_matched attributes. Both attributes
are always included. If there are no non-matching authors, the
:authors_non_matched attribute is set to the empty string.
---
lib/notmuch.h| 34
Improve the display of matching/non-matching authors.
Distinguishing between matching and non-matching authors in the emacs
interface is currently done by parsing the :authors attribute of a
search result. If one of the authors uses the pipe symbol (|) in their
'From' address this parsing
Add URI handling to the vim client. You can now press 'enter' by
default and the client will parse the current line and find any 'Part's
or URIs available for opening. If there are more than one it opens the
one under the cursor or else it opens the only one available. It also
supports mailto:
Change how the notmuch vim client supports attachments:
- For each message part a 'Part : ' is added to the
header.
- You can then use 'e' to extract the attachment under the cursor or
use it elsewhere to extract all attachments (the prior behavior)
- You can use 'v' to 'view' the
This patch adds URI handling to the vim client. You can now press
'enter' by default and the client will parse the current line and find
any 'Part's or URIs available for opening. If there are more than one
it opens the one under the cursor or else it opens the only one
available. It also
Sepp Tannhuber wrote:
> Ian Main schrieb am 6:28 Freitag, 24.Oktober 2014:
>
> > I wonder if you'd be willing to give the vim client a go. We've done a lot
> > of work to it lately and I think it would handle all you listed here.
> For me, it's hard to get familiar with it because I have not
These macros help clarify basic bit-twiddling code and are written to
be robust against C undefined behavior of shift operators.
---
lib/message.cc| 6 +++---
lib/notmuch-private.h | 11 +++
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/lib/message.cc
Quoth Mark Walters on Oct 24 at 10:23 am:
>
> Hi
>
> I definitely like the idea: some comments below.
Agreed.
> On Fri, 24 Oct 2014, David Edmondson wrote:
> > In addition to the :authors attribute of each search result, include
> > :authors_matched and :authors_non_matched attributes. Both
This one is pretty straightforward and useful too.
Ian
Ian Main wrote:
> This adds the ability to mark an entire folder as read (or any other
> tags you like once you map it).
>
> This update adds documentation for the command.
>
> Ian
> ---
> vim/notmuch.txt | 1 +
> vim/notmuch.vim
Can I get someone to test this one? It's pretty simple and useful.
Ian
Ian Main wrote:
> This patch makes the folder screen refresh each time you 'enter' it.
> This way when you read a folder and mark items as read the changes are
> reflected immediately when you return to the folder view.
Can I get someone to test this one? It's pretty simple and useful.
Ian
Ian Main wrote:
This patch makes the folder screen refresh each time you 'enter' it.
This way when you read a folder and mark items as read the changes are
reflected immediately when you return to the folder view.
This one is pretty straightforward and useful too.
Ian
Ian Main wrote:
This adds the ability to mark an entire folder as read (or any other
tags you like once you map it).
This update adds documentation for the command.
Ian
---
vim/notmuch.txt | 1 +
vim/notmuch.vim | 11
Apparently README.md overrides README, so this will show up instead of
our generic README on github.
If the user is already on github, then clicking a link for more
information is not a hardship.
---
README.md | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 README.md
In addition to the :authors attribute of each search result, include
:authors_matched and :authors_non_matched attributes. Both attributes
are always included. If there are no non-matching authors, the
:authors_non_matched attribute is set to the empty string.
---
lib/notmuch.h| 34
Improve the display of matching/non-matching authors.
Distinguishing between matching and non-matching authors in the emacs
interface is currently done by parsing the :authors attribute of a
search result. If one of the authors uses the pipe symbol (|) in their
'From' address this parsing
Rather than splitting the :authors attribute, which is error prone,
use the separate :authors_matched and :authors_non_matched attributes.
This improves the display of authors should one of them include a pipe
symbol (|) in their 'from' address.
---
emacs/notmuch.el | 64
Ian Main im...@redhat.com schrieb am 6:28 Freitag, 24.Oktober 2014:
I wonder if you'd be willing to give the vim client a go. We've done a lot
of work to it lately and I think it would handle all you listed here.
For me, it's hard to get familiar with it because I have not found a detailed
On Fri, Oct 24 2014, David Bremner da...@tethera.net wrote:
Apparently README.md overrides README, so this will show up instead of
our generic README on github.
If the user is already on github, then clicking a link for more
information is not a hardship.
LGTM. although I'd prefer
Hi
I definitely like the idea: some comments below.
On Fri, 24 Oct 2014, David Edmondson d...@dme.org wrote:
In addition to the :authors attribute of each search result, include
:authors_matched and :authors_non_matched attributes. Both attributes
are always included. If there are no
On Thu, Oct 23 2014, Mark Walters markwalters1...@gmail.com wrote:
On Sun, 12 Oct 2014, Michal Sojka sojk...@fel.cvut.cz wrote:
The new outputs allow printing senders, recipients or both of matching
messages. The --output option is converted from keyword argument to
flags argument, which
On Fri, Oct 24 2014, Ian Main im...@stemwinder.org wrote:
Add URI handling to the vim client. You can now press 'enter' by default and
the client will parse the current line and find any 'Part's or URIs available
for opening. If there are more than one it opens the one under the cursor or
Tomi Ollila tomi.oll...@iki.fi writes:
On Fri, Oct 24 2014, David Bremner da...@tethera.net wrote:
Apparently README.md overrides README, so this will show up instead of
our generic README on github.
If the user is already on github, then clicking a link for more
information is not a
On Thu, Oct 23 2014, Mark Walters wrote:
Thinking about this some more how about printing the name and address as
a structured pair/map (at least for all cases except text/text0 output):
something like (in JSON)
[name: John Doe address: john@example.com]
It seems wrong to me to go to the
On Fri, Oct 24 2014, Mark Walters wrote:
What about having both authors_matched and authors_not_matched as lists
of authors (ie one string for each author)?
That's a sensible idea. I will look into it.
Then emacs, for example, wouldn't try and parse the string back into
authors before
Hi Mark,
I mostly agree with your points mentioned in this and other your emails.
I'll prepare v4 based on that.
On Wed, Oct 22 2014, Mark Walters wrote:
On Sun, 12 Oct 2014, Michal Sojka sojk...@fel.cvut.cz wrote:
The new outputs allow printing senders, recipients or both of matching
Quoth Mark Walters on Oct 24 at 10:23 am:
Hi
I definitely like the idea: some comments below.
Agreed.
On Fri, 24 Oct 2014, David Edmondson d...@dme.org wrote:
In addition to the :authors attribute of each search result, include
:authors_matched and :authors_non_matched attributes.
These macros help clarify basic bit-twiddling code and are written to
be robust against C undefined behavior of shift operators.
---
lib/message.cc| 6 +++---
lib/notmuch-private.h | 11 +++
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/lib/message.cc
Dear All,
i'm using org. And I'm using notmuch (that's why I address both mailing
lists). Now, writing an email in everyday bussiness requires a
non-significant time of your workhours. So I'd like to have this event
in my org agenda. So any time I send some email with a given subject,
I'd like to
On Fri, Oct 24 2014, Eric Abrahamsen wrote:
David Belohrad da...@belohrad.ch writes:
Dear All,
i'm using org. And I'm using notmuch (that's why I address both mailing
lists). Now, writing an email in everyday bussiness requires a
non-significant time of your workhours. So I'd like to have
Sepp Tannhuber wrote:
Ian Main im...@redhat.com schrieb am 6:28 Freitag, 24.Oktober 2014:
I wonder if you'd be willing to give the vim client a go. We've done a lot
of work to it lately and I think it would handle all you listed here.
For me, it's hard to get familiar with it because I
This patch adds URI handling to the vim client. You can now press
'enter' by default and the client will parse the current line and find
any 'Part's or URIs available for opening. If there are more than one
it opens the one under the cursor or else it opens the only one
available. It also
On Fri, Oct 24 2014, Ian Main im...@stemwinder.org wrote:
This patch does not apply on top of notmuchmail master
(commit 38240d106139da8).
This patch adds URI handling to the vim client. You can now press
Although insignificant, I'll start commenting on all sent patches
(that I look into)
Add URI handling to the vim client. You can now press 'enter' by
default and the client will parse the current line and find any 'Part's
or URIs available for opening. If there are more than one it opens the
one under the cursor or else it opens the only one available. It also
supports mailto:
Change how the notmuch vim client supports attachments:
- For each message part a 'Part number: filename' is added to the
header.
- You can then use 'e' to extract the attachment under the cursor or
use it elsewhere to extract all attachments (the prior behavior)
- You can use 'v' to 'view'
David Edmondson d...@dme.org writes:
On Fri, Oct 24 2014, Eric Abrahamsen wrote:
David Belohrad da...@belohrad.ch writes:
Dear All,
i'm using org. And I'm using notmuch (that's why I address both mailing
lists). Now, writing an email in everyday bussiness requires a
non-significant time
In addition to the 'authors' attribute of each search result, include
'authors_matched' and 'authors_non_matched' attributes. Both
attributes are always included and are formatted as a list of
authors. If there are no matching authors, the 'authors_non_matched'
attribute is set to the empty list.
Improve the display of matching/non-matching authors.
Distinguishing between matching and non-matching authors in the emacs
interface is currently done by parsing the :authors attribute of a
search result. If one of the authors uses the pipe symbol (|) in their
'From' address this parsing
---
test/T160-json.sh| 9 +
test/T170-sexp.sh| 4 ++--
test/T470-missing-headers.sh | 8
3 files changed, 19 insertions(+), 2 deletions(-)
diff --git a/test/T160-json.sh b/test/T160-json.sh
index c1cf649..0a8df18 100755
--- a/test/T160-json.sh
+++
Rather than splitting the :authors attribute, which is error prone,
use the separate :authors_matched and :authors_non_matched attributes.
This improves the display of authors should one of them include a pipe
symbol (|) in their 'from' address.
---
emacs/notmuch.el | 64
Ian Main im...@stemwinder.org schrieb am 18:02 Freitag, 24.Oktober 2014:
Interesting, good feedback. Is it the usage that is difficult or setup?
Installation was not a problem for me although the files »notmuch.vim« and
»notmuch.txt« were not found by »make install« for some reason. So I
Sepp Tannhuber wrote:
Ian Main im...@stemwinder.org schrieb am 18:02 Freitag, 24.Oktober 2014:
Interesting, good feedback. Is it the usage that is difficult or setup?
Installation was not a problem for me although the files »notmuch.vim« and
»notmuch.txt« were not found by »make install«
65 matches
Mail list logo
