Click links not working

Not sure if these issues are related, but they seemed to coincide with recent Github pulls. 1) Click links no longer triggers the link to open. I can still use the Open URL command in the header right-click menu. That's not helpful if there's more than one link in a node. 2) I get the followin

Re: Stickynote editor behaviour

Issue 249 raised Lewis -- 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.c

Re: It's time for Leo devs to prefer Python 3

On Wednesday, March 30, 2016 at 11:32:50 AM UTC-5, Edward K. Ream wrote: *​Important*: leoGlobals​.py has a number of convenience functions that > make these tests automatically. You should be particularly aware of: > > - g.isBytes, g.isInt, g.isString, g.isUnicode. > - g.toUnicode, g.toEncodedSt

Re: It's time for Leo devs to prefer Python 3

​​On Wed, Mar 30, 2016 at 10:39 AM, Edward K. Ream wrote: > actually getting code to work on 2 and 3 can be fairly tricky. My > preferred way is to do: > > if g.isPython3: > # Python 3-specific code. > else: > # Python 2-specific code. > *​Important*: leoGlobals​.py has a number of con

It's time for Leo devs to prefer Python 3

Imo, it's time for Leo devs to develop and test on Python 3.x. This should no longer be a hardship. The Anaconda distro is available for both 2 and 3 on Windows, Ubuntu and MacOS. Of course, actually getting code to work on 2 and 3 can be fairly tricky. My preferred way is to do: if g.isPytho

Re: Encoded stickynote bug?

On Wed, Mar 30, 2016 at 10:16 AM, 'Terry Brown' via leo-editor wrote: > > The "working latest version" tests were Py 2.7, the "fails older > version" tests were Py 3.x. I think Peter was assuming that the latest > version would also fail in Py 3.x, probably just reported it that way > because of

Re: Encoded stickynote bug?

On Wed, 30 Mar 2016 09:59:02 -0500 "Edward K. Ream" wrote: > On Tue, Mar 29, 2016 at 5:02 AM, Peter Mills > wrote: > > ​> ​ > Works fine: > [Latest version] > > > Fails with exception: [​​Previous versions] > > I don't understand the point of reporting bugs that have already been > fixed. >

Re: Encoded stickynote bug?

On Tue, Mar 29, 2016 at 5:02 AM, Peter Mills wrote: ​> ​ Works fine: [Latest version] > Fails with exception: [​​Previous versions] I don't understand the point of reporting bugs that have already been fixed. Edward -- You received this message because you are subscribed to the Google Group

Re: Stickynote editor behaviour

On Tue, 29 Mar 2016 04:02:55 -0700 (PDT) lewis wrote: > I have been trying out the Stickynote plugin. > In the documentation (Plugins>stickynotes>About) its says "Adds > simple "sticky notes" feature (popout editors) for Qt gui." > This suggests it should behave as an editor. > > When I edit a

Re: Encoded stickynote bug?

On Tue, 29 Mar 2016 03:02:43 -0700 (PDT) Peter Mills wrote: > txt = unicode(txt) > NameError: name 'unicode' is not defined Should be fixed, should have been g.toUnicode(txt), seeing unicode() doesn't exist in Python 3. If you can try the latest commit and confirm, that would be good. Cheers