From: Karl Dahlke <email@example.com>
Subject: [edbrowse-dev] toggle or explicit
Date: Thu, 26 Apr 2018 06:52:14 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
We batted this about on the chat group, but it's a significant UI change so should be addressed here as well.
I was wondering if scripts would run easier with swrap and snowrap to explicitly enable and disable search with wrap, rather than a togle, which is state dependent. Or maybe swrap1 and swrap0.
Then a script could set it or clear it and know where we stand.
Some commands like ci and cs are explicit, others are toggle. There are pros and cons. The entire gestalt is inconsistent however.
So another idea is to redo everything in a consistent fashion: foo is a toggle, foo1 enables, foo0 disables.
It's a significant change to the UI, but might be worth it.
Someone suggested foo=1 or foo=on to enable, but edbrowse is all about speed, and minimal typing, in the fine tradition of ls because we're too damn lazy to type list.
I think people could quickly get use to foo1 and foo0.
Another possibility is foo+ and foo-.
reply other threads:[~2018-04-26 11:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).