On Tuesday, April 21, 2020 at 3:56:26 PM UTC+2, Edward K. Ream wrote:
>
> >Associating code with unit tests would be useful, but putting tests
> in p.u is about the most complicated thing that might work.
>
Of course. Conceptually, AFAICT, unit tests and code are in a similar
relation as nat
On Wed, Apr 22, 2020 at 4:33 AM 'Marcel Franke' via leo-editor <
leo-editor@googlegroups.com> wrote:
> If you mean the declutter-code, then it's no surprise. The implementation
is aweful and halfassed, as usual.
I stopped reading here.
You are allowed to make disrespectful, insulting, remarks on
On Tue, Apr 21, 2020 at 10:45 AM Thomas Passin wrote:
> Here you go. I've included all of my zettel scripts. The one I mentioned
> is zettel-goto-node.
>
Thanks. I'll start there.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To uns
Am Dienstag, 21. April 2020 15:56:26 UTC+2 schrieb Edward K. Ream:
One thought was to put one or more unit tests for node p in p.u, p's user
> data. Clearly that's possible. Moreover, a script could discover and run
> such unit tests.
>
>
That's not really multidimensionl, just nested, as lon
Here you go. I've included all of my zettel scripts. The one I mentioned
is zettel-goto-node.
On Tuesday, April 21, 2020 at 11:34:05 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Tue, Apr 21, 2020 at 9:41 AM Thomas Passin > wrote:
>
> You may not remember, but I developed a script for the zettelk
On Tue, Apr 21, 2020 at 9:41 AM Thomas Passin wrote:
You may not remember, but I developed a script for the zettelkasten system
> that does something much like this.
>
I did remember. I just didn't remember to mention it :-)
> Given that you have a node that contains a line :target: followed by
On Tuesday, April 21, 2020 at 9:56:26 AM UTC-4, Edward K. Ream wrote:
>
> Innovation almost happens without a juicy problem. The problem that
> inspired these thoughts was this: how can we associate unit tests with (the
> code in) a Leo node?
> [snip]
>
> Leo already has unl's (uniform node l
Innovation almost happens without a juicy problem. The problem that
inspired these thoughts was this: how can we associate unit tests with (the
code in) a Leo node?
One thought was to put one or more unit tests for node p in p.u, p's user
data. Clearly that's possible. Moreover, a script could
