Re: Usage of "Leo-devel" archives from GitHub installed via pip into a dedicated PyVE does not work

> > I think I'm just going to declare the incantation of `pip install >> http://path/to/leo/archive.zip` as >> broken beyond reasonable repair and that people have to use either PyPi or >> git clone (when using pip). >> > > Looks like I'll have to bite the

Re: How do you install leointeg into VS Code?

thought i might add this in here... Here's a nice feature of vscode: There's a terminal at the bottom of vscode (pull/drag from the bottom if already closed) so you can use it after opening the expansion folder to run 'npm install' without even opening a terminal prompt. wait for those

Re: How do you install leointeg into VS Code?

By the spirit of Shannon! I forgot the most important step: Installing dependencies! Assumings you have node.js installed on your computer, install all dependencies by running 'npm install' from inside the expansion directory. (this will install all dependencies listed at the end of

Re: How do you install leointeg into VS Code?

On Thursday, October 10, 2019 at 2:48:21 PM UTC-5, Robert Cholette wrote: > > > 1 - have vscode installed on your computer, obviously > 2 - git clone the project into a folder > 3 - right-click that folder -> open with vscode, OR from inside a vscode > window, File-> Open Folder... > Well,

Re: How do you install leointeg into VS Code?

On Thu, Oct 10, 2019 at 2:51 PM Robert Cholette wrote: > P.S. Please do not hesitate to try and crash my expansion to find bugs! > Hehe. What else did you expect? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from

Re: How do you install leointeg into VS Code?

On Thu, Oct 10, 2019 at 2:48 PM Robert Cholette wrote: So basically, just opening the leoInteg project in vscode allows you to try > it out by pressing F5 (run / start a debug session) > Thanks. I'll get to this very soon. It would be good to put the full instructions in the readme file.

Re: Improved asciidoc, asciidoctor and pandoc support

On Thu, Oct 10, 2019 at 3:18 PM Matt Wilkie wrote: > >> For me the external file is not created. See the desktop-integration.leo >>> file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. >>> >> >> Matt, what's the status of this now? >> > > It works after installing asiidoc3. I didn't

Re: Usage of "Leo-devel" archives from GitHub installed via pip into a dedicated PyVE does not work

Hello Matt, Am Donnerstag, 10. Oktober 2019 08:31:09 UTC+2 schrieb Matt Wilkie: > > Following a similar recipe using Conda I confirm `global config dir: None` and `No @menu setting found` log window messages. I also have critical missing folders in "PYTHONHOME\Lib\site-packages\leo",

Re: Improved asciidoc, asciidoctor and pandoc support

> > > For me the external file is not created. See the desktop-integration.leo >> file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. >> > > Matt, what's the status of this now? > It works after installing asiidoc3. I didn't understand that @adoc is fundamentally different from

Re: How do you install leointeg into VS Code?

P.S. Please do not hesitate to try and crash my expansion to find bugs! (such as try to open multiple views of the same body pane, or open multiple different body panes simultaneously and see the outline focus on the right node as you click inside different body panes, try to modify a body and

Re: How do you install leointeg into VS Code?

1 - have vscode installed on your computer, obviously 2 - git clone the project into a folder 3 - right-click that folder -> open with vscode, OR from inside a vscode window, File-> Open Folder... 4 - this will open a vscode window for working on leoInteg, it will recognize that this is an

Re: #1342 ready for testing in the find-tab branch

#1357 I cannot replace-all anymore. Everything else works as per the docs. And I cannot use Alt-x if the cursor is in the "replace" text input field, which is very strange and apparently doesn't happen on Windows. (all I get is an x at the end of the replace string) I even tried switching to

How do you install leointeg into VS Code?

The leointeg page doesn't seem to have any installation instructions. I would love to try this out. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: @button for displaying all parents of a clone to log pane

On Thu, Oct 10, 2019 at 12:19 PM Brian Theado wrote: > > I confess that I find both commands confusing, but I'll leave them in. >> > > Thanks for the feedback. Do you mean you find the output confusing or how > to use it confusing or confusing why it would be useful? > All of the above. For

Re: @button for displaying all parents of a clone to log pane

Edward, On Thu, Oct 10, 2019 at 12:36 PM Edward K. Ream wrote: [...] > Done at 5e0117d, if I understand you correctly. > Thanks! > I confess that I find both commands confusing, but I'll leave them in. > Thanks for the feedback. Do you mean you find the output confusing or how to use it

Re: Improved asciidoc, asciidoctor and pandoc support

On Mon, Oct 7, 2019 at 2:08 PM Matt Wilkie wrote: > Please report your experiences with these new features. >> > > For me the external file is not created. See the desktop-integration.leo > file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. > Matt, what's the status of this now?

Re: @button for displaying all parents of a clone to log pane

On Thu, Oct 10, 2019 at 6:08 AM Brian Theado wrote: > I've been thinking about this a lot and I've come to the conclusion that > there should be a separate command that will display all the clone > positions of a given node. Maybe the original could be renamed from > 'show-clones' to

Re: Where is the demote command? Why does the tutorial not link to it? Why is it not in the Outline menu?

Op dinsdag 8 oktober 2019 21:15:44 UTC+2 schreef Matt Wilkie: > > Plus, making sure it's not overlooked, you can move nodes around with > keyboard shift-arrow as well as with the commands. For me thus is usually > more convenient. > > -matt > > Thanks, this was exactly what I was looking for!

Re: docs: Installing Leo from sources (all platforms)

On Thu, Oct 10, 2019 at 3:30 AM Matt Wilkie wrote: I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains > generic install-from-source instructions for all platforms. It might need > some format tuning and perhaps other editing. I think it could replace or > be merged with a

Re: @button for displaying all parents of a clone to log pane

I've been thinking about this a lot and I've come to the conclusion that there should be a separate command that will display all the clone positions of a given node. Maybe the original could be renamed from 'show-clones' to 'show-clone-parents' and this one could be called 'show-clone-ancestors'

docs: Installing Leo from sources (all platforms)

I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other edting. I think it could replace or be merged with a couple of the following nodes. Or at least something to

Re: Mention boltex at LeoEditor.com?

On Wed, Oct 9, 2019 at 4:24 PM The Living Cosmos wrote: > I started a recent reddit thread about Leo and someone mentioned boltex: > > https://www.reddit.com/r/emacs/comments/deslm6/interface_to_outlines_similar_to_leo_editor/f32shpx?utm_source=share_medium=web2x > > and it looks mind-blowing: >

Re: Usage of "Leo-devel" archives from GitHub installed via pip into a dedicated PyVE does not work

On Thu, Oct 10, 2019 at 1:31 AM Matt Wilkie wrote: I think I'm just going to declare the incantation of `pip install > http://path/to/leo/archive.zip` as > broken beyond reasonable repair and that people have to use either PyPi or > git clone (with pip). >

Re: Usage of "Leo-devel" archives from GitHub installed via pip into a dedicated PyVE does not work

> > Following a similar recipe using Conda I confirm `global config dir: None` >>> and `No @menu setting found` log window messages. I also have critical >>> missing folders in "PYTHONHOME\Lib\site-packages\leo", like Icons. Digging >>> in... >>> >> >> Can you give already a status update on