Quick! While cworth is working I want to push this back to the top of
the queue!
crypto branch is still ready for merge!
git://finestructure.net/notmuch
Thanks!
jamie.
pgpU4YPWyQSEZ.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@no
Quick! While cworth is working I want to push this back to the top of
the queue!
crypto branch is still ready for merge!
git://finestructure.net/notmuch
Thanks!
jamie.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signat
Hey, folks. I just pushed a couple of patches to my "crypto" branch [0]
that add support for auto-tagging of multipart/signed and
multipart/encrypted messages with the "signed" and "encrypted" tags
respectively. Only new messages are thus tagged, so a database rebuild
is required to auto-tag old
Hey, folks. I just pushed a couple of patches to my "crypto" branch [0]
that add support for auto-tagging of multipart/signed and
multipart/encrypted messages with the "signed" and "encrypted" tags
respectively. Only new messages are thus tagged, so a database rebuild
is required to auto-tag old
On Mon, 28 Feb 2011 14:24:03 +0100, Sebastian Spaeth
wrote:
> On Sun, 27 Feb 2011 10:41:48 +, Darren McGuicken fernseed.info> wrote:
> I also run the crypto branch since it has been published and it is
> working just fine.
I have just started using the crypto branch, and after a few mistep
On Mon, 28 Feb 2011 14:24:03 +0100, Sebastian Spaeth
wrote:
> On Sun, 27 Feb 2011 10:41:48 +, Darren McGuicken
> wrote:
> I also run the crypto branch since it has been published and it is
> working just fine.
I have just started using the crypto branch, and after a few misteps on
my part
Jameson Rollins writes:
> If folks have suggestions for disambiguating tag names that don't
> themselves create further confusion on some other front, then I'm
> inclined to just go with the simplest and most straightforward tag name.
Are persistent tags required here? The original question at
On Mon, 28 Feb 2011 21:16:13 -0600, Rob Browning wrote:
> Are persistent tags required here? The original question at least,
> seemed to just be asking for a visual indicator that a message has
> encrypted or signed bits. So I wondered if that might be accomplished
> without actual tags.
Hey, R
On Mon, 28 Feb 2011 21:16:13 -0600, Rob Browning
wrote:
> Are persistent tags required here? The original question at least,
> seemed to just be asking for a visual indicator that a message has
> encrypted or signed bits. So I wondered if that might be accomplished
> without actual tags.
Hey,
Jameson Rollins writes:
> If folks have suggestions for disambiguating tag names that don't
> themselves create further confusion on some other front, then I'm
> inclined to just go with the simplest and most straightforward tag name.
Are persistent tags required here? The original question at
On Mon, 28 Feb 2011 15:08:39 -0500, Daniel Kahn Gillmor
wrote:
> The outstanding question in my mind is whether those tags could be
> mistaken by a naïve user for meaning one of the other concepts. Is
> there a way to name the tags to minimize that kind of confusion?
I think that would be diffi
On Mon, 28 Feb 2011 15:08:39 -0500, Daniel Kahn Gillmor wrote:
> The outstanding question in my mind is whether those tags could be
> mistaken by a na?ve user for meaning one of the other concepts. Is
> there a way to name the tags to minimize that kind of confusion?
I think that would be diffic
On 02/28/2011 02:56 PM, Jameson Rollins wrote:
> On Mon, 28 Feb 2011 13:59:54 -0500, Daniel Kahn Gillmor fifthhorseman.net> wrote:
>> But: what does the "signed" tag mean? i wouldn't want to necessarily
>> conflate these four ideas:
>
> These are good points, Daniel. However, I had actually just
On Sun, 27 Feb 2011 10:41:48 +, Darren McGuicken wrote:
> If feedback is needed here then likewise, I've been running the crypto
> branch since it was made available. The only strangeness I've seen was
> that which was reported in id:"87sjw2h6xy.fsf at bookbinder.fernseed.info"
> for expired
On 02/28/2011 01:25 PM, Jameson Rollins wrote:
> On Mon, 28 Feb 2011 08:52:45 -0500, Ross Glover
> wrote:
>> I too am now running the crypto branch and find it quite amazing. The
>> one feature I would like added, though, is some face color or
>> auto-tagging in the search buffer for mail with e
On 02/28/2011 02:56 PM, Jameson Rollins wrote:
> On Mon, 28 Feb 2011 13:59:54 -0500, Daniel Kahn Gillmor
> wrote:
>> But: what does the "signed" tag mean? i wouldn't want to necessarily
>> conflate these four ideas:
>
> These are good points, Daniel. However, I had actually just been
> thinking
On Mon, 28 Feb 2011 13:59:54 -0500, Daniel Kahn Gillmor
wrote:
> But: what does the "signed" tag mean? i wouldn't want to necessarily
> conflate these four ideas:
These are good points, Daniel. However, I had actually just been
thinking of something much simpler, along the lines of just tagging
On Mon, 28 Feb 2011 13:59:54 -0500, Daniel Kahn Gillmor wrote:
> But: what does the "signed" tag mean? i wouldn't want to necessarily
> conflate these four ideas:
These are good points, Daniel. However, I had actually just been
thinking of something much simpler, along the lines of just tagging
On 02/28/2011 01:25 PM, Jameson Rollins wrote:
> On Mon, 28 Feb 2011 08:52:45 -0500, Ross Glover
> wrote:
>> I too am now running the crypto branch and find it quite amazing. The
>> one feature I would like added, though, is some face color or
>> auto-tagging in the search buffer for mail with e
On Mon, 28 Feb 2011 08:52:45 -0500, Ross Glover wrote:
> I too am now running the crypto branch and find it quite amazing. The
> one feature I would like added, though, is some face color or
> auto-tagging in the search buffer for mail with encrypted mime parts.
> It seems like this could be achi
On Mon, 28 Feb 2011 08:52:45 -0500, Ross Glover
wrote:
> I too am now running the crypto branch and find it quite amazing. The
> one feature I would like added, though, is some face color or
> auto-tagging in the search buffer for mail with encrypted mime parts.
> It seems like this could be ach
I too am now running the crypto branch and find it quite amazing. The
one feature I would like added, though, is some face color or
auto-tagging in the search buffer for mail with encrypted mime parts.
It seems like this could be achieved with notmuch effort (by someone
notme) by adding similar fu
I too am now running the crypto branch and find it quite amazing. The
one feature I would like added, though, is some face color or
auto-tagging in the search buffer for mail with encrypted mime parts.
It seems like this could be achieved with notmuch effort (by someone
notme) by adding similar fu
On Sun, 27 Feb 2011 10:41:48 +, Darren McGuicken
wrote:
> If feedback is needed here then likewise, I've been running the crypto
> branch since it was made available. The only strangeness I've seen was
> that which was reported in id:"87sjw2h6xy@bookbinder.fernseed.info"
> for expired ke
On Sat, 26 Feb 2011 20:45:15 -0400, David Bremner wrote:
> Further to our discussion on IRC the other day about providing
> feedback on patches, I have run these patches pretty much all of
> February with no glitches. I am running them on 3 different machines,
> although they are all Debian AMD64
On Sat, 26 Feb 2011 20:45:15 -0400, David Bremner wrote:
> Further to our discussion on IRC the other day about providing
> feedback on patches, I have run these patches pretty much all of
> February with no glitches. I am running them on 3 different machines,
> although they are all Debian AMD64
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins wrote:
> Hi, all. I have pushed a new branch called "crypto" to my notmuch
> repository [0]. This branch provides full support for PGP/MIME signed
> and encrypted messages, including emacs UI support. It has been applied
> on top of cworth's c
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins
wrote:
> Hi, all. I have pushed a new branch called "crypto" to my notmuch
> repository [0]. This branch provides full support for PGP/MIME signed
> and encrypted messages, including emacs UI support. It has been applied
> on top of cworth's
On Fri, 04 Feb 2011 09:32:23 -0800, Jameson Rollins wrote:
> Yeah, I've found some emails that are doing this as well. I'm looking
> in to what we can do to mitigate the problem, which I think is
> ultimately a problem in GMime. The json output should not be
> breaking, though, so that I will de
On Fri, 04 Feb 2011 09:32:23 -0800, Jameson Rollins
wrote:
> Yeah, I've found some emails that are doing this as well. I'm looking
> in to what we can do to mitigate the problem, which I think is
> ultimately a problem in GMime. The json output should not be
> breaking, though, so that I will d
I just love seeing all those yellow signatures. It reminds me to meet
you all in real life to verify your keys :-).
Thanks for implementing this, the whole lot of you. It works really
well.
Sebastian
-- next part --
A non-text attachment was scrubbed...
Name: not availabl
Hey, folks. I've pushed some improvements to the "crypto" branch that:
* add support for replying to encrypted messages
* don't show sigstatus button for unsigned encrypted messages
As always, please let me know encounter any problems.
jamie.
pgpOKBX6CVNwM.pgp
Description: PGP signature
_
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins wrote:
>
> Please test and provide feedback. I would really like to see this
> series merged into the mainline for the next release, if at all
> possible.
I reported some pretty weird experiences yesterday on IRC with replies
not working. It t
Hey, folks. I've pushed some improvements to the "crypto" branch that:
* add support for replying to encrypted messages
* don't show sigstatus button for unsigned encrypted messages
As always, please let me know encounter any problems.
jamie.
-- next part --
A non-text a
On 02/04/2011 11:59 AM, micah anderson wrote:
> On Thu, 03 Feb 2011 14:52:01 -0500, Daniel Kahn Gillmor fifthhorseman.net> wrote:
>> when you say "encrypted by" do you mean "encrypted to"? do you have
>> access to the corresponding secret key?
>
> If I open a message that was sent to me and was
On Thu, 03 Feb 2011 13:02:41 -0800, Jameson Rollins wrote:
> > Can we pass the decrypted text to message mode on a reply?
> Yeah, some folks pointed this out on #notmuch this morning. The
> decryption is only happening in notmuch-show, but we need to do it in
> notmuch-reply as well for the decry
On Thu, 03 Feb 2011 14:52:01 -0500, Daniel Kahn Gillmor wrote:
> On 02/03/2011 11:25 AM, micah anderson wrote:
> > 1. I personally think notmuch-show-process-pgpmime should default to
> > true
>
> note that with it set to false, you can still M-RET (instead of RET) on
> an item in the summary wi
On Fri, 04 Feb 2011 13:12:27 -0400, David Bremner wrote:
> I reported some pretty weird experiences yesterday on IRC with replies
> not working. It turns out they were caused by having old versions of
> xapian installed in /usr/local (which I think might have caused some
> mixup with headers and l
On Fri, 04 Feb 2011 13:12:27 -0400, David Bremner wrote:
> I reported some pretty weird experiences yesterday on IRC with replies
> not working. It turns out they were caused by having old versions of
> xapian installed in /usr/local (which I think might have caused some
> mixup with headers and l
On Fri, 04 Feb 2011 12:09:48 +, Darren McGuicken
wrote:
> On Thu, 03 Feb 2011 13:02:41 -0800, Jameson Rollins
> wrote:
> > > Can we pass the decrypted text to message mode on a reply?
> > Yeah, some folks pointed this out on #notmuch this morning. The
> > decryption is only happening in no
On Fri, 04 Feb 2011 12:09:48 +, Darren McGuicken wrote:
> On Thu, 03 Feb 2011 13:02:41 -0800, Jameson Rollins finestructure.net> wrote:
> > > Can we pass the decrypted text to message mode on a reply?
> > Yeah, some folks pointed this out on #notmuch this morning. The
> > decryption is only
On 02/04/2011 11:59 AM, micah anderson wrote:
> On Thu, 03 Feb 2011 14:52:01 -0500, Daniel Kahn Gillmor
> wrote:
>> when you say "encrypted by" do you mean "encrypted to"? do you have
>> access to the corresponding secret key?
>
> If I open a message that was sent to me and was encrypted by the
On Fri, 04 Feb 2011 14:04:23 +0100, Sebastian Spaeth
wrote:
> I just love seeing all those yellow signatures. It reminds me to meet
> you all in real life to verify your keys :-).
>
> Thanks for implementing this, the whole lot of you. It works really
> well.
Yes! I'm really glad you're findin
On Fri, 04 Feb 2011 14:04:23 +0100, Sebastian Spaeth
wrote:
> I just love seeing all those yellow signatures. It reminds me to meet
> you all in real life to verify your keys :-).
>
> Thanks for implementing this, the whole lot of you. It works really
> well.
Yes! I'm really glad you're findin
On Fri, 04 Feb 2011 08:24:38 -0400, David Bremner wrote:
> On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins
> wrote:
> > Hi, all. I have pushed a new branch called "crypto" to my notmuch
> > repository [0]. This branch provides full support for PGP/MIME signed
> > and encrypted messages, in
On Fri, 04 Feb 2011 08:24:38 -0400, David Bremner wrote:
> On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins finestructure.net> wrote:
> > Hi, all. I have pushed a new branch called "crypto" to my notmuch
> > repository [0]. This branch provides full support for PGP/MIME signed
> > and encryp
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins
wrote:
>
> Please test and provide feedback. I would really like to see this
> series merged into the mainline for the next release, if at all
> possible.
I reported some pretty weird experiences yesterday on IRC with replies
not working. It
On Thu, 03 Feb 2011 14:52:01 -0500, Daniel Kahn Gillmor
wrote:
> On 02/03/2011 11:25 AM, micah anderson wrote:
> > 1. I personally think notmuch-show-process-pgpmime should default to
> > true
>
> note that with it set to false, you can still M-RET (instead of RET) on
> an item in the summary w
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins wrote:
> Hi, all. I have pushed a new branch called "crypto" to my notmuch
> repository [0]. This branch provides full support for PGP/MIME signed
> and encrypted messages, including emacs UI support. It has been applied
> on top of cworth's c
I just love seeing all those yellow signatures. It reminds me to meet
you all in real life to verify your keys :-).
Thanks for implementing this, the whole lot of you. It works really
well.
Sebastian
pgpuhM09gqBWa.pgp
Description: PGP signature
___
n
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins
wrote:
> Hi, all. I have pushed a new branch called "crypto" to my notmuch
> repository [0]. This branch provides full support for PGP/MIME signed
> and encrypted messages, including emacs UI support. It has been applied
> on top of cworth's
On Thu, 03 Feb 2011 13:02:41 -0800, Jameson Rollins
wrote:
> > Can we pass the decrypted text to message mode on a reply?
> Yeah, some folks pointed this out on #notmuch this morning. The
> decryption is only happening in notmuch-show, but we need to do it in
> notmuch-reply as well for the decr
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins wrote:
> Please test and provide feedback. I would really like to see this
> series merged into the mainline for the next release, if at all
> possible.
Fan. Tastic. Thanks so much for this, incredible work!
Grabbed and testing now, the only
On 02/03/2011 03:34 PM, Jameson Rollins wrote:
> On Thu, 03 Feb 2011 14:52:01 -0500, Daniel Kahn Gillmor fifthhorseman.net> wrote:
>> You either want to fix this in your emacs config by putting your
>> fingerprint into mml2015-signers and setting mml2015-encrypt-to-self
>>
>> Or you want to set gp
Hi Micah--
just wanted to follow up on your points/questions:
On 02/03/2011 11:25 AM, micah anderson wrote:
> 1. I personally think notmuch-show-process-pgpmime should default to
> true
note that with it set to false, you can still M-RET (instead of RET) on
an item in the summary window to have
On 02/03/2011 03:34 PM, Jameson Rollins wrote:
> On Thu, 03 Feb 2011 14:52:01 -0500, Daniel Kahn Gillmor
> wrote:
>> You either want to fix this in your emacs config by putting your
>> fingerprint into mml2015-signers and setting mml2015-encrypt-to-self
>>
>> Or you want to set gpg's default-reci
On Thu, 03 Feb 2011 20:42:38 +, Darren McGuicken
wrote:
> On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins
> wrote:
> > Please test and provide feedback. I would really like to see this
> > series merged into the mainline for the next release, if at all
> > possible.
>
> Fan. Tastic.
On Thu, 03 Feb 2011 20:42:38 +, Darren McGuicken wrote:
> On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins finestructure.net> wrote:
> > Please test and provide feedback. I would really like to see this
> > series merged into the mainline for the next release, if at all
> > possible.
>
>
On 02/02/2011 08:18 PM, Jameson Rollins wrote:
> Hi, all. I have pushed a new branch called "crypto" to my notmuch
> repository [0]. This branch provides full support for PGP/MIME signed
> and encrypted messages, including emacs UI support.
I have tested this, and am now using it. I'm very happ
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins
wrote:
> Please test and provide feedback. I would really like to see this
> series merged into the mainline for the next release, if at all
> possible.
Fan. Tastic. Thanks so much for this, incredible work!
Grabbed and testing now, the onl
On Thu, 03 Feb 2011 14:52:01 -0500, Daniel Kahn Gillmor
wrote:
> On 02/03/2011 11:25 AM, micah anderson wrote:
> > 1. I personally think notmuch-show-process-pgpmime should default to
> > true
>
> note that with it set to false, you can still M-RET (instead of RET) on
> an item in the summary wi
On Thu, 03 Feb 2011 14:52:01 -0500, Daniel Kahn Gillmor wrote:
> On 02/03/2011 11:25 AM, micah anderson wrote:
> > 1. I personally think notmuch-show-process-pgpmime should default to
> > true
>
> note that with it set to false, you can still M-RET (instead of RET) on
> an item in the summary win
Hi Micah--
just wanted to follow up on your points/questions:
On 02/03/2011 11:25 AM, micah anderson wrote:
> 1. I personally think notmuch-show-process-pgpmime should default to
> true
note that with it set to false, you can still M-RET (instead of RET) on
an item in the summary window to have
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins wrote:
> Hi, all. I have pushed a new branch called "crypto" to my notmuch
> repository [0]. This branch provides full support for PGP/MIME signed
> and encrypted messages, including emacs UI support. It has been applied
> on top of cworth's c
On 02/02/2011 08:18 PM, Jameson Rollins wrote:
> Hi, all. I have pushed a new branch called "crypto" to my notmuch
> repository [0]. This branch provides full support for PGP/MIME signed
> and encrypted messages, including emacs UI support.
I have tested this, and am now using it. I'm very happ
On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins
wrote:
> Hi, all. I have pushed a new branch called "crypto" to my notmuch
> repository [0]. This branch provides full support for PGP/MIME signed
> and encrypted messages, including emacs UI support. It has been applied
> on top of cworth's
Hi, all. I have pushed a new branch called "crypto" to my notmuch
repository [0]. This branch provides full support for PGP/MIME signed
and encrypted messages, including emacs UI support. It has been applied
on top of cworth's current master (21e97c50). It includes the
following:
* David Edmon
Hi, all. I have pushed a new branch called "crypto" to my notmuch
repository [0]. This branch provides full support for PGP/MIME signed
and encrypted messages, including emacs UI support. It has been applied
on top of cworth's current master (21e97c50). It includes the
following:
* David Edmon
68 matches
Mail list logo
