From: Olaf TNSB <still.another.person@gmail.com>
To: Steven Allen <steven@stebalien.com>
Cc: notmuch@notmuchmail.org, David Bremner <david@tethera.net>
Subject: Re: Add (extracted) attachment text to the search index?
Date: Thu, 2 Mar 2017 09:45:18 +1100 [thread overview]
Message-ID: <CABDMPboUZ1iPCf6YzaMjV-c7AamyQCEHp0R-0q5DmBDTki6HeA@mail.gmail.com> (raw)
In-Reply-To: <877f48lw4s.fsf@bistromath>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
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).
I was thinking a really hacky solution would be fake up a new email with
the same headers but body being the attachment text, doing a notmuch
new/insert and then replacing the file on disk of the new email with a link
to the original message (not sure if that will trigger notmuch new, I don't
think so). Doesn't feel robust, but...
What do ya reckon?
[-- Attachment #2: Type: text/html, Size: 1564 bytes --]
next prev parent reply other threads:[~2017-03-01 22:45 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 [this message]
2017-03-02 0:41 ` David Bremner
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=CABDMPboUZ1iPCf6YzaMjV-c7AamyQCEHp0R-0q5DmBDTki6HeA@mail.gmail.com \
--to=still.another.person@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=steven@stebalien.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).