On Friday, February 24, 2017 at 7:23:16 PM UTC+1, Daniel Cunningham wrote:
> So instead of: "death by whitespace?" it's simply: "Dude. Whitespace
> matters." :-)
>
:) ... but you are right. It sometime hurts quite a bit. ...
But we also have to deal with backwards compatibility. .. There
Hi Mario,
Thanks for your efforts at explaining. Yes, I'm coming to a new
appreciation. With TW, you can't treat declarations and invocations as a
matter of personal style. You need to understand exactly how the
substitutions will take place.
So instead of: "death by whitespace?" it's
Hi Mario,
You are quite the gentleman! Rookie mistake on my part. Many thanks for
spotting the error!
Best regards,
-- Daniel
On Fri, Feb 24, 2017 at 12:00 AM, PMario wrote:
> Hi,
>
> I think there is a typo. IMO it should be:
>
> \define
On Friday, February 24, 2017 at 7:34:03 AM UTC+1, Daniel Cunningham wrote:
>
>
>- Death by whitespace: I found out if there's any leading whitespace
>(before the macro definition) the tiddler fails. Also, if there's any
>whitespace in the filter list, it will fail. Again, trying
On Friday, February 24, 2017 at 7:34:03 AM UTC+1, Daniel Cunningham wrote:
>
> Finally. some observations and questions for you veterans (keeping in mind
> that I'm not at all familiar with the code base yet):
>
>- It kind of "bothered" me that the declaration "looks" like it has a
>
Hi,
I think there is a typo. IMO it should be:
\define timeline2(limit:"100",format:"DDth MMM
",subfilter:"",sortaction:"sort",dateField:"modified")
see the : after sortaction!
-m
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To
Sorry It was when I tried to add a comment above the macro that I threw the
error. I need to study up on TW5 comment syntax.
On Thursday, February 23, 2017 at 11:15:35 PM UTC-8, Daniel Cunningham
wrote:
>
> Uhhh, scratch the "leading whitespace fragility" question. I need to
> chase my own
Uhhh, scratch the "leading whitespace fragility" question. I need to chase
my own sloppiness down... :-)
On Thursday, February 23, 2017 at 10:34:03 PM UTC-8, Daniel Cunningham
wrote:
>
> Hi Mark,
>
> Thanks for that follow-up! I'm beginning to see (thanks to you and Mario)
> how this
Hi Mark,
Thanks for that follow-up! I'm beginning to see (thanks to you and Mario)
how this works.
OK, so I now get how you can negate the sort order inside the macro (with a
bang). And then I see from the docs that the way that expression evaluates
is L-to-R via that "railroad" style
Hi Daniel,
Mario's syntax uses the macrocall widget, which is a somewhat more formal
way of calling a macro that works better in some situations.
The problem with the timeline macro is that it doesn't give you access to
the sorting order (A/D), as you can see in this filter:
Many thanks, Mario! I tried that, and it works.
But rather than change a shadow tiddler, I elected to put in into a
"end-user" tiddler, that I can then place in the sidebar with a
"$:tags/SideBar" tag. That gives me the functionality I was looking for.
Also, I won't shoot myself in the
I've made a PR for this fix.
On Wednesday, February 22, 2017 at 7:32:35 PM UTC-8, Mark S. wrote:
>
> So this line in the documentation is incorrect:
>
> [!is[system]$subfilter$has[modified]!sort[modified]limit[$limit$]eachday[
> modified]]
>
> and should read instead
>
>
So this line in the documentation is incorrect:
[!is[system]$subfilter$has[modified]!sort[modified]limit[$limit$]eachday[
modified]]
and should read instead
[!is[system]$subfilter$has[$dateField$]!sort[$dateField$]limit[$limit$]
eachday[$dateField$]]
Mark
On Wednesday, February 22, 2017 at
On Wednesday, February 22, 2017 at 11:48:49 PM UTC+1, Daniel Cunningham
wrote:
>
> And then what you are saying is that since this is embedded in the
> timeline macro, any sort criteria I try to apply to "created" will be to no
> avail?
>
Have a look at the docs:
A! Thanks much, Mark! I saw that documentation, but did not realize
its implications.
So, just to be clear, it's saying?...
1. look at stuff that's not a system tiddler;
2. filter anything that's got a "modified" field;
3. do a reverse sort on the "modified" date;
4. and
Per the documentation, timeline uses this filter:
[!is[system]$subfilter$has[modified]!sort[modified]limit[$limit$]eachday[
modified]]
This means that a sort on the modified field is applied after the subfilter
and will take precedence over a sort order specified in the subfilter.
I guess I
16 matches
Mail list logo