Re: New writer plugins in leo/plugins/writers

On Wed, Jul 30, 2014 at 1:59 PM, 'Terry Brown' via leo-editor wrote: > I'll just assume the outline I grabbed for testing was haunted / > cursed / possessed and move on. When testing I always use --no-cache. Otherwise caching will shortcut things in very confusing ways. Edward -- You receive

Warning: two recent revs change the loading of importer/writers plugins

Revs rev e717fc0... and 3553a9a... could cause problems. This can't be helped for those of us on the bleeding edge. The new code gives priority to plugins in the ~/.leo folder. That is, the new code loads plugins in the leo/plugins/importers and leo/plugins/writers folders only if the corresp

Re: New writer plugins in leo/plugins/writers

On Wed, 30 Jul 2014 12:59:30 -0500 "Edward K. Ream" wrote: > On Wed, Jul 30, 2014 at 11:11 AM, Edward K. Ream > wrote: > >> Can you confirm that @auto-explicit always trumps extension? > > Works for me. Example: @auto-test xyzzy.txt works. Indeed, I have three copies of the same file: md5sum:

Re: New writer plugins in leo/plugins/writers

On Wed, Jul 30, 2014 at 11:11 AM, Edward K. Ream wrote: >> Can you confirm that @auto-explicit always trumps extension? Works for me. Example: @auto-test xyzzy.txt works. But notice, I wrote xyzzy.txt with and @edit node. We probably have to be careful when working with "dummy" plugins. If the

Re: Jedi autocompletion library for python

On Wed, Jul 30, 2014 at 9:54 AM, Fidel N wrote: > Hehe > Didnt find them on google but youtube :D Thanks. EKR -- 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 le

Re: New writer plugins in leo/plugins/writers

On Wed, Jul 30, 2014 at 11:06 AM, 'Terry Brown' via leo-editor wrote: > On Wed, 30 Jul 2014 09:38:19 -0500 > "Edward K. Ream" wrote: >> Unless I am mistaken, writers are always called. > > Only if the file's tree is dirty. Er, right. That's what I meant :-) > Can you confirm that @auto-explic

Re: New writer plugins in leo/plugins/writers

On Wed, 30 Jul 2014 09:38:19 -0500 "Edward K. Ream" wrote: > On Wed, Jul 30, 2014 at 9:14 AM, 'Terry Brown' via leo-editor > wrote: > > > It seems to me that calling the importer and writer on empty files > > should have so little cost in cases where it's unnecessary that it's > > worth doing i

Re: Jedi autocompletion library for python

Hehe Didnt find them on google but youtube :D https://www.youtube.com/watch?v=TNMjbaimk9g https://w ww.youtube.com/watch?v=mflvdXKyA_g On Wed, Jul 30, 2014 at 4:48 PM, Edward K. Ream wrote: > On Wed,

Re: Jedi autocompletion library for python

On Wed, Jul 30, 2014 at 9:42 AM, Fidel N wrote: > just watched some tutorials and I loved it. Thanks for the link. Which tutorials did you watch. I must be google-impaired this morning... Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group.

Re: Jedi autocompletion library for python

just watched some tutorials and I loved it. Thanks for the link. On Wed, Jul 30, 2014 at 4:39 PM, Edward K. Ream wrote: > On Wed, Jul 30, 2014 at 9:23 AM, Ville M. Vainio > wrote: > > Something to evaluate: > > > > https://github.com/davidhalter/jedi > > Thanks for the link. Any help with aut

Re: New writer plugins in leo/plugins/writers

Yeah, I haven't been keeping up with details, but it seems @auto is gaining superpowers, wherein I can equip the node with custom capabilities blah blah nevermind, Edward's message just arrived: empty ok On Wed, Jul 30, 2014 at 9:14 AM, 'Terry Brown' via leo-editor wrote: > On Wed, 30 Jul 2014

Re: Jedi autocompletion library for python

