From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: lei interactive TUIs (ncurses/vim/emacs)
Date: Wed, 08 Nov 2023 23:14:37 -0500 [thread overview]
Message-ID: <87il6b36mq.fsf@kyleam.com> (raw)
In-Reply-To: <20230922203353.M780211@dcvr>
[ I missed this (just saw it mentioned in a recent message). ]
Eric Wong writes:
> I've also noticed vim has scripting abilities (like Emacs?) and
> notmuch bundles a vim extension we can take inspiration from.
> Perhaps we could bundle vim and Emacs extensions for lei, too...
[...]
> So, any thoughts on this matter?
>
> Anybody willing to maintain an lei TUI for emacs?
As part of piem [1], I've done some work on an Emacs interface for lei,
in particular `lei q'. It's pretty bare-bones (been meaning to get back
to it...), but it's functional for searching and basic viewing.
[1]: https://git.kyleam.com/piem/about/
prev parent reply other threads:[~2023-11-09 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 20:33 lei interactive TUIs (ncurses/vim/emacs) Eric Wong
2023-11-09 4:14 ` Kyle Meyer [this message]
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il6b36mq.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.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.
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).