Saq,
Thanks fort the tip, yes I tried that. I will review again with a fresh
look, but it is confusing me.
I am wondering if there is some sort of regression or bug here?
I suppose in the mean time if I can find an alternative, perhaps with list
filters and not filtered transclusions it would be fine, however it does
seem like a source of hours of frustration.
I will share back any learnings.
Without solving why the former did not work this is a working version.
\define get-config(name)
{{{ [all[current]get[$name$]] ~[[$:/config/$name$]get[text]] ~[[$:/config/
$name$]get[config-values]split[ ]first[]] }}}<br>
\end
<<get-config test-config>>
However from experience if I wish to access the result in a list filter I
will first need to wikify
<<get-config test-config>>
Which makes the code messy.
Regards
Tones
On Monday, 9 November 2020 17:12:54 UTC+11, Saq Imtiaz wrote:
>
> How are you setting
> <local-value>
>
> ?
>
> I suspect it never returns an empty list, and therefore the else clause is
> never triggered.
>
> For example, the following will never trigger an else clause when used in
> a filter, as it will never return an empty list:
> <$set name=config-tiddler value={{{ [[$config-name$]addprefix[$:/config/]]
> }}}>
>
> Assuming that each filter run returns an empty list when it should not be
> used, you can also use the form:
> {{{ [<local-value>] [<global-config-value>] [<config-default>] +[first[]]
> }}}
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/bf81160e-d107-41e1-b0ef-8d8774058edbo%40googlegroups.com.
