Re: arrhg, nuance is an idiot!
Perhaps you could copy your python.exe with another name ('leopython.exe,
or ???" and then use a batch file to execute launchleo.py with the new
executable?
I suppose you could even give launchleo.py a custom extension ('.plc' or
some such) and then set the windows file type to autoexecute it with
leopython.exe, then you probably wouldn't need an extra batch file.
On Thursday, March 23, 2017 at 6:32:34 AM UTC-7, Eric S. Johansson wrote:
>
> What does this have to do with Leo? For most of you, nothing. For me, a
> lot.
>
> Summary: got hand disability, use speech recognition.
> Problem: NaturallySpeaking associates grammar elements with the executable
> running. When I run Leo from a git copy, NaturallySpeaking thinks the
> executable is Python!
>
> (BFH)[1]
>
> Need: I need to find a way to make Leo "a windows executable" from
> NaturallySpeaking's perspective. I'm guessing that something like py2exe
> will do this for me.
>
> Is there a build process for Windows executables as part of the Leo
> distribution? If I build Windows executables, would it be helpful to others?
>
> --- eric
>
> [1] a polite abbreviation of a swear of frustration incorporating of
> profanities both scatological and sacrilegious, US and British. I usually
> say this when working with NaturallySpeaking because nuance gives disabled
> users the big middle finger.
>
--
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: leo stalling for long periods
> > I was mistaken, most of my external files are local, but some may be on > network drives. > That said, your setting change seems to have fixed the problem! Perhaps even local files have similar problems on some platforms? -- 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: leo stalling for long periods
All of my external files are on network drives. I'll give that setting change a try. Thanks for the help. On Monday, December 12, 2016 at 12:53:52 PM UTC-8, Curtis Carlsen wrote: > > I downloaded the new code base to try out the new importers. (Leo 5.4, > december 8th) > > I am seeing extended stalling of different parts of the program, where > everything freezes and the program does not respond to keypresses or mouse > clicks. The stall lasts for up to 30 seconds or a minute, then things > start working again. It seems to happen at random intervals. I don't have > to be doing anything, sometimes I am just looking at a node, or navigating > the tree and it freezes. > > I have seen it happen when editting nodes, and also when I am in the > file|import any menu item. It doesn't really seem to matter what I am > doing at the time. And if I run leo from the terminal, I don't see any > error messages there. The file I am editting is fairly large (1.15 MBytes) > > I am running on Windows 7, python 2.7 > > If I revert to using leo 5.1 final from October 20th, the problem goes > away. > > -- 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: leo stalling for long periods
The file consists of hundreds of smaller nodes. There may be a few large nodes, but I find the warning screen about the QT lost data bug annoying so I usually delete them. The original file is my work diary, built up over many months. It has lots of proprietary company data. The boss would not be pleased with me sharing it. I usually close out the diary files after about a year, because they get slow to work with. But the symptoms this time are different. Everything is running along fast and then just stops. It kinda has the feel of a thread getting stalled by a locked resource. I seem to recall some kind of issue with python getting locked up on multiprocessors because of a poorly designed global lock, I have no idea if that could actually be involved, but it's just something I remember. -- 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.
leo stalling for long periods
I downloaded the new code base to try out the new importers. (Leo 5.4, december 8th) I am seeing extended stalling of different parts of the program, where everything freezes and the program does not respond to keypresses or mouse clicks. The stall lasts for up to 30 seconds or a minute, then things start working again. It seems to happen at random intervals. I don't have to be doing anything, sometimes I am just looking at a node, or navigating the tree and it freezes. I have seen it happen when editting nodes, and also when I am in the file|import any menu item. It doesn't really seem to matter what I am doing at the time. And if I run leo from the terminal, I don't see any error messages there. The file I am editting is fairly large (1.15 MBytes) I am running on Windows 7, python 2.7 If I revert to using leo 5.1 final from October 20th, the problem goes away. -- 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.
body text changes from @command script lost when saved?
I have the following code in an @command node:
w = c.frame.body.bodyCtrl
w.setFocus()
start,end = w.getSelectionRange()
w.insert(start, {)
w.insert(end+1, })
c.setChanged()
w.setFocus()
=
It brackets the current text selection with curly braces.
The code seems to work fine at first. The braces appear in the body text.
But when I do a save, the changes are reverted. If I do an edit manually
in the buffer before saving then the changes are retained. It seems that
the changes made by the script are not setting the text as changed. Is
this something to do with the undoer or something else? I've checked in
the docs and searched here, and found nothing relating.
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To view this discussion on the web visit
https://groups.google.com/d/msg/leo-editor/-/88YaBrZtzx0J.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
Re: New ideas re optimizing python
It might be interesting to play with cython to see what parts of Leo could be made faster... -- Ville M. Vainio @@ Forum Nokia Wouldn't it be better to use the python profiler to see where the CPU spends the most time, rather than trying optimization in ad-hoc sections of code? The cprofile program runs most python programs basically at full speed. I've used it several times and it's a lifesaver. From what I've read about Cython, speedups come in two major types: 1) hard typed variables: removes the requirement to translate values and verify data type safety at run time. 2) removing the exception handling overhead: turns out that python's exception system is a bit of a hog(as are most, I think). So Cython uses the C convention of passing back a NULL value on errors in routines that need a boost. It apparently offers some hooks to let the programmer interface between the two exception algorithms. Cython code that doesn't address the above issues tends to run at the same speed as Cpython in the instances I tried. Also, if you are interested in doing safety and type checking in compile time versus run time, the method and class decorators features in python would probably be tailor made for this purpose. Curtis Carlsen -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-edi...@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