On Wed, Jul 30, 2014 at 9:23 AM, Ville M. Vainio wrote: > Something to evaluate: > > https://github.com/davidhalter/jedi Thanks for the link. Any help with auto-completion is welcome ;-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. T

Re: New writer plugins in leo/plugins/writers

On Wed, Jul 30, 2014 at 9:14 AM, 'Terry Brown' via leo-editor wrote: > It seems to me that calling the importer and writer on empty files > should have so little cost in cases where it's unnecessary that it's > worth doing it just to enable all the "who would have thought of that" > applications

Jedi autocompletion library for python

Something to evaluate: https://github.com/davidhalter/jedi -- 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 thi

Re: Download link for the latest version

On Wed, 30 Jul 2014 06:33:37 -0700 (PDT) duf...@gmail.com wrote: > Hi > I recently re-installed my system, and now I am about to re-install > Leo. > > As far as I know, Leo's latest public version could be downloaded > from this link: > http://www.greygreen.org/leo/leo-editor-latest.zip The info

Re: New writer plugins in leo/plugins/writers

On Wed, 30 Jul 2014 05:19:18 -0500 "Edward K. Ream" wrote: > 2. Nah: ic.createOutline won't call an importer for empty files. > That's just silly. However, if you set trace = True in > ic.createOutline, the traces will tell you whether the read failed > (file did not exist) or returned an empty

Re: Download link for the latest version

The latest version is this one: https://github.com/leo-editor/leo-editor Click "download zip" in the right side of the screen. This is not an exe-installer though. I didnt change my qt installation so dont know about the latest, but according to what I read I would say yes. I would install pyqt

Download link for the latest version

Hi I recently re-installed my system, and now I am about to re-install Leo. As far as I know, Leo's latest public version could be downloaded from this link: http://www.greygreen.org/leo/leo-editor-latest.zip Is this still the link for the most up-to-date version available? Or is there a more u

I may push to git, and *then* do unit tests

I do most of my work on a Windows machine, but I like to run unit tests on my nearby Ubuntu machine. It's much quicker that way. Furthermore, running unit tests on a remote machine is a better test. For example, if I forget to add a new file, things will not be well on the Ubuntu machine. Ot

Leo's pylint command: a major improvement to work flow

When pylint is available on your machine, Leo's pylint command will execute run pylint on all @ nodes in the selected tree. This command is now available from the popup menus created by the contextmenu plugin. This command is a dynamic way of selecting files to check with pylint. It is *much*

Re: New writer plugins in leo/plugins/writers

On Tue, Jul 29, 2014 at 10:20 PM, 'Terry Brown' via leo-editor wrote: > On Tue, 29 Jul 2014 18:20:16 -0700 (PDT) > "Edward K. Ream" wrote: > >> In short, afaik, importers and writers can create their own kinds of >> @auto nodes, as long as they have unique spellings. > > Yep, just overriding run(

Re: custom background color for 'selected/highlighted text'

glad you could solve it Zoltan. On Wed, Jul 30, 2014 at 11:11 AM, Zoltan Benedek wrote: > I've found it. > I should copy the entire node @data qt-gui-plugin-style-sheet and > customize what I want. > > A lot of thanks. > > > > On Wednesday, July 30, 2014 11:52:17 AM UTC+3, Zoltan Benedek wrote:

Re: custom background color for 'selected/highlighted text'

I've found it. I should copy the entire node @data qt-gui-plugin-style-sheet and customize what I want. A lot of thanks. On Wednesday, July 30, 2014 11:52:17 AM UTC+3, Zoltan Benedek wrote: > > Hi Fidel, > > Many thanks for the tip, I can change the color I wanted. > > Unfortunately I have some

Re: custom background color for 'selected/highlighted text'

Hi Fidel, Many thanks for the tip, I can change the color I wanted. Unfortunately I have some font issues with the new setting: the fonts changed in the outline pane and log pane. I copied the entire section QTextEdit#richTextEdit from leoSettings.leo into a node (@settings-->Qt Gui (appearanc