Re: No python 2 work after December 1, 2019

[Terry Brown]

Not sure about that, my
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
is running 2.7 by default, and I'm sure I did a fresh install, not an
upgrade.  99.5% sure anyway ;-)

But I do think Python 3 is *installed* by default on 18.04.  3.6.7
currently.

Cheers -Terry

On Wed, Jun 5, 2019 at 9:36 AM Josef  wrote:

> Correction:
>
> as far as I heard, Python 3 is already the default on the currrent Ubuntu
> 18.04 LTS. I was under the wrong assumption that Python 2 is the default,
> because when I upgraded from 16.04 LTS to 18.04 LTS the default Python
> installation did not change from 2 to 3.
>
> Sorry, if I caused any confusion.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/b2f938c9-6d81-4674-aae6-71c1a7182dc8%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAFPg46Q_oWJCqx3N7qxtN88-Jsg5SYkK8EJscDFMU2%2Bv-p%2BVTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: No python 2 work after December 1, 2019

[Josef]

Correction:

as far as I heard, Python 3 is already the default on the currrent Ubuntu 
18.04 LTS. I was under the wrong assumption that Python 2 is the default, 
because when I upgraded from 16.04 LTS to 18.04 LTS the default Python 
installation did not change from 2 to 3.

Sorry, if I caused any confusion.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/b2f938c9-6d81-4674-aae6-71c1a7182dc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: No python 2 work after December 1, 2019

[Josef]

On Thursday, May 2, 2019 at 1:00:23 PM UTC+2, Edward K. Ream wrote:
>
> December 1 of this year is a firm cutoff date for further work in the 
> unified python 2/3 code base that is the basis for Leo 5.9.  After that, 
> further work would be pointless, because official support for Python 2 will 
> end on December 31.
>
> I suspect there will be a 5.9.1 release of Leo that will fix difficulties 
> with LeoWapp.
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/d58d5a5c-d414-46d5-9898-b6fbdf8e4fb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

switching use-pygments within one leo file

[Josef]

use-pygments = True works better for latex files, but Leo's colorizer seems 
to work better for some other syntaxes,
so I was wondering if there is a way to switch between the two within a 
single Leo outline?

Btw, the pygments colorizer seems to be buggy when it comes to Lua long 
literal string syntax, e.g. those between [[ and ]] or between [=[ and ]=] 
etc. when it contains newlines or quotes. Should I file a bug report, or is 
this anyhow a "won't fix"?

- Josef

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/d77e702e-7f25-4a07-8d8d-931ebc5c5b37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mass update: rev 2fefa47 in devel contains "super" branch

[Edward K. Ream]

This completes #1169 . 
The code is much simpler than before.

#1170  discusses a 
large number of pylint-inspired changes made in the "super" branch, and the 
risks involved. Imo, removing python 2 related cruft must be done now, no 
matter what the short-term pain may be.

The new code will form the basis of the "unity" branch. See #1171 
, which recommends 
retiring Leo's old look and feel. Imo this work is the best way to simplify 
Leo. We will all have a chance to vet this branch before merging it into 
devel. 

I apologize in advance for any problems these changes may cause. 

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/3886964e-ac15-4600-83a3-2c3985c5192b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using Sync with Leo on Win/MacOs

[Edward K. Ream]

On Tue, Jun 4, 2019 at 2:40 PM jkn  wrote:

> I do something like this, under Linux and Windows. I have @file nodes with
> names like this:
>
> @file .{{sep}}docs{{sep}}myfilename.mwiki
>
> The {{sep}} gets magically converted to '\' under Windows and '/' under
> Linux. I think there are other keywords available with this {{...}}syntax;
> look for a thread "cross-platform file references - how to deal with?"
>

FYI, searching reveals that the magic happens in the following functions:

- g.os_path_expandExpression.
- replace_path_expression.

Two more visible wrappers around os.path methods use the above functions:

g.os_path_finalize and g.os_path_finalize_join.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0CvEb4C2MGwG25VQFHvUkLh1XV6bxE9K_HAjsVmwu2Ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using Sync with Leo on Win/MacOs

[Israel Hands]

thanks Jon - very helpful - will chase this!

IH

On Tuesday, 4 June 2019 20:40:56 UTC+1, jkn wrote:
>
>
>
> On Tuesday, June 4, 2019 at 6:58:12 PM UTC+1, Israel Hands wrote:
>>
>> Hi, 
>>
>> I use Sync rather than dropbox for my shared data and Sync works by 
>> having a directory on your machine that is nominated to be 'synced' to the 
>> cloud storage. Which is fine but  I quite like having text files in that 
>> shared folder that are used with @auto in a leo file. However because Win 
>> and MacOs refer to directory paths differently I haven't worked out how to 
>> have Leo under MacOs and Win 'see' the same file from the same @auto node. 
>> I hope that makes sense. I wouldn't mind keeping the text files in the same 
>> directory as the Leo files is there a way of making this work?
>>
>> ta
>>
>> IH
>>
>
> I do something like this, under Linux and Windows. I have @file nodes with 
> names like this:
>
> @file .{{sep}}docs{{sep}}myfilename.mwiki
>
> (this is a 'mediawiki' file).
>
> The {{sep}} gets magically converted to '\' under Windows and '/' under 
> Linux. I think there are other keywords available with this {{...}}syntax; 
> look for a thread "cross-platform file references - how to deal with?"
>
> As shown this keeps the @file within the main Leo file directory, under a 
> 'docs' subdirectory in this case; I use it with Owncloud in a similar way 
> to your use of Sync. I presume that with the sue of symbolic links, under 
> Linux at least one could put them somewhere else. However I haven't yet 
> pursued this.
>
> HTH
> Jon N
>
>
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/00a4164e-f754-4b1f-b0d9-3523f658ff58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.