From: lego12239@yandex.ru
To: 9fans@9fans.net
Subject: Re: [OBORONA-SPAM] [9fans] Next Generation Acme
Date: Tue, 13 May 2025 16:24:57 +0300 [thread overview]
Message-ID: <aCNIKSuLSAjQUxyF@legohost> (raw)
In-Reply-To: <CAEAzY38=dJ0URuyOxP9hSd54LCXkBmnNBLmOZtb+yXh9P277Zg@mail.gmail.com>
On Tue, May 13, 2025 at 02:20:56PM +0200, Aram Hăvărneanu wrote:
> Here are some of my ideas for the next generation of Acme. Please
> disagree or add more.
Hi. My imho.
> 1. Keep the Acme UI, but add rows, not just columns. Potentially
> make each window a full multiplexor (like rio(1), not 100% sure
> about this).
The today common monitor ratio is 16:9. Thus, creating a some row screen
wide just makes vertical space for other window is too small. As for me, i
never needed this :-).
> 5. Add enough ANSI terminal sequences support to win(1) such that
> workarounds are no longer necessary for common CLI software (git(1),
> grep(2), etc).
This might be good.
> 6. Replace structural regular expression with something based on
> Tree-sitter, but with an actual usable syntax.
Please, no replacing. Structural regexp should stay. Otherwise we
break many scripts.
> 12. Multiple window support, in the sense of multiple operating
> system windows.
Do you mean multiple instances of acme? Multiple windows of one
instance seems inconvenient.
> 14. Elastic tab support, or some better way of dealing with tabular
> data.
What do you mean?
> 15. A better way of dealing with resize, right now acme does really
> bad when moving from a big monitor to a laptop because it preserves
> layout. I'd like a way to globally set layout independent of Dump.
Work with layout between different resolutions is hard. I also run
the same acme instance on different screens (external big and laptop).
But if you save sizes of windows in percents, you got on laptop too small
windows in characters units. I mean, i want all windows be 80 chars wide.
And on big external monitor(16:9) i have 2 such cols with big font. But
on small laptop screen this session can't have 2 80 chars wide cols with
the same font. In this case, we must choose another font. But i dont'
want smaller font :-). This hard to solve automatically, i think.
> 16. No settings, no options, no themes, no syntax highlighting, no
> keyboard based interface (the mouse is king).
As for me, it would be better to have some config, because more features -
more options. And even now my alias for acme looks like this:
alias acme='PATH=~/bin/acme:$PATH acme -a -f /mnt/font/DejaVuSerif/15a/font -F /mnt/font/LiberationMono/15a/font'
On the other side, the alias is working and this is not trouble :-).
But some keyboard shortcuts would be useful. Something for editing adjacent
lines like:
- go to line up/down
- go to word forward/backward
--
Олег Неманов (Oleg Nemanov)
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4f1a2098b1e1c854-M4e4ca477d145bf00b170e74d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2025-05-13 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 12:20 Aram Hăvărneanu
2025-05-13 12:51 ` Mark van Atten
2025-05-13 13:51 ` Aram Hăvărneanu
2025-05-13 13:24 ` lego12239 [this message]
2025-05-13 14:16 ` [OBORONA-SPAM] " Aram Hăvărneanu
2025-05-13 14:15 ` Shawn Rutledge
2025-05-13 14:32 ` tlaronde
2025-05-13 15:29 ` Jacob Moody
2025-05-13 23:20 ` Mathieu Bivert
2025-05-17 11:59 ` Willow Liquorice
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aCNIKSuLSAjQUxyF@legohost \
--to=lego12239@yandex.ru \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).