leointeg now updated with 'real' editable body pane made out of a fake 
document in a custom filesystem. does not update leo side yet.
 
On Saturday, August 10, 2019 at 3:49:34 PM UTC-4, Robert Cholette wrote:
>
> First I'd like to apologize for just asking this on github, I didnt 
> realise here was perhaps a better place to ask this kind of thing... 
>
> Hi! Long time leo user here. I use it mainly for the 'core' features: 
> outline organisation of my code : @clean nodes, structure with @others. And 
> I alt-tab leo alongside with another editor/IDE for 
> running/debugging/compiling/linting/beautifying/etc...
>
> I dont care so much about vim/emacs integration nor dont even understand 
> what those buffers/minibuffers are and all around feel like that qt-gui 
> framework didnt age very well. (no offence meant here, as I would be 
> devastated to think I offended edream, he's like my programming 'idol')
> I also do not use @buttons and internal scripting in leo altough i can see 
> its use for some people. 
>
> I mainly use Leo for its 'file-generation'/'file-reading' (mainly @clean) 
> feature via the outline structure that it provides. Organising a program 
> with an outline, clones and @others is the best! Which also, if I may say 
> so, is Leo's 'killer feature'.
>
> So i'd like to try and integrate, or 'roll my own' leo in my other 
> favorite editor so that I have the subset of leo's features that I just 
> defined as its 'killer features' available without having Leo 'opened'. 
> Is leoBridge the way to go? ...or is there a way to start leo with no GUI 
> and have it listen for commands on a specific port for input/output of 
> commands and answers? 
>
> Many thanks in advance!!  
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/d506676e-dbd3-4b73-bd08-84f6cd2aad6a%40googlegroups.com.

Reply via email to