From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: lei interactive TUIs (ncurses/vim/emacs)
Date: Fri, 22 Sep 2023 20:33:53 +0000 [thread overview]
Message-ID: <20230922203353.M780211@dcvr> (raw)
I hardly have any experience in this area; but automatic
end-to-end tests for ncurses and other TUI stuff seems
like a huge pain...
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...
While I use vim[1], I've always kept my vim decoupled from Perl
(or Lua, Python, Ruby, TCL, etc) and rather tie stuff together
with pipes. IOW, I'm happy my editor can run arbitrary shell
commands; but don't want stuff linked into my editor (since more
code is usually more fragile).
So, any thoughts on this matter?
Anybody willing to maintain an lei TUI for emacs?
I might give a vim TUI a shot...
But writing and testing a FUSE FS is much more natural...
[1] My choice to use vi/vim is merely because it's the most
widely-installed editor on random systems I ssh into.
It also mostly works the same after a few decades w/o
needing UI changes; same goes for Perl.
next reply other threads:[~2023-09-22 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 20:33 Eric Wong [this message]
2023-11-09 4:14 ` lei interactive TUIs (ncurses/vim/emacs) Kyle Meyer
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=20230922203353.M780211@dcvr \
--to=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).