From: Adrian Perez de Castro <aperez@igalia.com>
To: notmuch@notmuchmail.org
Subject: Fw: Introducing myself
Date: Thu, 19 Nov 2009 01:32:30 +0100 [thread overview]
Message-ID: <20091119013230.5a9c29e5@hikari> (raw)
[-- Attachment #1: Type: text/plain, Size: 2458 bytes --]
(Re-injecting this one in the list... it was my fault in reality because I
sent two copies, one to the list and another to Carl, so he replied to me
directly. It would have been enough to send my mail to the list -- I am
sorry a lot for the noise)
Begin forwarded message:
Date: Thu, 19 Nov 2009 00:58:38 +0100
From: Carl Worth <cworth@cworth.org>
To: Adrian Perez de Castro <aperez@igalia.com>
Subject: Re: [notmuch] Introducing myself
On Wed, 18 Nov 2009 16:47:06 +0100, Adrian Perez de Castro
<aperez@igalia.com> wrote:
> On Wed, 18 Nov 2009 03:15:31 -0800, Carl wrote:
>
> I tried the "notmuch.el" Emacs mode, and have just installed Emacs in
> order to be able to try it out. As I have been using Vim for the last ~9
> years, probably that was the reason why I found it not very comfortable.
Wow, you're brave to give it a shot. And I'm glad that you were able to
work your way through it.
> I showed the thing to my work mates this morning and most of them said
> that they would like to have Mutt-like keybindings *with* Not Much's
> search and tagging running behind it.
Any long-time mutt users want to suggest keybindings? I've mostly been
making stuff up as I go (with some influence from sup), but I think it's
early enough that I could still re-train my muscles. Get your votes in
now for your favorite keybindings.
> I also think it would be great to have a curses-based UI, so this may
> be a good opportunity to start doing some serious coding with it in my
> spare time.
Sounds great. I would feel just fine seeing lots of interfaces built up
around the notmuch search and tagging. I do hope people doing custom
interfaces will consider implementing some of the things that I happen
to consider part of the "notmuch experience", (viewing an entire, nested
thread at once with citations/signatures elided---this feature comes
exactly from sup; and my magic space-bar for reading lots of mail with
only one key---though the most important part here is to not archive a
message until it is paged *off* the screen---as opposed to many emailers
that mark a message as "read" as soon as any of the message appears on
the screen).
Of course, if you're doing your own interface, then you get to do
whatever you want. But I hope you might at least consider those ideas.
Happy hacking!
-Carl
--
Adrian Perez de Castro <aperez@igalia.com>
Igalia - Free Software Engineering
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-11-19 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 0:32 Adrian Perez de Castro [this message]
2009-11-19 0:57 ` Fw: Introducing myself Adrian Perez de Castro
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=20091119013230.5a9c29e5@hikari \
--to=aperez@igalia.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).