Mat,
Is the origin of Foo bar from the "Grand Foo Bar" from a masonic lodge? a
very U.S. centric source?. I also find it all but useless myself, I have to
read something 5 times if it has too many foos and bars because there is
not any other information contained within them. The fact that
I'm actually allergic to apples.
...but I must admit, that IS a nice alternative. I might start to use it :-)
<:-)
--
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
Has my plea been footile? It has just the opposite effect on me, I can't stop
thinking 'what's a foo?' I must be foolexic, or was on a bar stool the day they
covered it at school. Couldn't 'apples' be used instead?
--
You received this message because you are subscribed to the Google Groups
Addendum: And any newcomers who have a modicum of programming knowledge
will use Foo anyway so... it's probably better to just learn it. IMO it is
part of common computer literacy.
<:-)
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To
@Watt
>
>
Foo, foobar etc was invented specifically so you don't have to think. Plus
it is now a convention so if you introduce something else, then people will
have to get used to that instead. For a single string I guess HelloThere
would work but it is not generic. And for multiple
I hope you twizards know how much your contributions are valued and appreciated
but on behalf of non-programmers everywhere, the easily confused and all those
unfamiliar with the use and tradition behind the word 'foo' can I humbly
request that it is never used in examples relating to
Great answers guys!
I missed to include the "enlist" operator (now added in the OP) but I
assume this doesn't change @pmarios point that it is still generally faster.
>Open close the preview several times
Trick!
<:-)
--
You received this message because you are subscribed to the
Hi Mat,
If we only look at the the <$list line, they are fundamentally different.
The *first *one assigns a macro-call to the filter variable
The *second *one assigns a string value to the filter variable.
The *first list* needs to run 2 filters. 1 in the set widget 1 in the list
widget
filter=<> uses whatever is stored in the variable foo as the filter
itself, filter=[] uses whatever is stored in the variable foo as an
input title.
Some examples are probably more helpful:
<$set name=foo value="""[tag[HelloThere]]""">
Set `foo="[tag[HelloThere]]"`
! Using `"[]"`
<$list
9 matches
Mail list logo
