From: Anton Khirnov <anton@khirnov.net>
To: Johannes Larsen <mail@johslarsen.net>, notmuch@notmuchmail.org
Subject: Re: announce: my fork of alot
Date: Mon, 17 May 2021 14:55:57 +0200 [thread overview]
Message-ID: <162125615708.29687.4069557858592320237@lain.red.khirnov.net> (raw)
In-Reply-To: <162125473215.485346.8032242148529876406@hue.johslarsen.net>
Quoting Johannes Larsen (2021-05-17 14:32:12)
> 2021-05-17 10:54:09, Anton Khirnov <anton@khirnov.net> wrote:
> > Here's my current roadmap:
>
> Lots if interesting features/fixes!
Of course keep in mind that it's largely a wishlist, so don't expect
these to be done
- at all
- any time soon
- in this order
> > - 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.
Did you actually hit it? I don't think I actually saw it happen more
than a couple times, but even so I'd like to fix it before adding more
async.
>
> > * 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
Seems that just periodically polls the pane list, which is suboptimal.
Seems tmux has a 'wait-for' command that could be useful for
implementing this.
> > - 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.
Yeah, that's a known bug and I'm sure I'll get to fixing it SomeDay(tm),
since it's rather annoying.
--
Anton Khirnov
next prev parent reply other threads:[~2021-05-17 12:56 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
2021-05-17 12:55 ` Anton Khirnov [this message]
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=162125615708.29687.4069557858592320237@lain.red.khirnov.net \
--to=anton@khirnov.net \
--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).