From: Franz Fellner <alpine.art.de@gmail.com>
To: Ian Main <imain@redhat.com>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch vim patches
Date: Fri, 17 Oct 2014 18:35:38 +0200 [thread overview]
Message-ID: <20141017183538.GI20696@TP_L520.localdomain> (raw)
In-Reply-To: <544046f358233_2c291569e8c76@ovo.mains.priv.notmuch>
On Thu, 16 Oct 2014 15:30:11 -0700, Ian Main <imain@redhat.com> wrote:
> 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.
Yes, sounds good.
Today I thought of a more generic approach:
pass a query that a message should match.
:notmuch-show-next-message tag:unread # go to the next unread
message in thread
:notmuch-show-next-message from:"Ian Main" # got to the next
message in thread sent by "Ian Main"
...
The user then can map keys to custom commands.
Good or too generic?
Furthermore I thought of rearranging the sources:
- Put files in Vundle/*-compatible dirs, would simplify development.
(Currently I have several files symlinked from notmuch-src into .vim)
- Put the "heavy" ruby code into its own file. Today I got an error I
could not deal with because line numbers did not match. Also I read
about the possibility that the ruby interpreter might optimize only
seperate files. This could lead to better performance.
Franz
next prev parent reply other threads:[~2014-10-17 16:35 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
2014-10-17 16:35 ` Franz Fellner [this message]
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=20141017183538.GI20696@TP_L520.localdomain \
--to=alpine.art.de@gmail.com \
--cc=imain@redhat.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).