i don't think you're missing anything obvious in terms of acme, it's clearly not made for you.
your options are either to modify acme itself and insert keyboard shortcuts, or to ignore acme and try to make as many little scripts as possible, executed from rio terminals. i often feel like i can not justify the time to spend and create scripts for everything, when i can instead use an iterative interactive process of running and editing and then rerunning commands in rio. but given your input problems, i am sure you can not only use this excuse to spend more time on automation, but you'll get rather good at it, too, over time, meaning you will be able to remember more and re-use more of your own commands for many different use cases... at some point you'll have invented your own couple hundred private languages that will require just plain text based input methods. it's very effective, just not very standard and not very acme-like. so yeah, personally i'd chose this: just make more rc scripts, as many as you can :) On 7/1/21, umbrati...@prosimetrum.com <umbrati...@prosimetrum.com> wrote: >> taking advantage of Fitts' law in UI interactions > > another fairly standard practice: organise window management > to leave a pixel or two around the edge to allow slamming > mouse to the nearest extremity in order to access rio b3 menu. > > blasphemy: I occasionally wonder how difficult it would be > to implement windows-style Ctrl+←/→ word boundary jumping, > maybe even Shift to select… > > umbraticus ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T716c5aa0e2aa8a27-M2fad8ae63eacb802507bb294 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
