From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Alternative to fine-grained mouse usage?
Date: Thu, 1 Jul 2021 12:36:34 +0200 [thread overview]
Message-ID: <CAFSF3XNDTwtCRKOWOxeuLn59KDJ=KFcZkUqMhY3EgpvMZBOjXA@mail.gmail.com> (raw)
In-Reply-To: <AB4376CCC5D72B8AC6F0F5BFB875E25D@prosimetrum.com>
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, umbraticus@prosimetrum.com <umbraticus@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
next prev parent reply other threads:[~2021-07-01 10:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 1:15 Dworkin Muller
2021-07-01 2:51 ` umbraticus
2021-07-01 4:36 ` Paul Lalonde
2021-07-01 5:05 ` umbraticus
2021-07-01 10:36 ` hiro [this message]
2021-07-03 9:09 ` Dworkin Muller
2021-07-03 9:31 ` hiro
2021-07-01 11:12 ` igor
2021-07-01 17:48 ` Ethan Gardener
2021-07-01 18:01 ` Sigrid Solveig Haflínudóttir
2021-07-01 21:59 ` [9fans] Sam tricks (was: Alternative to fine-grained mouse usage?) Silas McCroskey
2021-07-02 15:03 ` [9fans] Alternative to fine-grained mouse usage? silas poulson
2021-07-02 18:06 ` Ethan Gardener
2021-07-02 18:54 ` Silas McCroskey
2021-07-03 2:29 ` umbraticus
2021-07-03 11:52 ` Ethan Gardener
2021-07-03 11:48 ` Ethan Gardener
2021-07-03 16:32 ` silas poulson
2021-07-03 21:33 ` Ethan Gardener
2021-07-03 23:19 ` Dworkin Muller
2021-07-04 9:42 ` Ethan Gardener
2021-07-02 2:20 ` Cyber Fonic
2021-07-07 3:14 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-07-12 4:01 ` Dworkin Muller
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='CAFSF3XNDTwtCRKOWOxeuLn59KDJ=KFcZkUqMhY3EgpvMZBOjXA@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).