From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] toggle play
Date: Fri, 27 Apr 2018 06:47:55 -0400 [thread overview]
Message-ID: <20180327064755.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
The latest push is an experiment with a couple toggle commands, nothing set in stone here.
swrap was clunky to type, and used all the time, so I reverted back to sw, search with wrap, and also sw+ and sw-.
So if a script knows you will want search with wrap enabled
sw+
this also has the advantage that the absolute commands don't print any output, and you usually don't want a lot of output from your running script.
The toggle version sw still prints the message because you might not remember where you were, you might want it to tell you search with wrap or search without wrap.
This is a general pattern.
This was my vision 20 years ago: edbrowse tells you what you need to know and nothing more.
Another one implemented is js+ and js-,
because I have a number of functions that specifically want javascript, or don't want javascript, and you probably do too.
If we like this style I can implement the rest.
It's pretty much boiler plate programming.
Karl Dahlke
reply other threads:[~2018-04-27 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180327064755.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.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.
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).