From: Ian Main <imain@redhat.com>
To: Franz Fellner <alpine.art.de@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch vim patches
Date: Thu, 16 Oct 2014 15:30:11 -0700 [thread overview]
Message-ID: <544046f358233_2c291569e8c76@ovo.mains.priv.notmuch> (raw)
In-Reply-To: <20141016144109.GB3471@TP_L520.localdomain>
Franz Fellner wrote:
>
>
> > I'm starting to realize that I could default to using 'enter' to both
> > open URI's and view attachments. Any other ideas welcome.
>
> - make some of the functions public so users can bind them to keys they
> want
> - introduce show_[prev,next]_unread_msg, probably factor out
> "show_scroll_to_msg()" and implement prev/next msg with that?
You know I was just reading a thread and hit 'a' to archive a message
within the thread and for some reason it hung for a few seconds.. but it
made me think we should be able to press 'a' (or whatever archive key)
and have it archive and move to next unread. That seems to me to be a
good behavior with a natural flow.
Ian
> - use proper buffers instead of Scratch buffers, so BufExplorer also
> shows notmuch-vim buffers
> - folding of messages; add option to fold read messages by default.
>
> I think I can implement the second point (if you not already did
> that).
> I also looked into folding, but my knowledge of all the possiblities is
> not that good (manual folding markers look ugly, don't know if/how 'syntax'
> will work; and IMHO the user's shortcuts for folding should still work).
>
> Franz
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2014-10-16 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 19:47 notmuch vim patches Ian Main
2014-10-16 12:41 ` Franz Fellner
2014-10-16 19:22 ` Ian Main
2014-10-16 22:30 ` Ian Main [this message]
2014-10-17 16:35 ` Franz Fellner
2014-10-17 17:29 ` Ian Main
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=544046f358233_2c291569e8c76@ovo.mains.priv.notmuch \
--to=imain@redhat.com \
--cc=alpine.art.de@gmail.com \
--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).