On Mon, Jun 22, 2020 at 6:27 PM Félix <[email protected]> wrote:
>
> - I see that the command palette already supports some of Leo's
>> outline-oriented (essential) commands. It might be good to use a separate
>> Leo decorator to denote commands that leoInteg should support. But that's a
>> nit.
>
>
> They do have a decorator: "Leo", opening the command palette and
> ctrl+shit+P and typing 'leo' will restrict to leo commands.
>
Thanks for the clarification. Do you have special code to discover Leo
commands, or do you allow anything in c.commandDict?
- I also see that you support some Leo settings in the way cool settings
>> pane.
>
>
> In vscode, with the 'git-lens' extension installed, (i think it comes by
> default now even!.. not sure...)
>
Iirc, a git extension is pre-installed. I installed git-lens manually.
> open the command palette and start typing "git welcome" to see what
> inspired me for that settings "webview" page!
>
That's cool. The description of git-lens in the plugins pane is even more
impressive.
> - I don't see syntax coloring in the Leo outlines.
>
>
> Wheuat?? what do you mean? syntax coloring works and it makes the whole
> 'leoInteg" landscape come together so nicely! I have to re-do all my gifs
> and movies because of that! Have you pulled 'dev' ? maybe I forgot to push
> ,,, I'll check again...
>
I just switched to your "dev" branch and did an npm install. Now I do see *some
*syntax coloring in the body pane.
I see (both in my actual files and in your example gifs) that Leo's
directives are colored, but not python-specific keywords such as "def".
Let's test for typescript. From the command palette I see that "Leo: Insert
Node" is bound to Ctrl + I. Very cool.
I created a new node, containing:
@language typescript
import * as vscode from "vscode";
import * as WebSocket from 'ws';
import { Constants } from "./constants";
import { LeoBridgePackage, LeoAction } from "./types";
import { LeoIntegration } from "./leoIntegration";
import { LeoAsync } from "./leoAsync";
Wow. Copy and paste from vs-code retains the styling in this email!
You see exactly what I see. The @language is not colored, nor are "import"
and "as" and "from" keywords.
- After F5, the new window contains an "Outline" area in the Explorer area.
>> It says "The active editor can not provide outline information". What is
>> the purpose of the "Outline" area? There is also a "Timeline" area. It
>> shows "No timeline information was provided". I wonder whether this might
>> be related to a plugin, say gitLens.
>
>
> aha! - those are regular vscode views that are usually in the explorer
> panel indeed. they are standard, The 'outline' will show you a regular
> 'outline' of class methods, properties of a file that would be open in an
> editor. ...any file... just select a source in the explorer, it opens and
> boom, half a second later, a generated outline appears. its a plain
> representation of the source file. (the opposite of building with leo, if
> you will... or maybe like a plain 'import' tree without any structure depth
> to represent anything.)
>
I suspected as much. I think it would be fine to suppress those panes.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/CAMF8tS03zGMZz4%3D%3D99P2PtHMD1MLt9Ymbo2QLTU1uYbzE15gLQ%40mail.gmail.com.
