Re: What I've just learned from Vitalije

Am Mittwoch, 13. Dezember 2017 22:28:50 UTC+1 schrieb Edward K. Ream: def a_generator(): > if 0: > yield 'abc' # Makes the function a generator > return None > This only works with Python 3. Python 2 does not support mixing return and yield. It's also overcomplicated.

Re: What I've just learned from Vitalije

Am Donnerstag, 14. Dezember 2017 11:05:46 UTC+1 schrieb Edward K. Ream: ​In our code, bool(node) is always True, so this comment is a bit off the > mark. > Well that's a chance to fix this. You are also free to enhance the check.Checking expliciet for None is popular with other DOM-libs.

Re: Inspired by Vitalije's prototype

Am Dienstag, 12. Juni 2018 12:43:11 UTC+2 schrieb Edward K. Ream: Terry, Vitalije, Ville Vainio, Bernhard Mulder, Kent Tenney, Marc-Antoine > Parent, Paul Paterson and others have all made significant contributions to > Leo. By any reasonable measure, Leo is open software. > It's not whether

Re: Inspired by Vitalije's prototype

Am Montag, 11. Juni 2018 15:48:00 UTC+2 schrieb vitalije: Since March 2018, when it was declared that only Edward should commit to > the master brunch, no contribution is counted for any other developer in > leo-editor team. > This is not true. The individual commits of every developer are

Re: Inspired by Vitalije's prototype

Am Dienstag, 12. Juni 2018 12:50:00 UTC+2 schrieb vitalije: > But just FYI here is the explanation from github how they count contributions. Ok, I see where you are coming from. Did you confirm that commits to develop are not appearing in your contribution-list after devel was merged to

Re: Any plausible use for uA's that can't be serialized to json?

Am Dienstag, 1. Mai 2018 23:07:36 UTC+2 schrieb Edward K. Ream: Several Leo devs have suggested using json rather than pickle to represent > Leo's uA's. > > Does anyone presently use any uA that can't be serialized into json? > > Not sure whether you are aware about it, but pythons json-module

Re: Basic Layout of the Leo GUI

Am Mittwoch, 18. April 2018 22:32:37 UTC+2 schrieb john lunzer: That said, your argument appears to be based on something, the "conventions > and standards" of IDE GUIs, that if it exists at all is a rapidly changing > amorphous blob at best. > Not true. There is strong core of established

Re: Merging 5.8-dev into master is next

Am Dienstag, 27. Februar 2018 21:36:11 UTC+1 schrieb Edward K. Ream: > > On Tue, Feb 27, 2018 at 2:19 PM, Matt Wilkie > wrote: > > Would it be easier to invert the process, and have dedicated releases >> branches and then master never needs to be frozen? >> > > ​Anything is

Re: Merging 5.8-dev into master is next

Am Mittwoch, 28. Februar 2018 11:01:04 UTC+1 schrieb Edward K. Ream: > > On Wed, Feb 28, 2018 at 3:39 AM, 'Marcel Franke' via leo-editor < > leo-e...@googlegroups.com > wrote: > >> >> The usual way to do this today: >> >> master as stable. >>

Re: Zettelkasten - Notes Jim but not as we know them.

Am Dienstag, 25. Februar 2020 17:33:10 UTC+1 schrieb Thomas Passin: All right; I've not seen the term "zettelkasten" applied to systems before > Luhmann's got publicised. > Well, I can't speak for the etymology of the word. It's even in germany not the most popular usage for this word

Re: Zettelkasten - Notes Jim but not as we know them.

Am Mittwoch, 26. Februar 2020 23:50:11 UTC+1 schrieb andyjim: I must frankly admit that the only reason I am barking up the zettelkasten > tree is that I have failed to run across a better system > You never played with Wikis? Or generally Hypertext? though of course not a replica of

Re: Zettelkasten - Notes Jim but not as we know them.

Am Donnerstag, 27. Februar 2020 15:46:04 UTC+1 schrieb Thomas Passin: But in general you are not wrong here. Leo Editor can be used that way, >> even though it's not be the best for this. But it's not the worst either. >> It depends on how you polish it and yourself. Using Leo in a way to copy

Re: Zettelkasten - Notes Jim but not as we know them.

Am Freitag, 28. Februar 2020 02:11:20 UTC+1 schrieb Thomas Passin: I think the capabilities of the Nav tab will go a long way. > True, there is also that. I always forget it, because it's so bad UX. BTW Using "created" instead of "timestamp" would be more self-documentating. >> > > That's up

Re: Zettelkasten - Notes Jim but not as we know them.

Am Freitag, 28. Februar 2020 04:51:42 UTC+1 schrieb andyjim: Another ugly and inconvenient question: Are you contemplating a command to > automate starting a new zettel (is it ok to use that term for the time > being? I gather you plan to find a new term.)? Sorry to bring it up again, > but

Re: Zettelkasten - Notes Jim but not as we know them.

Am Freitag, 28. Februar 2020 15:19:38 UTC+1 schrieb Thomas Passin: It's not about storage, it's about reducing visual clutter in the text. > Understandable. I have that problem too. Im thinking about moving my metadata to p.v.u and adding a metadata-widget on the editor-side to not forget

Re: Zettelkasten - Notes Jim but not as we know them.

Am Montag, 24. Februar 2020 20:28:05 UTC+1 schrieb andyjim: > I'm still wondering exactly how Luhmann's indexing played out. > He used manual maintained index-cards of keywords. Just big lists of keywords with reference-numbers which he used a startingpoint to dig into a topic. You can

Re: Zettelkasten - Notes Jim but not as we know them.

Am Dienstag, 25. Februar 2020 02:37:13 UTC+1 schrieb Thomas Passin: Note: Luhmann was the inventer of the zettelkasten. > Ok, just for clarification: No he was not. Zettelkasten is a german word for a box (=kasten) of paperslips (=zettel). It's pretty common tool. People before Luhmann used

Re: Reproducible computational science

Am Dienstag, 7. April 2020 21:57:27 UTC+2 schrieb Brad: > > > I wonder if Leo could be a compelling platform for this use case. > > Why do you think that? What is leo offering that other solutions miss? The idea would be to have a sharable Leo file of a given format that would > include

Re: ENB: Dubious idea: multi-dimentional outlines

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

Re: A better way to send code to language processors

Am Montag, 23. März 2020 16:49:08 UTC+1 schrieb Edward K. Ream: This post > > shows a button that sends code to rust. Thomas adapted it for Graal/JS > here

Re: A better way to send code to language processors

Am Dienstag, 24. März 2020 01:32:29 UTC+1 schrieb Thomas Passin: I often use mixtures of code and non-code blocks. If there are different > kinds of code blocks, though, there can be problems if you want to execute > them. If you execute each code block with a different language processor,