The character set is chosen to be suitable for pathnames, and the same
as that used by contrib/nmbug
[With additions by Jani Nikula]
---
util/Makefile.local |2 +-
util/hex-escape.c | 168 +++
util/hex-escape.h | 41 +
3 files
This obsoletes the series
id:"1344190393-22497-1-git-send-email-da...@tethera.net"
[Patch v2 1/6] hex-escape: (en|de)code strings to/from restricted
[Patch v2 2/6] test/hex-xcode: new test binary
[Patch v2 3/6] test/hex-escaping: new test for hex escaping routines
In order to avoid the prob
Initial use case is testing dump and restore, so we only have
message-ids and tags.
The message ID's are nothing like RFC compliant, but it doesn't seem
any harder to roundtrip random UTF-8 strings than RFC-compliant ones.
Tags are UTF-8, even though notmuch is in principle more generous than
tha
Initially, provide a way to create "stub" messages in the notmuch
database without corresponding files. This is essentially cut and
paste from lib/database.cc. This is a seperate file since we don't
want to export these symbols from libnotmuch or bloat the library with
non-exported code.
---
test
This program is used both as a test-bed/unit-tester for
../util/hex-escape.c, and also as a utility in future tests of dump
and restore.
---
test/.gitignore |1 +
test/Makefile.local | 10 -
test/basic |2 +-
test/hex-xcode.c| 103 +++
We demonstrate the current notmuch restore parser being confused by
message-id's and tags containing non alpha numeric characters
(particularly space and parentheses are problematic because they are
not escaped by notmuch dump).
We save the files as hex escaped on disk so that the output from the
These are more like unit tests, to (try to) make sure the library
functionality is working before building more complicated things on
top of it.
---
test/hex-escaping | 26 ++
test/notmuch-test |1 +
2 files changed, 27 insertions(+)
create mode 100755 test/hex-escap
Michal Nazarewicz writes:
>
> $ dpkg -l |grep xapian
> ii apt-xapian-index 0.25ubuntu2 maintenance tools for a Xapian index
> of Debi
> ii libxapian-dev 1.0.18-1 Development files for Xapian search
> engine l
> ii libxapian15 1.0.18-1 Search engine library
Hi
On Tue, 14 Aug 2012 07:25:00 +0200, David Froger wrote:
>
> So I think I understand my problem. The reason is that in put in my
> .config/bower/bower.conf:
>
> notmuch_deliver=/bin/true
>
> To solve the problem of "duplicated sent email" with Gmail:
> http://support.google.com/mail/bin/answer.p
> Michal Nazarewicz writes:
>> $ dpkg -l |grep xapian
>> ii apt-xapian-index 0.25ubuntu2 maintenance tools for a Xapian index
>> of Debi
>> ii libxapian-dev 1.0.18-1 Development files for Xapian search
>> engine l
>> ii libxapian15 1.0.18-1 Search engine librar
On Tue, 14 Aug 2012, Michal Nazarewicz wrote:
> Yeah, it seems that INSTALL claims “Notmuch will work best with Xapian
> 1.0.18 (or later) or Xapian 1.1.4 (or later)”, which doesn't seem to be
> the case.
>
> On top of that, configure does not seem to even check the version
> number.
Someone(tm)
> > - fuse zip stores all changes in memory until unmounted
> > - fuse zip (and libzip for that matter) creates new temporary file when
> >updating archive, which takes considerable time when the archive is
> >very big.
>
> This isn't much of a hastle if you have maildir per time period
On Tue, Aug 14, 2012 at 7:04 PM, Vladimir Marek
wrote:
>> > - fuse zip stores all changes in memory until unmounted
>> > - fuse zip (and libzip for that matter) creates new temporary file when
>> >updating archive, which takes considerable time when the archive is
>> >very big.
>>
>> Thi
> >> > - fuse zip stores all changes in memory until unmounted
> >> > - fuse zip (and libzip for that matter) creates new temporary file when
> >> >updating archive, which takes considerable time when the archive is
> >> >very big.
> >>
> >> This isn't much of a hastle if you have maildir
On Tue, Aug 14, 2012 at 7:50 PM, Vladimir Marek
wrote:
>> On the other hand I strongly sustain having a more optimized
>> backend for emails, especially for such cases. For example a
>> BerkeleyDB would perfectly fit such a use case, especially if we store
>> the body and the headers in separa
Quoting Jani Nikula (2012-08-14 14:57:13)
> > Is close() really required though? The comment justifies it saying
> > that:
> >
> > Many Xapian objects hold references to the database, so merely
> > deleting the database may not suffice to close it. Thus, we
> > explicitly close
On Tue, Aug 14, 2012 at 7:05 PM, Ciprian Dorin Craciun
wrote:
> I proposed -- better said queried if possible or at least wanted
> -- to have an internal interface (SPI) that any mail store would have
> to implement in order to be indexed and used by notmuch. I guess the
> interface would be q
On Tue, Aug 14, 2012 at 8:11 PM, Christophe-Marie Duquesne wrote:
> one could complete this work with an
> interface to couchdb for offlineimap
*I meant for notmuch
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo
Vladimir Marek writes:
> Well, if your granularity will be one archive per year of mail, it
> should not be that bad ...
Except for someone like Keith, who has all his email since sometime in
the 80s or something insane like that :)
--
Stewart Smith
pgpqbDWUxd3Kw.pgp
Description: PGP signatur
ourse, the list of mounted file systems could get insane
depending on granularity I guess...
--
Stewart Smith
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notm
On Sun, 12 Aug 2012 21:33:39 +0100, Patrick Totzke
wrote:
> Quoting David Froger (2012-08-12 16:53:43)
> > > > 3. Would it be possible to have the feature 'kill a thread' like Sup
> > > > have? (see
> > > > http://sup.rubyforge.org/README.txt).
> > >
> > > I haven't needed such a feature so I d
> This is the command to save drafts:
>
> notmuch-deliver Drafts --tag=draft \
> --remove-tag=inbox --remove-tag=unread < message_file
>
> Does it work if you run it manually? Just make a dummy message_file
> with Date:, From:, To:, Subject: headers and a body.
The manual command work
Michal Nazarewicz writes:
>
> $ dpkg -l |grep xapian
> ii apt-xapian-index 0.25ubuntu2 maintenance tools for a Xapian index
> of Debi
> ii libxapian-dev 1.0.18-1 Development files for Xapian search
> engine l
> ii libxapian15 1.0.18-1 Search engine library
Hi
On Tue, 14 Aug 2012 07:25:00 +0200, David Froger
wrote:
>
> So I think I understand my problem. The reason is that in put in my
> .config/bower/bower.conf:
>
> notmuch_deliver=/bin/true
>
> To solve the problem of "duplicated sent email" with Gmail:
> http://support.google.com/mail/bin/answer.
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20120814/5bd3fd0d/attachment.pgp>
On Tue, 14 Aug 2012, Michal Nazarewicz wrote:
> Yeah, it seems that INSTALL claims ?Notmuch will work best with Xapian
> 1.0.18 (or later) or Xapian 1.1.4 (or later)?, which doesn't seem to be
> the case.
>
> On top of that, configure does not seem to even check the version
> number.
Someone(tm)
> > - fuse zip stores all changes in memory until unmounted
> > - fuse zip (and libzip for that matter) creates new temporary file when
> >updating archive, which takes considerable time when the archive is
> >very big.
>
> This isn't much of a hastle if you have maildir per time period
On Tue, Aug 14, 2012 at 7:04 PM, Vladimir Marek
wrote:
>> > - fuse zip stores all changes in memory until unmounted
>> > - fuse zip (and libzip for that matter) creates new temporary file when
>> >updating archive, which takes considerable time when the archive is
>> >very big.
>>
>> Thi
> >> > - fuse zip stores all changes in memory until unmounted
> >> > - fuse zip (and libzip for that matter) creates new temporary file when
> >> >updating archive, which takes considerable time when the archive is
> >> >very big.
> >>
> >> This isn't much of a hastle if you have maildir
On Tue, Aug 14, 2012 at 7:50 PM, Vladimir Marek
wrote:
>> On the other hand I strongly sustain having a more optimized
>> backend for emails, especially for such cases. For example a
>> BerkeleyDB would perfectly fit such a use case, especially if we store
>> the body and the headers in separa
Quoting Jani Nikula (2012-08-14 14:57:13)
> > Is close() really required though? The comment justifies it saying
> > that:
> >
> > Many Xapian objects hold references to the database, so merely
> > deleting the database may not suffice to close it. Thus, we
> > explicitly close
On Tue, Aug 14, 2012 at 7:05 PM, Ciprian Dorin Craciun
wrote:
> I proposed -- better said queried if possible or at least wanted
> -- to have an internal interface (SPI) that any mail store would have
> to implement in order to be indexed and used by notmuch. I guess the
> interface would be q
On Tue, Aug 14, 2012 at 8:11 PM, Christophe-Marie Duquesne
wrote:
> one could complete this work with an
> interface to couchdb for offlineimap
*I meant for notmuch
33 matches
Mail list logo
