Re: Discuss: compare zettlekasten, bookmarks, google

On Tue, Jul 7, 2020 at 3:00 PM Paul wrote: > "Often googling a topic is faster than using a bookmark, no matter how > easy it is to find the bookmark. Otoh, bookmarks remind me that something > is worth googling!" > > Ad hoc googling doesn't afford one the opportunity to structure knowledge >

Discuss: compare zettlekasten, bookmarks, google

"Often googling a topic is faster than using a bookmark, no matter how easy it is to find the bookmark. Otoh, bookmarks remind me that something is worth googling!" Ad hoc googling doesn't afford one the opportunity to structure knowledge as one builds understanding of a new subject. Nested

About Leo and vs code

I would like to say just a few words about Leo's future as it relates to vs code. 1. Leo will remain a stand-alone pure python app indefinitely. It would be a huge mistake to deprecate Leo as a stand-alone app. Leo's existing plugins, such as Terry's todo.py and backlink.py plugins have no

Re: hoist/dehoist

On Tue, Jul 7, 2020 at 5:24 AM Edward K. Ream wrote: I've added the following to my internal to-do list: > > Review leoInteg issues and comment if a 'helper function' in Leo might > help. > I have just created Leo issue #1613 for this.

Discuss: compare zettlekasten, bookmarks, google

Every since the original discussion of zettelkasten I have been wondering whether it might be useful in organizing my bookmarks. It certainly has drawn my attention to how I actually do organize my bookmarks. Perhaps

Heh: how to find the source code for any vs code plugin

You can see the source code for any vs code plugin without having to install it: - In vs code, click the plugins (building blocks) icon on the left. - Search for the plugin. - Selecting the plugin opens a corresponding extension's tab. - All plugins have a "Repository" button in the extension's

Please *do* create issues for any purpose

In the Markdown Recipe thread we have been discussing Leo issues. Should we try to limit their number? Are open issues a "blight" on Leo? On the contrary, I think we should regard Leo's issues as a sign of our community's

Re: You didn't ask for it but it's here anyways! LeoInteg 0.1.12

On Mon, Jul 6, 2020 at 10:00 PM Félix wrote: Try this, (close everything - start from scratch) in your normal vscode > window, press [CTRL+, ] to open your user settings, switch to the JSON view > if not already in json text mode, (upper right corner button) , then start > leoInteg (and its

Re: hoist/dehoist

On Tue, Jul 7, 2020 at 12:59 AM Félix wrote: Nevermind the hoist/de-hoist I've got it under control! :) > Glad to hear it. Well done. In a similar vein, I'm going to test an importer script (with Ctrl-B in leoInteg) and see what happens. Edward -- You received this message because you are

Re: hoist/dehoist

On Mon, Jul 6, 2020 at 7:10 PM Félix wrote: > If anyone who knows Leo's codebase wants to help with leoInteg, a nice little thing would be to go through the issues at your leisure, and comment if it rings a bell in relation to a 'helper function' in Leo that might do something in particular to

Re: hoist/dehoist

Nevermind the hoist/de-hoist I've got it under control! :) works great with this: def getChildren(self, p_ap): '''EMIT OUT list of children of a node''' if p_ap: w_p = self.ap_to_p(p_ap) if w_p and w_p.hasChildren(): return self.outputPNodes(w_p.children()) else: return self.outputPNodes([]) #