unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Johannes Larsen <mail@johslarsen.net>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: announce: my fork of alot
Date: Sun, 16 May 2021 19:23:54 -0500	[thread overview]
Message-ID: <CAMP44s3dPnPt8=CkPZgQiSNt8QEkZk1qkP1xPYu6w=faVTkAYA@mail.gmail.com> (raw)
In-Reply-To: <162120681380.417438.5199919064593359694@hue.johslarsen.net>

On Sun, May 16, 2021 at 6:13 PM Johannes Larsen <mail@johslarsen.net> wrote:
>
> 2021-05-17 00:32:09, Felipe Contreras <felipe.contreras@gmail.com> wrote:
> > Have you tried notmuch-vim?
>
> Yes, I have tried it, but I did not like its thread view though. Maybe
> that mbox-like view of all messages in a thread works fine if there few
> messages per thread, but I interact with a lot of mailing-lists where it
> is not uncommon with 20+ messages in a thread, and then I kind of need
> some sort of hierarchic view of messages to keep my bearings.

I hear you.

I do interact with such mailing lists, but _usually_ I only deal with
the new messages on the thread, not *all* messages. In that scenario
the thread-view works fine.

However, when I'm looking at old threads that I neglected, then it is
a bit cumbersome. I agree with you.

I'm not unfamiliar with big threads: my last big thread is of
yesterday: 45 messages [1].

I do have some experimental code in which I started rewriting
notmuch-vim from scratch, and one of the first thoughts I had was: why
not use a hierarchical view? In fact I don't think it would be that
difficult; we could use vim folds in order to expand/contract
subthreads.

There's a lot of other things to do first though.

> Also, I have been using vim as my primary editor/IDE for decades, so I
> am kind of scared of bundling even more features into that setup. When I
> am dealing with dozens of plugins and thousands of lines with vimscript
> configuration already, then it is not so uncommon for some of them to
> interact badly with each other.

Sure, but in modern versions of vim (since 7.0?) there is an autoload
feature [2]. With that feature nothing actually happens unless you (or
some code) calls that function. There's absolutely no way autoload
code can interact with another plugin if you have not issued a
:NotMuch command specifically.

Granted: the current version of notmuch-vim doesn't use this autoload
feature, although I suspect much of the code normally is hidden from
view (until you call :NotMuch). I'm not entirely sure, and it's better
to make sure using autoload.

This is something I could do in probably less than 30 minutes, if it's
truly a blocker for you... But again... I think there's a lot of
things to do first; that's why I haven't done it yet.

Of course, any issues you find you are more than welcome to report on
the issue tracker.

Cheers.

[1] https://lore.kernel.org/git/20210511222754.417371-1-felipe.contreras@gmail.com/
[2] https://vimhelp.org/eval.txt.html#autoload

-- 
Felipe Contreras

  reply	other threads:[~2021-05-17  0:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 10:19 announce: my fork of alot Anton Khirnov
2021-05-16 11:15 ` Michael J Gruber
2021-05-16 14:42   ` Anton Khirnov
2021-05-16 15:41   ` Patrick Totzke
2021-05-16 17:47     ` Anton Khirnov
2021-05-16 18:23       ` Patrick Totzke
2021-05-17  7:08         ` Patrick Totzke
2021-05-17  7:33           ` Michael J Gruber
2021-05-17  7:54             ` Michael J Gruber
2021-05-17  8:25             ` Anton Khirnov
2021-05-17  8:19           ` Anton Khirnov
2021-05-17  8:28             ` Patrick Totzke
2021-05-17  8:39               ` Anton Khirnov
2021-05-17  9:02         ` Anton Khirnov
2021-05-16 22:09 ` Johannes Larsen
2021-05-16 22:32   ` Felipe Contreras
2021-05-16 23:13     ` Johannes Larsen
2021-05-17  0:23       ` Felipe Contreras [this message]
2021-05-17  8:54   ` Anton Khirnov
2021-05-17 12:32     ` Johannes Larsen
2021-05-17 12:55       ` Anton Khirnov
2021-05-17 19:03         ` Johannes Larsen

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='CAMP44s3dPnPt8=CkPZgQiSNt8QEkZk1qkP1xPYu6w=faVTkAYA@mail.gmail.com' \
    --to=felipe.contreras@gmail.com \
    --cc=mail@johslarsen.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).