any easy way to make that distinction? ..
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)
/daydreams about tmoad
…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”
similar to
.https://archive.is/tM7Yo#selection-401.99-401.252
These names are reserved from initial registration, but to the extent they are already registered the existing registrant may renew them
^(random quote from archive of example.com , ftr)
perhaps i should get round to testing/(locating/reading the source of) the https://tiddlywiki.com/#WebServer%20API
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