On Wed, 29 Feb 2012 17:47:46 -0500, Austin Clements wrote:
> > On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements
> > wrote:
> > > What if the output of search (say, specifically the JSON format)
> > > included information on each message in the thread such as the
> > > 'message' production
On Wed, 29 Feb 2012 17:47:46 -0500, Austin Clements amdra...@mit.edu wrote:
On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements amdra...@mit.edu
wrote:
What if the output of search (say, specifically the JSON format)
included information on each message in the thread such as the
On Wed, 29 Feb 2012 10:50:46 -0500, Jesse Rosenthal
wrote:
> On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements
> wrote:
> > What if the output of search (say, specifically the JSON format)
> > included information on each message in the thread such as the
> > 'message' production from
On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements wrote:
> What if the output of search (say, specifically the JSON format)
> included information on each message in the thread such as the
> 'message' production from devel/schemata minus the body field? Then
> the frontend would have loads of
Quoth Jesse Rosenthal on Feb 29 at 10:05 am:
> On Sun, 26 Feb 2012 16:59:53 -0500, Tom Prince
> wrote:
> > It is probably overkill for any one feature, but it does seem like
> > something useful to have. So maybe it would be worthwhile to create
> > for this one feature, even it it is overkill.
On Sun, 26 Feb 2012 16:59:53 -0500, Tom Prince
wrote:
> It is probably overkill for any one feature, but it does seem like
> something useful to have. So maybe it would be worthwhile to create
> for this one feature, even it it is overkill.
I can think of other features where some layer like
On Sun, 26 Feb 2012 16:59:53 -0500, Tom Prince tom.pri...@ualberta.net wrote:
It is probably overkill for any one feature, but it does seem like
something useful to have. So maybe it would be worthwhile to create
for this one feature, even it it is overkill.
I can think of other features where
On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements amdra...@mit.edu wrote:
What if the output of search (say, specifically the JSON format)
included information on each message in the thread such as the
'message' production from devel/schemata minus the body field? Then
the frontend would
On Wed, 29 Feb 2012 10:50:46 -0500, Jesse Rosenthal jrosent...@jhu.edu wrote:
On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements amdra...@mit.edu wrote:
What if the output of search (say, specifically the JSON format)
included information on each message in the thread such as the
'message'
On Sun, 26 Feb 2012 11:22:10 +, Patrick Totzke wrote:
> > so it would seem more appropriate that this be done in the backend.
> I agree. I personally think this is a nice feature to have in all
> user interfaces to notmuch and therefore it makes sense to implement it once
> in the lib. Also
On Sun, 26 Feb 2012 12:51:49 -0400, David Bremner wrote:
> I have sometimes wondered about having another library layer making some
> of the current CLI functionality accessible to bindings. I'm not really
> sure of the pro's and con's of such approach. It would certainly be
> overkill for this
On Sun, 26 Feb 2012 17:41:04 +0100, Daniel Schoepe
wrote:
>
> At least it should not be done in the library, because it'd need to read
> the user's addresses from configuration file which the library is not
> supposed to access, as far as I understand.
>
One can work around this by passing in
Quoting Daniel (2012-02-25 16:34:15)
>From what I understand, at least the Python bindings deliver primarily author
>names (not addresses),
To clarify, `notmuch.Thread.get_authors` returns a comma separated list of the
realname parts of all From-headers that occur in messages of this thread.
>
Quoting Daniel (2012-02-25 16:34:15)
From what I understand, at least the Python bindings deliver primarily author
names (not addresses),
To clarify, `notmuch.Thread.get_authors` returns a comma separated list of the
realname parts of all From-headers that occur in messages of this thread.
so
On Sun, 26 Feb 2012 11:22:10 +, Patrick Totzke
patricktot...@googlemail.com wrote:
so it would seem more appropriate that this be done in the backend.
I agree. I personally think this is a nice feature to have in all
user interfaces to notmuch and therefore it makes sense to implement it
On Sun, 26 Feb 2012 17:41:04 +0100, Daniel Schoepe dan...@schoepe.org wrote:
At least it should not be done in the library, because it'd need to read
the user's addresses from configuration file which the library is not
supposed to access, as far as I understand.
One can work around this
On Sun, 26 Feb 2012 12:51:49 -0400, David Bremner da...@tethera.net wrote:
I have sometimes wondered about having another library layer making some
of the current CLI functionality accessible to bindings. I'm not really
sure of the pro's and con's of such approach. It would certainly be
Have somebody tried to implement replacement of the user author with "me" in
author lists (using defined email address(es))?
>From what I understand, at least the Python bindings deliver primarily author
names (not addresses), so it would seem more appropriate that this be done in
the backend.
18 matches
Mail list logo
