From: David Bremner <david@tethera.net>
To: Olaf TNSB <still.another.person@gmail.com>,
Steven Allen <steven@stebalien.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Add (extracted) attachment text to the search index?
Date: Wed, 01 Mar 2017 20:41:51 -0400 [thread overview]
Message-ID: <87varscxww.fsf@tethera.net> (raw)
In-Reply-To: <CABDMPboUZ1iPCf6YzaMjV-c7AamyQCEHp0R-0q5DmBDTki6HeA@mail.gmail.com>
Olaf TNSB <still.another.person@gmail.com> writes:
> On Thu, Mar 2, 2017 at 4:55 AM, Steven Allen <steven@stebalien.com> wrote:
>>
>>
>> David Bremner <david@tethera.net> writes:
>> > This would require some modifications of notmuch. Either modifying
>> > lib/index.cc to add the terms at indexing (notmuch new/insert) time, or
>> > providing some way of adding the terms later. The former actually sounds
>> > simpler to me.
>>
>> To do this correctly, you'd want to be able to run an external text
>> extraction tool (for PDFs, word documents, etc.) so I think the latter
>> would be better in the long run (it would allow the user to index
>> attachments in the hooks).
>
> (As a non-dev...) I agree. The ability to add (and delete!) content
> post-insert sounds more desirable. I don't want to have to re-index all my
> email as the next version of <horrible-binary-object>-to-text gets
> released. I'd like to be able to (search-for-attachment)-(delete)-(re-add).
There has been some patches (related to encrypted email), that reindex
individual messages. So that would be a clean fix for that. I haven't
really thought about reindexing parts of messages, which is what seems
to be the proposal here.
d
next prev parent reply other threads:[~2017-03-02 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 2:58 Add (extracted) attachment text to the search index? Olaf TNSB
2017-03-01 11:34 ` David Bremner
2017-03-01 17:55 ` Steven Allen
2017-03-01 22:45 ` Olaf TNSB
2017-03-02 0:41 ` David Bremner [this message]
2017-03-02 0:55 ` Olaf TNSB
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87varscxww.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=steven@stebalien.com \
--cc=still.another.person@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).