Yes, /
is good one, but so is I believe my suggestion the back tick, if it follows something, because then if not it is just code
.
- We could also use
\
to trigger a selection from the new options on 5.3.0
\define
\procedure
\parameters
In fact all pragmas,
I think this solution will work best with this after market in sets of curated auto complete triggers, perhaps organised so when not designing you disable the TiddlyWiki Script items.
To me there is real value in leveraging existing symbols such as [ { | <
because it is in a way self documenting, and appears when you are doing something with the elements that us the character.
I can also see value in pulling the default parameters from widgets, pull content from inside ( )
and change :
to =
Here is my opinionated perspective, for you to throw “bouquets or brickbats” at.
-
I am not yet good enough to write the complex regex if needed for these yet.
-
\
+backtick, pragmas * -
/
+backtick escaped regex (not sure here?) - etc…
-
[[
link tiddlers (in wikitext [[tiddlername]]
) ← existing
{{
transclude all tiddlers (in wikitext {{tiddlername}}
) *
||
transclude here all tiddlers (in wikitext {{||tiddlername}}
) ← existing
!!
transclude field (in wikitext {{!!fieldname}}
) *
<<
replacing macro:
variable or macroname ( in wikitext <<macros>>
) *
And the harder to document using a single backtick
[` link all tiddlers (in filters `[tiddlername]`) *
{` transclude all tiddlers (in filters `{tiddlername}`) *
{!` transclude field (in filters `{!fieldname}`) *
<` all macros (in filters `<macroname>`) *
<`??? all variables and macros (in filters `<macroname>`)
maybe also ?
<m` for macros not variables ???
<v` for variables not macros ???
<p` for parameters ???
etc...
- Note: When I use a single backtick in the trigger it does not display correctly in the Registered triggers
- Changing from
<code>
to(Trigger <$text text={{!!trigger}}/>)
fixes it.
- Changing from
- The above lend themself to definition in data tiddlers, perhaps with a toggle to enable / disable.
- I am building these now and will package, but there will be a few challenges
- Edited to reflect changes as I build them, * used for those created
- My efforts so far autocomplete-triggers.json (5.0 KB)
The beauty being we can do what ever we want