Re: notmuch - Hook return code: 134

2013-08-18 Thread Suvayu Ali
On Fri, Aug 16, 2013 at 09:53:14PM -0300, Marcelo Laia wrote:
 Hi Ali,
 
 I deleted taht message and got the similar message!
 
 
  Calling hook: notmuch new
  Hook stdout: 
 Hook stderr:terminate called after throwing an instance of
 'std::length_error'
   what():  basic_string::assign
 Aborted
 
 
  Hook return code: 134

Sorry I don't have any other ideas.  Did you ask on the notmuch mailing
list notm...@notmuchmail.org?  I didn't see your message there.  I did
see your post on the mutt-kz list though; but this is a notmuch issue.

GL,

-- 
Suvayu

Open source is the future. It sets us free.


Re: notmuch - Hook return code: 134

2013-08-18 Thread Marcelo Laia
I solved it! (:

Here is the trick:

$ notmuch dump --output=~/out.nm
$ mv ~/Mail/.notmuch ~/.notmuch.bak
$ notmuch new
$ notmuch tag -inbox -unread '*'
$ notmuch restore --accumulate --input=~/out.nm

http://notmuchmail.org/howto/#index6h2

Thank you very much!

-- 
Marcelo


Re: notmuch - Hook return code: 134

2013-08-16 Thread Marcelo Laia
Hi Ali,

I deleted taht message and got the similar message!


 Calling hook: notmuch new
 Hook stdout: 
Hook stderr:terminate called after throwing an instance of
'std::length_error'
  what():  basic_string::assign
Aborted


 Hook return code: 134


Have you any hint?

Laia


On 08/08/13 at 01:43pm, Suvayu Ali wrote:
 Hi Marcelo,
 
 Did you intend to send this to the notmuch list?  Anyway, since I use
 notmuch, I will try to answer.
 
 On Thu, Aug 08, 2013 at 07:57:09AM -0300, Marcelo Laia wrote:
  A few days a go I got problems with notmuch: it dosent index my
  messages.
  
  To day I try it by CL and got the messages:
  
   Calling hook: notmuch new
   Hook stdout: 
  Hook stderr:Note: Ignoring non-mail file:
  /home/marcelo/Mail/GMail/Enviados/cur/1309905148_0.6040.laia,U=18964,FMD5=e0c551b26041517d2160549b93207ed4:2,S
  terminate called after throwing an instance of 'std::length_error'
what():  basic_string::assign
  Aborted
  
  
   Hook return code: 134
 
 I'm assuming that you use OfflineIMAP to sync, and you call notmuch new
 in the postsynchook.  Since the error message complains about file not
 being a proper message file, I would suggest you look at the raw file
 and check if it is indeed corrupted.
 
 In the past I have noticed sometimes when the sync process gets
 interrupted, OfflineIMAP borks the file permissions of the message.  I
 have to hand fix it for OfflineIMAP to continue again.  Maybe your issue
 is another manifestation of the same problem.
 
 Hope this helps,
 

-- 
Marcelo


Re: notmuch - Hook return code: 134

2013-08-08 Thread Suvayu Ali
Hi Marcelo,

Did you intend to send this to the notmuch list?  Anyway, since I use
notmuch, I will try to answer.

On Thu, Aug 08, 2013 at 07:57:09AM -0300, Marcelo Laia wrote:
 A few days a go I got problems with notmuch: it dosent index my
 messages.
 
 To day I try it by CL and got the messages:
 
  Calling hook: notmuch new
  Hook stdout: 
 Hook stderr:Note: Ignoring non-mail file:
 /home/marcelo/Mail/GMail/Enviados/cur/1309905148_0.6040.laia,U=18964,FMD5=e0c551b26041517d2160549b93207ed4:2,S
 terminate called after throwing an instance of 'std::length_error'
   what():  basic_string::assign
 Aborted
 
 
  Hook return code: 134

I'm assuming that you use OfflineIMAP to sync, and you call notmuch new
in the postsynchook.  Since the error message complains about file not
being a proper message file, I would suggest you look at the raw file
and check if it is indeed corrupted.

In the past I have noticed sometimes when the sync process gets
interrupted, OfflineIMAP borks the file permissions of the message.  I
have to hand fix it for OfflineIMAP to continue again.  Maybe your issue
is another manifestation of the same problem.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.


Re: notmuch - Hook return code: 134

2013-08-08 Thread Marcelo Laia
Dear Suvayu Ali,

Yes, I sent it to notmuch list. But, no answer yet!

Yes, I use notmuch with offlineimap. Here is the code:

~/.offlineimaprc
(...)
postsynchook = notmuch new
(...)

It have worked good until 20 or 30 days a go!

Yes, I have opened the raw file and it was ok. No problem with it.

Thank you!

-- 
Marcelo