unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Damien Cassou <damien@cassou.me>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] Add Emacs' imenu support in notmuch-show and notmuch-search
Date: Sun, 11 Jun 2017 11:28:23 +0200	[thread overview]
Message-ID: <87bmpuq3ew.fsf@cassou.me> (raw)
In-Reply-To: <87zidfb9bp.fsf@tethera.net>

[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]

David Bremner <david@tethera.net> writes:
> I am indeed using the default. I think you forgot the screen 
> shot. 


indeed. Attached to this email.


>> I can still get rid of indentation if you confirm you don't 
>> want  it. 
> 
> I think so, although to be honest I never tried imenu before 
> testing your patches, perhaps we should wait for other opinions. 


I advise you to install counsel at least for that (I don't use it 
for anything else).


>> You also say the information on the header line is not very 
>> helpful. Do you have any other suggestion? I'm open to trying 
>> several different alternatives and see what people prefer. 
> 
> I guess I don't really understand how the matching is supposed 
> to work. If the user has to type from the beginning of the index 
> string, then I guess putting either the date or the subject 
> first might be helpful.


That depends on the frontend. For example, with counsel-imenu, I 
can type "attach" to filter by emails in the thread with the 
attachment tag.


> It's probably true that there is no one good order for all 
> threads. Some threads change subject often, others author, and 
> one I'm looking at right now has 25 messages with two authors 
> and one subject. 


-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

[-- Attachment #2: Screenshot from 2017-06-10 22-24-26.png --]
[-- Type: image/png, Size: 297873 bytes --]

  reply	other threads:[~2017-06-11  9:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 15:25 Add support for imenu Damien Cassou
2017-05-23 16:45 ` Jani Nikula
2017-05-24  6:17   ` Damien Cassou
2017-05-24  6:14 ` [PATCH] Add Emacs' imenu support in notmuch-show and notmuch-search Damien Cassou
2017-06-10  0:12   ` David Bremner
2017-06-10 21:49     ` Damien Cassou
2017-06-11  1:29       ` David Bremner
2017-06-11  9:28         ` Damien Cassou [this message]
2017-06-11 11:00           ` David Bremner
2017-06-12 13:30             ` Damien Cassou
2017-06-12 13:30               ` [PATCH] Add Emacs' imenu support in notmuch-show and notmuch-search Damien Cassou
2017-06-14  1:22               ` David Bremner
2017-06-14  9:44                 ` Re: David Bremner
2017-06-14  9:54                   ` Re: Damien Cassou
2017-06-14 11:06                     ` imenu support David Bremner

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=87bmpuq3ew.fsf@cassou.me \
    --to=damien@cassou.me \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    /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).