any one
a) used a terminal ?
b) heard of “(gnu)readline” ?
im interested in the research/philosophical aspects of the command line
post linked above
(fwiw: less interested in (imho brain-dead) machine generated code )
it seams many technical details and historical tradeoffs
( line discipline !? )
have shaped the command line functionality of the less popular but more flexible operating systems
eg:feature’s of readline influence the address bar in browsers
and js-dev-console’s
(imho it would be relay something to have tw functionality to ‘work’ from within dev-console )
… might more insight into such history inform the ui/ux decisions of tomorrow
Beware, though: What you are about to see is not particularly elegant. In fact, the TTY subsystem — while quite functional from a user’s point of view — is a twisty little mess of special cases. To understand how this came to be, we have to go back in time.
fwiw the motivation/interest in a
usable prompt based interface
mostly stems from attempting to better understand
the connections betwixt constructs
which create the ui/gfx (mostly by attempting to alter and catastrophically braking things) =}
on some previous iteration (how time flys)
…NLS is (imho) interesting to compare with tiddly wiki
perhaps some similar demo should be recreated on multiuser-wiki!! ;D
anyway …i was trying to recall when the console.ui was an extension how could i forget firebug!
i sniped that and got some
uncaught exception(s): Linked List only accepts string values, not undefined $:/boot/boot.js:2515:10
=p
which makes me thunk of this succulent snippet i foraged from the depths of [[search-company-scrape-data]] ;- )
parse?/split tid/text with filter
each line with
{{{ [all[current]get[text]splitregexp[\n]] }}}
each line with substring
{{{ [all[current]get[text]splitregexp[\n]contains-string[substring]] }}}
each char
{{{ [all[current]get[text]splitregexp[]] }}}
presumably it would not be much of a stretch to create
link url/uri whatever handler that could
display sections from “#err/$:/boot/boot.js:2515:10”
though im surprised after a quick scan “commands”
is not included
PATH="./node_modules/.bin:$PATH"
tiddlywiki
usage: tiddlywiki [<wikifolder>] [--<command> [<args>...]...]
Available commands:
* commands: Run commands returned from a filter
...
tiddlywiki --commands "[[help]]"
Error: Missing command: help
perhaps what is (imho) missing could be provided by creating
the above missing command … (any hints?)
idk but perhaps it would be nice coherence
if similar route’s/functions could be called from api or cli or …
at least it might simplify documentation?
( :
/aaaahhhhhhh finaly
a few concepts/observations from sections from this wiki for some reason spring to mind … though tbh im not shore how much relevance any of it may or may not have …
in this or that
.context
=0
