From: Johannes Larsen <mail@johslarsen.net>
To: Anton Khirnov <anton@khirnov.net>, notmuch@notmuchmail.org
Subject: Re: announce: my fork of alot
Date: Mon, 17 May 2021 14:32:12 +0200 [thread overview]
Message-ID: <162125473215.485346.8032242148529876406@hue.johslarsen.net> (raw)
In-Reply-To: <162124164914.29687.9843712933198261750@lain.red.khirnov.net>
[-- Attachment #1.1: Type: text/plain, Size: 1792 bytes --]
2021-05-17 10:54:09, Anton Khirnov <anton@khirnov.net> wrote:
> Here's my current roadmap:
Lots if interesting features/fixes!
> - commands themselves should probably be synchronous [...] to
> prevent races where a later command conflicts with an earlier one
Yeah, that race condition is a annoyance. Quitting alot helps at least.
> * atomic complex retagging commands
> e.g. add+remove in the same command
sup had something like that. The retag operation when you had multiple
messages used +/- prefixes to add/remove tags from those messages whilst
leaving other tags on them untouched. I do not know if this was atomic,
but at least it was idempotent.
> * running external commands in a separate tmux pane/terminal
That is a good idea. Quitting the editor and using ";" to temporary
switching to another buffer (e.g. reading something elsewhere in a
thread) works, but is a hassle. [vim-dispatch] does something similar
for e.g. external compilation/tests from the editor, so maybe they
figured out some indicator for when tmux panes/windows completes.
[vim-dispath]: https://github.com/tpope/vim-dispatch
> - search+highlight
Yeah, I am still automatically trying "/" in alot (the hotkey that
searched like that in sup) to search in the buffer.
> - properly handle focus switching between the thread tree and message body
Mapping something to "move toggle" worked okay to switch focus between
these panes. Was kind of a surprise when scrolling within a message body
scrolled to the next message though.
> - pipeto refactoring
Yeah, as it is now I only use it with less to read the raw body. I think
pipeto based on a selected body/attachment for instance would be useful.
--
johs (Johannes Larsen), (+47) 41435451
[-- Attachment #1.2: signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEpTer3kqGU3pr882G07zxebJvqyYFAmCiYkwACgkQ07zxebJv
qyZZiw//fK3+u3WnYSbcuAv7zhFLudEkm4GDMMR83bkegUhevhcjlPXSVSqh1NIj
Tv4Vvh4lwl5fZyLnx+YON40TBzfuPOrMX2nfjOw8Uy5Qkw48lDhfTTfBTasuOWKG
8pEtFPwRIW4eYJMc8PjY9blqZ6WkcdAeZVl0mFrmT1JqZ3tL7z8njksrpSjkH416
0Wk6E3Ok7hSGcmmzgkvQP0i8oH8+QAu52pM8RCILTLqsBt9M8/8W7ktAT6VlGCkI
HLpkCEotF9jlrmEvQ0OYUZ1QkrOdcEAYiR6yswhF/gJ/dC+NQtVVuZvasSFK4cDe
UZHTyIFkxIY7KNYuEXggECqYoHIO/Tgo1imii8ep/RTSsUhvQ0LtcbBtOH2IyOBi
YRT3eVOaMsh7SPjDihrajGMR9wi5O/Cc/FNqQUKQTov6l7vG5MXM+ZyRdWhnrRnn
5wrO/6wvfsJ0EmPrKsOKCh2OSNLgXZ/kKh5TJry5DiwE4sCNdnZyQI3qbQdqATR4
2xbxrmgEVofg5of/kH4SETP5P/p62Sxthf21U9kKGZJp/c/fHb1caBAYqQH42bjO
lHkxe0v9d5bzh+CnbZdnnQRIZ4OSK7plbJSHLWgXnggxKugyVSDi9N2Oq6yT8NjO
6m8p0xn5Qb8zljsZomhiajKU4+tL30CC/784l1TI3+ySGL/tvhY=
=w//Z
-----END PGP SIGNATURE-----
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2021-05-17 12:32 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
2021-05-17 8:54 ` Anton Khirnov
2021-05-17 12:32 ` Johannes Larsen [this message]
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=162125473215.485346.8032242148529876406@hue.johslarsen.net \
--to=mail@johslarsen.net \
--cc=anton@khirnov.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).