unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Ian Main <imain@stemwinder.org>
To: Sepp Tannhuber <sepp.tannhuber@yahoo.de>,
	Sepp Tannhuber <sepp.tannhuber@yahoo.de>,
	"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Looking for the perfect mail client
Date: Fri, 24 Oct 2014 14:32:59 -0700	[thread overview]
Message-ID: <544ac58b65db6_444b78fe8863@ovo.mains.priv.notmuch> (raw)
In-Reply-To: <1414176577.35150.YahooMailNeo@web172705.mail.ir2.yahoo.com>

Sepp Tannhuber wrote:
> Ian Main <imain@stemwinder.org> schrieb am 18:02 Freitag, 24.Oktober 2014:
> 
> > Interesting, good feedback.  Is it the usage that is difficult or setup?
> Installation was not a problem for me although the files »notmuch.vim« and 
> »notmuch.txt« were not found by »make install« for some reason. So I linked
> them into the notmuch-vim directory. After that »make install« succeeded.
> But the main obstacle is that new users must find by trial and error that
> they must type »s« to search, »t« to tag files and so on. It would be very
> useful to list all the key bindings and configuration options.
> I still don't know how to compose a new message.

https://github.com/imain/notmuch-vim/blob/master/doc/notmuch.txt

Look at the 'MAPPINGS' section.  I think a tutorial might be good though.

> > Well like any other text based client it uses a text dump of a links or such (I
> > forget which one).
> I think »elinks --dump«
> 
> > We have great support for web browser viewing of the email
> > though if that isn't good enough.
> Yes, it's 2014. ;-)

Time flies!!

> > Let me know if you have suggestions on where it's lacking. 
> Okay, thank you so far.

Thanks!

  reply	other threads:[~2014-10-24 21:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 10:02 Looking for the perfect mail client Sepp Tannhuber
2014-10-21 10:42 ` Simon Chopin
2014-10-21 13:53   ` Suvayu Ali
2015-03-30 14:27   ` Patrick Totzke
2014-10-21 11:18 ` Gaute Hope
2014-10-22  6:46   ` Sepp Tannhuber
2014-10-22  6:57     ` Gaute Hope
2014-10-22 12:23       ` Sepp Tannhuber
2014-10-22 13:49         ` Gaute Hope
2014-10-22 14:48           ` Sepp Tannhuber
2014-10-22 15:30             ` Gaute Hope
2014-10-22 16:03             ` Gaute Hope
2014-10-22 16:52               ` Sepp Tannhuber
2014-10-22 17:38                 ` Peter Feigl
2014-10-23 10:47                   ` Sepp Tannhuber
2014-10-23 10:57                     ` Justus Winter
2014-10-23 11:23                       ` Franz Fellner
2014-10-23 10:58                     ` Franz Fellner
2014-10-23 21:13                       ` Sepp Tannhuber
2014-10-24  4:28 ` Ian Main
2014-10-24  8:58   ` Sepp Tannhuber
2014-10-24 16:02     ` Ian Main
2014-10-24 18:49       ` Sepp Tannhuber
2014-10-24 21:32         ` Ian Main [this message]
2014-10-25  8:50           ` Sepp Tannhuber
2014-10-27 18:41             ` Ian Main
2014-10-28  0:28             ` 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=544ac58b65db6_444b78fe8863@ovo.mains.priv.notmuch \
    --to=imain@stemwinder.org \
    --cc=notmuch@notmuchmail.org \
    --cc=sepp.tannhuber@yahoo.de \
    /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).