Humm.. I turned the 'load plugins' flag back on... this seems to trip a plugin
that cant deal with the null GUI... I'll wait for more details about this and
see if people report crashes with plugins bugging at startup.
--
You received this message because you are subscribed to the Google
I am using the extension by Alessandro Fragnani.
Kind regards,
Brad
On Thursday, July 9, 2020 at 2:00:58 PM UTC-6, Félix wrote:
>
> Thank for your update Brad,
>
> I see what you mean and am currently working on solutions on that matter:
> https://github.com/boltex/leointeg/issues/72
>
> I
On Fri, Jul 10, 2020 at 3:14 AM Félix wrote:
added some cool 'test' stuff on branch "boltex/issue75"
>
Félix and I chatted on zoom yesterday for several hours. What follows are
some items we discussed.
A preview unknown attributes, i.e. *p.v.u*, basic usage: So use a .leo file
> that maybe has
added some cool 'test' stuff on branch "boltex/issue75"
A preview unknown attributes, i.e. *p.v.u*, basic usage: So use a .leo file
that maybe has some 'todo' tasks added to some nodes, or other attributes
added by other plugins and what not! open them with leoInteg and behold!
also you can
Thank for your update Brad,
I see what you mean and am currently working on solutions on that matter:
https://github.com/boltex/leointeg/issues/72
I feel the need to point out that if your settings are set correctly,
leoInteg *will* start everything automatically if your current workspace
Hello Félix,
I appreciate your hard work on this project!
My workflow in VSCode is normally as follows:
- Store directories as projects using the Project Manager extension.
Directories can contain a variety of file types (Python, Jupyter, markdown,
Leo, ...)
- Open a project and click on
On Thu, Jul 9, 2020 at 2:54 AM Félix wrote:
> Currently doing small ui touchups and interaction/focus fixes:
>
Thanks for the update.
One feature I'd like to see eventually. When leoInteg opens a .leo file I
would like to see the .leo file appear in vs code's "File: Open Recent"
submenu.
On Wed, Jul 8, 2020 at 4:27 PM Félix wrote:
Make sure the new 'leo tree browsing' option is "on" before trying the
> arrow keys alone. if option is off, you're back to using the arrows in the
> old vscode style which just moves a 'cursor' shade over the nodes, and
> "Enter presses" are then also
On Wed, Jul 8, 2020 at 4:00 PM Félix wrote:
> When I clicked the checkbox the pane said "Modified". How do I save the
>> settings?
>
>
> After 1.5 seconds it should be replaced by auto-save message, in grey, I'm
> going to test it under windows too...
>
Now it works. After the "Modified"
Currently doing small ui touchups and interaction/focus fixes:
- ctrl+S is really needed when focus on tree or body to save the leo file
and derive files.
- and so are maybe home , end , pgup and pgdn keys when the 'leo tree
browsing style' option is on.
- along with the 'enter' key that
Edward, I've switched back to windows to test changing config for the new
'leo tree browsing' mode and it works fine. (for me... might be some other
problem elsewhere)
Alt-arrows call the exact same function as arrows alone when the new 'leo
tree browsing' mode is enabled so there's no
Hi Brad!
Glad you like it!
Knowing that other people understand and use what i'm doing is a great
motivator and a pleasant experience! So thank you for taking the time to
report your usage of leoInteg!
Not knowing much about VSCode extensions, do you imagine that further down
> the road a
>
> When I clicked the checkbox the pane said "Modified". How do I save the
> settings?
After 1.5 seconds it should be replaced by auto-save message, in grey, I'm
going to test it under windows too...
Plain arrow keys select the proper node, but leave a dotted outline
> surrounding the
Hello Félix,
As a regular user of Leo and VSCode, this is awesome!
Following Matt Wilkie's great step-by-step account of how to get things
going under Anaconda Python, I edited some leo outlines and was very
impressed by the potential of this project.
Not knowing much about VSCode extensions,
On Wed, Jul 8, 2020 at 1:54 PM Félix wrote:
> Here's a quick list of most of the new features. Going to make little
> touch-ups and cleanup before merging to master.
>
> *New option setting : Use Leo Tree Browsing. (find better name!)*
>
When I clicked the checkbox the pane said "Modified". How
Here's a quick list of most of the new features. Going to make little
touch-ups and cleanup before merging to master.
*New option setting : Use Leo Tree Browsing. (find better name!)*
*New option setting : Show/hide 'edit headline' hover icon. (allowing to
remove all icons lets the user go
On Wed, Jul 8, 2020 at 9:29 AM Félix wrote:
> Note to self: Test under windows just before pushing after adding features!
>
> Turns out vscode commands are case-insensitive under linux! Which leads to
> compile errors when trying to run under windows with erroneous case
> inconsistencies!
>
>
Note to self: Test under windows just before pushing after adding features!
Turns out vscode commands are case-insensitive under linux! Which leads to
compile errors when trying to run under windows with erroneous case
inconsistencies!
Thanks for trying, and sorry for this rookie mistake! All
On Wed, Jul 8, 2020 at 1:46 AM Félix wrote:
> Just pushed lots of new features on the dev branch!
>
Thanks for this. I'm getting up just as you are going to sleep ;-)
When I start your extension I get this warning:
[boltex.leointeg]: Menu item references a command `leointeg.dehoist` which
is
19 matches
Mail list logo
