Having difficulty with WIndows 10

[Phil]

I am trying (almost successfully) to get Leo installed on a colleague's 
Windows 10 machine. She has installed Anaconda and is running a Python 3 
environment. She has pulled the master branch of Leo into 
c:/Users/userid/Tools/leo-editor, and she can run an Anaconda prompt in 
that directory and run Leo "manually" just fine. But we have utterly failed 
getting file associations to work so that she can just double click on a 
Leo file to open it.

Any suggestions, either to make the appropriate file associations, or for 
some reasonable workaround?

Thanks!
Phil

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: edit-pane-csv separator

[Josef]

Hi Terry,

after using edit-pane-csv for some time now, I have one big wish left: it 
would be great if Leo could remember the settings for each file, at least 
for @clean nodes. Ideally the csv pane would stay open for these nodes.

I have many csv files around, which I need to maintain manually on a 
regular basis, so it would be nice if Leo could remember the settings for 
each of these files, and it would be even better if I would not have to run 
the command edit-pane-csv on each file every time after I closed the 
associated Leo file.

Cheers - Josef

On Friday, August 10, 2018 at 5:38:37 PM UTC+2, Terry Brown wrote:
>
> On Fri, 10 Aug 2018 08:14:53 -0700 (PDT) 
> Josef > wrote: 
>
> > Hi Terry 
> > 
> > I tried 
> > 
> > Leo 5.7.4 devel, build 20180807122609 
> > 
> > and it did not work right away with a .latex file. It seems to get 
> > confused by the @language latex in the first line. It worked when I 
> > removed it. 
> > 
> > It would be nice if it would ignore leo directives. 
>
> Hmm, it doesn't pay any attention to leo directives, and just defaults 
> to ',' CSV mode.  Not sure what was going on there. 
>
> > Another quirk is, that every line needs to have the same number of 
> > separators, but particularly when editing latex tables by hand one 
> > does not always enter all cells if they are empty anyway. This 
> > probably is a limitation of the Python CSV library, though. 
>
> True... hmm, the design is that a series of lines with the same number 
> of separators is what *defines* a table.  Probably reasonable for CSV, 
> but I can see the issue with LaTeX. 
>
> The simplest way I can think of addressing that would be some way to 
> normalize the number of delimiters in a table, either have the user 
> select the whole table or incrementally bring in lines from above / 
> below the table, adding empty cells to them. 
>
> But if I remember LaTeX tables, that will impact line drawing, 
> "1 & 2 \\" vs "1 & 2 & & \\" in a four column table for example, the 
> first leaves the rest of the line blank whereas the second displays 
> empty cells, if you're drawing lines between cells that is.  I think. 
>   
> > I think it would also be nice if it could figure out the separator by 
> > itself and start up with a good suggestion, similar to the "sniffer" 
> > tool in the CSV module. 
>
> Might be doable, although I'm guessing that usually you'd only need to 
> change it once per session, and having it guess too often might make it 
> less flexible in terms of editing different table types in the same 
> node etc.  I did think of adding a presets dropdown for CSV / tab / 
> LaTeX / pipe etc. 
>
> > That all said, thank you very much for this command. It makes my life 
> > a lot easier. 
>
> Glad to hear it. 
>
> Cheers -Terry 
>

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

ENB: leoflexx.py is almost complete, but...

[Edward K. Ream]

A milestone: LeoWapp is almost complete. Almost all needed infrastructure 
works.

Alas, serious problems with the body pane remain. These problems must be 
solved in order to complete LeoWapp. I suspect these problems can be fixed, 
but there are no guarantees. We might have to put LeoWapp on hold...

*Serious problems with the body pane*

There are serious problems with using the ace JS editor 
,
 
as described in flexx issue #534 
. The ace text editor grabs 
Ctrl-F, Ctrl-A, tab and backspace, and probably other keys. Also, it 
"helpfully" adds matching parens closing parens.

These would not be problems if the necessary JS reactions would fire.  
These reactions would tell Leo's core the *actual* contents of the ace 
editor's text.  So far, these reactions never fire.

Arguably, the CodeMirror JS editor 

 
might a better choice than ace because CodeMirror aims to do *less.* We 
shall see. It will be straightforward to switch between ace and 
CodeMirror.  As with ace, it will be essential for CodeMirror to report 
(via reactions) to Leo's core (via LeoBrowserBody actions).


*What works*

With the exception of JS editor reactions, *all* necessary infrastructure 
is in place:

- Almost all control keys work, including Ctrl-B.
- Alt-x opens the minibuffer.  Most commands "just work".
- The 'unit' Easter Egg runs all unit tests.  Several fail, *as they should*
.
- Leo sets the outline's "dirty bit" correctly, but see below. 


*Minor problems*

- You must click the newly-opened Leo window before any keystrokes will 
fire.
  After the first click, almost everything works, except for reactions in 
the body pane.
- Alt-4 runs unit tests in the wrong environment.
  This is expected, and doesn't matter.  Instead, use the "unit" Easter Egg 
in the minibuffer.
- LeoWapp doesn't detect that the window is going to close, and so can't 
issue a warning.
- Arrow keys select multiple nodes in the outline pane.

*Summary*

The CodeMirror JS editor might be a better choice than ace.

Getting reactions (in either JS editor) to fire is the *crucial *missing 
piece of the puzzle:

- These reactions would complete the LeoWapp project!
- Otoh, permanently missing reactions would be a show-stopper.
- I'll ask Almar about getting JS editor reactions to fire after I have 
tried my hand at CodeMirror.

We'll know in a day or three whether the present JS editors can be made to 
generate the needed reactions.  If they can't, this project would have to 
be put on hold indefinitely. Sure, we could imagine forking either JS 
editor, but that's not likely.  Making either editor an official flexx 
widget would surely solve the problem, but who knows when that might happen?

Do not despair: I suspect the needed reactions can indeed be made to fire 
:-)

All other problems are minor.  Most should be fixable in an hour.

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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.