Re: best way to deal with unknow extension in shadow?

[vitalije]

 Warning: changing the @language directive in an @shadow node can cause
 quite a mess if you don't change the file's extension to match the new
 language.  Leo's @shadow code can get totally confused.  I'm not sure
 there is a solution that doesn't cause more complications.

Why Leo don't use for all kinds of files same sentinels in private
files ?
I am not sure, but I think that private files need not be syntax
valid. If Leo used same sentinels for all types of private files, then
changing of @language directive without changing file extension would
not confuse Leo's @shadow code.

Vitalije.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Previous and next similar word completer

[vitalije]

Hello everyone.
In editors that I have used before discovering Leo there were commands
for completing a word with similar word either before or after
insertion point. I could not find those commands in Leo so I have
written them. In case that anybody would like to use them here are
copies of those two nodes.
CUT FROM HERE
?xml version=1.0 encoding=utf-8?
?xml-stylesheet ekr_test?
leo_file
leo_header file_format=2/
vnodes
v t=vitalije.20081125152732.3vh@command complete-previous/vh
v t=vitalije.20081125152732.4vhWordCompleter/vh
v t=vitalije.20081125152732.5 a=Evhcomplete_word/vh
v t=vitalije.20081125152732.6vhlt;lt;backward searchgt;gt;/
vh
v t=vitalije.20081125154636.1vhlt;lt;counter checkgt;gt;/
vh/v
v t=vitalije.20081125152732.7vhlt;lt;clean up and
exitgt;gt;/vh/v
/v
v t=vitalije.20081125152732.8 a=Evhlt;lt;forward
searchgt;gt;/vh
v t=vitalije.20081125154636.1/v
v t=vitalije.20081125152732.7/v
/v
/v
v t=vitalije.20081125152732.9vhacceptable_word/vh/v
v t=vitalije.20081125152732.10vhundo_replacement/vh/v
v t=vitalije.20081125152732.11vhredo_replacement/vh/v
v t=vitalije.20081125152732.12vhexit/vh/v
v t=vitalije.20081125152732.13vhrun/vh/v
v t=vitalije.20081125152732.14vhadjust/vh/v
/v
v t=vitalije.20081125152732.15vhgetCurrentWord/vh/v
/v
/vnodes
tnodes
t tx=vitalije.20081125152732.3wordsep = u'., -+\n\r[]{}lt;gt;=-
+*amp;[EMAIL PROTECTED]\'?/\\|^()~`:;'
word_completer_key = 'back_word_completer'
@others
completer = g.app.config.get(c,word_completer_key,'WordCompleter')
if completer is None:
completer = WordCompleter(p,c,back=True)
g.app.config.set(c,word_completer_key,'WordCompleter',completer)
completer.run()
else:
completer.adjust(p, c.frame.body.getInsertPoint())
completer.complete_word()
/t
t tx=vitalije.20081125152732.4class WordCompleter:
def __init__(self, p, c, back=True):
self.p = p.copy()
self.c = c
self.back = back
self.pos = -1
@others
/t
t tx=vitalije.20081125152732.5def complete_word(self):
txt = self.chunk
word = self.word
try:
if self.back:
lt;lt;backward searchgt;gt;
else:
lt;lt;forward searchgt;gt;
except:
self.exit()
g.es_exception()/t
t tx=vitalije.20081125152732.6p = self.search_pos
start = -1
counter = 0
while p:
lt;lt;counter checkgt;gt;
i = txt.rfind(word, 0, start)
if i == -1:
p.moveToThreadBack()
if p:self.chunk = txt = p.bodyString()
start = -1
else:
if self.acceptable_word(i, txt, word):
self.chunk = txt[:i+len(word)-1]
return
start = i+len(word)-1
lt;lt;clean up and exitgt;gt;/t
t tx=vitalije.20081125152732.7if len(self.tried) gt; 1:
# there was some tries so we need to restore
self.c.setBodyString(self.p, self.before+self.word+self.after)
self.c.frame.body.setInsertPoint(self.pos)
return self.exit()/t
t tx=vitalije.20081125152732.8p = self.search_pos
start = 0
counter = 0
while p:
lt;lt;counter checkgt;gt;
i = txt.find(word, start)
if i == -1:
p.moveToThreadNext()
if p:self.chunk = txt = p.bodyString()
start = 0
else:
if self.acceptable_word(i, txt, word):
self.chunk = txt[i+1:]
return
start = i+1
lt;lt;clean up and exitgt;gt;/t
t tx=vitalije.20081125152732.9@ if found word for the first time
then try it
@c
def acceptable_word(self, i, txt, word):
if i == 0 or wordsep.find(txt[i-1]) != -1:
j = i+len(word)
while j lt; len(txt) and wordsep.find(txt[j]) lt; 0:
j += 1
nword = txt[i:j]
if nword not in self.tried:
self.tried[nword] = 1
u = self.c.undoer
bunch = u.createCommonBunch(p)
bunch.oldBody = p.bodyString()
bunch.insertPos = self.pos
# Set the type amp; helpers.
bunch.kind = 'node'
bunch.undoType = 'complete word'
bunch.undoHelper = self.undo_replacement
bunch.redoHelper = self.redo_replacement
bunch.newBody = newBody = self.before+nword+self.after

self.c.setBodyString(self.p, newBody)
self.c.frame.body.setInsertPoint(self.pos)

bunch.dirtyVnodeList = [p.v]
bunch.newChanged = u.c.isChanged()
bunch.newDirty = p.isDirty()
bunch.newMarked = p.isMarked()

u.pushBead(bunch)

return True
return False
/t
t tx=vitalije.20081125152732.10def undo_replacement(self):
u = self.c.undoer; c=self.c; p=u.p
bunch = u.getBead(u.bead)
c.setBodyString(p, bunch.oldBody)
c.frame.body.setInsertPoint(bunch.insertPos)/t
t tx=vitalije.20081125152732.11def redo_replacement(self):
c = self.c; u=c.undoer; bunch=u.getBead(u.bead+1)
c.setBodyString(bunch.p, bunch.newBody)
c.frame.body.setInsertPoint(bunch.insertPos)/t
t tx=vitalije.20081125152732.12def exit(self):
# this was used during

Re: Previous and next similar word completer

[vitalije]

  Could you put them on Leo's wiki?

 Edward

Done. Here is a link: http://leo.zwiki.org/CompletePreviousOrNextMatchingWord
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Previous and next similar word completer

[vitalije]

I have just noticed that when I copy this script from wiki, and paste
it in to new Leo file, nodes that were clones become ordinary nodes.
Nodes with the same heading were actually clones.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Previous and next similar word completer

[vitalije]

No, losing clones was my mistake.
I  have changed now page in wiki so that clones are still clones.
There was also small bug in my script that is now fixed :-)
Vitalije
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Unicode decode error [Bug #313288]

[vitalije]

There is a bug in leoAtFile module. I found that someone has already
reported that bug at launchpad with a number #313288.
When saving outline with a @thin node with non ASCII character, I am
getting UnicodeDecode error.
I use Tk interface.
I found that this bug was introduced in revision 1368.
Maybe it would help to solve a bug.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: Unicode decode error [Bug #313288]

[vitalije]

 I'll take time out from redraw follies to fix this today in the trunk.

Fixed in revision 1405.
It works o.k. for me now.
Thanks.
Vitalije
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: fast-color branch now merged with the trunk

[vitalije]

On Feb 10, 2:43 pm, Edward K. Ream edream...@gmail.com wrote:
 Rev 1537 of the trunk contains the merge of the fast-color branch into

 Please report any problem immediately.  Thanks.

Hi. I have just tried new qt plug-in and found out that when I select
any node that has some characters from unicode range, for the first
time it is displayed correct, but when I select another node and then
select again first node, unicode text is replaced by ?.
I am using Windows Vista
Leo Log Window...
Leo 4.5.1 final, build  1.244 , September 14, 2008
python 2.5.1, qt version 263169
Windows 6, 0, 6001, 2, Service Pack 1
Rev 1537

Vitalije
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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
-~--~~~~--~~--~--~---

@chapter problem with qt

[vitalije]

Hi. I have just tried new qt plug-in and found out that when I open a
leo file with chapters, I can see in outline on the top node with
headline @chapters. But when I click in any node, the @chapters node
disappears and when I execute mini-buffer command select-chapter I can
not see selected chapter until I click in top node in outline.

I am using Windows Vista
Leo Log Window...
Leo 4.5.1 final, build  1.244 , September 14, 2008
python 2.5.1, qt version 263169
Windows 6, 0, 6001, 2, Service Pack 1
Rev 1537

Vitalije
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: fast-color branch now merged with the trunk

[vitalije]

Actually this bug was introduced in revision 1447 if this information
would be helpful.
Vitalije.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: fast-color branch now merged with the trunk

[vitalije]

 Rev 1537 of the trunk contains the merge of the fast-color branch into
 Please report any problem immediately.  Thanks.

Hi. I have just tried new qt plug-in and found out that when I select
any node that has some characters from unicode range, for the first
time it is displayed correct, but when I select another node and then
select again first node, unicode text is replaced by ?.
I am using Windows Vista
Leo Log Window...
Leo 4.5.1 final, build  1.244 , September 14, 2008
python 2.5.1, qt version 263169
Windows 6, 0, 6001, 2, Service Pack 1
Rev 1537

Actually this bug was introduced in revision 1447 if this information
would be helpful.
Vitalije.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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
-~--~~~~--~~--~--~---

Can't type non ASCII characters in qt body

[vitalije]

Hi.

I can't type any non ASCII character like Виталије in Leo's body
when using Qt gui.
Instead of characters that I type Leo shows only ?-s. It displays
correct text that I have typed in using Tk as gui.

If it would help the this bug was introduced in revision 1527.
Although in that revision Leo was corrupting body text of nodes that
contain non ASCII characters. It displays correct body text when node
is first selected, but after selecting another node and then selecting
again node with non ASCII characters, all those characters are
replaced with ?-s. That behavior is since revision 1447.

I have also noticed that when in Qt gui, after changing chapter by
using command select-chapter there is no visible change in outline,
until I manually call c.redraw(). That is confusing.

I am using revision no. 1588.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: Can't type non ASCII characters in qt body

[vitalije]

Thanks for advise.

Indeed, creating sitecustomize.py with sys.setdefaultencoding('utf-8')
in it solved problem,
but ojn the other hand I agree that Leo should not require such a hack
from user in order
to work properly.

Vitalije.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: Moving clones

[vitalije]

On Mar 9, 7:30 am, Jesse Aldridge jessealdri...@gmail.com wrote:
 Is there an easy way to move a clone node over a long distance?  I see
 that when a clone is pasted after cutting or copying it is no longer a
 clone, but just a regular node.

I think you should use command Paste Node as clone from outline menu
instead of Paste Node.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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
-~--~~~~--~~--~--~---

found bug in mod_scripting.py

[vitalije]

I have just found bug in mod_scripting plugin. On line 299 there is a
call to method


299: b = self.createAtButtonFromSettingHelper
(h,script,statusLine,shortcut)

but, that method has following declaration on line 301

301: def createAtButtonFromSettingHelper
(self,args,h,script,statusLine,shortcut,bg='LightSteelBlue2'):

As you can see that method has declared at least 6 arguments, but in
calling line there are just 5 arguments (invisible self + 4 others).

I have looked few lines after and found that args from method
declaration is never used in method body. Actually original value of
that argument is rewritten in line 310

310: args = self.getArgs(h)

So, imo, declaration of method should be changed like this

def createAtButtonFromSettingHelper
(self,h,script,statusLine,shortcut,bg='LightSteelBlue2'):

Vitalije.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: Big @shadow collaboration Ahas! Just make it work

[vitalije]

Maybe the solution for using @shadow in collaborative environment like
bazaar could be found in developing some bazaar plug-in for push /
pull that would cope with @shadow and private files.

In repository should be kept private files (with sentinels).
The plug-in should be able to pull either private or public files at
users will.
When a programmer that uses Leo is committing the plug-in would
actually commit private files.
When a programmer that doesn't use Leo is committing the plug-in would
take public files, and record any changes in private files.
If it encounters any problem during synchronization process plug-in
can insert some special nodes with a list of found problems that Leo
users would see when they pull from repository next time.

Vitalije

--

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.

paste node as clone seems broken

[vitalije]

Hello
I think that menu command Outline - Paste node as a clone (Alt+Ctrl
+V) seems that has no effect at all.

It is possible to create clone and to move it around but it is not
very handy when I have to move it far away.

I thought that maybe I missed something in this group (maybe it was
intentionally changed) so I have looked in the users guide. There I
found in chapter 3 a section titled Dragging nodes that says that it
is possible to drag nodes with mouse, but it is not true for the Qt
gui. Maybe there should be a note about differences in Qt gui.

This morning I found that a mini buffer command 'paste-retaining-
clones' actually works, but although log window shows that it has a
shortcut all:(Alt+Ctrl+V) - that shortcut is not functioning.

from log window:
Leo 4.7 final, build 2985, February 23, 2010
Python 2.6.1, qt version 4.6.1
Windows 6, 0, 6001, 2, Service Pack 1

-- 
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.

Re: paste node as clone seems broken

[vitalije]

I have found what was causing trouble :-)

Putting @bool enable_alt_ctrl_bindings = True in myLeoSettings.leo
solved the problem.

It is interesting that in leoSettings.leo there is no such setting. I
couldn't find any thing in documentation either about it. I was lucky
to find it through auto-completion. When I entered c.k.e
enable_alt_ctrl_bindings was in auto-complete list, stating that its
value is None. So, I searched for that string in leoSettings and in
core/*.py ...

-- 
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.

Re: paste node as clone seems broken

[vitalije]

 Paste node and paste node as clone only work if you have copied a node
 (or tree of nodes).  Leo's qt plugin should enable or disable menu
 items, but it doesn't.

Yes, I knew that, but paste node as a clone didn't produce any effect,
while paste node did. As I have written above, problem was with
setting that forced ignoring key combinations with Alt and Control.

-- 
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.

Re: Should mod_autosave.ini be a versioned file?

[vitalije]

On Mar 6, 1:51 pm, vitalije vitali...@gmail.com wrote:
  The Leonine solution would be to put these settings in leoSettings.leo
  (that is, myLeoSettings.leo).

  Anyone want to do this?  I'll be happy to provide hints as needed.

  Edward

 I would like to try to do it.

Done at my local branch.
What should I do next?

-- 
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.

Recent change in leoTest has broken some of my tests

[vitalije]

Hello
a recent change in leoTest

+# 2010/03/05: set the current directory so that importing
leo.core.whatever works.
+leoDir = g.os_path_finalize_join(g.app.loadDir,'..','..')
+os.chdir(leoDir)

solved the problem of importing leo.core but, also introduced new
problems with tests that rely on current dir == path to leo file.
In order to solve the first problem of importing leo.core I have
created leo.pth file with the path to leoDir and stored it in site-
packages.
Maybe it would be better to add leoDir to environment before running
new process. Something like this:

leoDir = g.os_path_finalize_join(g.app.loadDir,'..','..')
env = dict(os.environ)
env['PYTHONPATH'] = env.get('PYTHONPATH', '')+';'+leoDir
os.spawnve(os.P_NOWAIT,sys.executable,args,env)

At least this works on my machine.

-- 
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.

Re: Should mod_autosave.ini be a versioned file?

[vitalije]

On Mar 6, 9:16 pm, Edward K. Ream edream...@gmail.com wrote:
 On Sat, Mar 6, 2010 at 7:42 AM, vitalije vitali...@gmail.com wrote:
  Done at my local branch.
  What should I do next?

 Run all unit tests and push to the trunk when they pass.

 Edward

I have ran all unit tests and they passed.
When I tried to do bzr push I got following error:
Using saved push location: bzr+ssh://bazaar.launchpad.net/~leo-editor-
team/leo-editor/trunk/
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.
bzr: ERROR: Cannot lock LockDir(lp-66527888:///~leo-editor-team/leo-
editor/trunk/.bzr/branchlock): Transport operation not possible:
readonly transport

I suppose that I need some permission,,, or not?

-- 
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.

Re: Should mod_autosave.ini be a versioned file?

[vitalije]

 ... or you can do bzr bundle and attach the resulting patch to a bug
 in launchpad.

 --
 Ville M. Vainiohttp://tinyurl.com/vainio

Done. I have reported bug #533546
and attached bundle to it.

-- 
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.

Re: Recent change in leoTest has broken some of my tests

[vitalije]

I have reported another bug  #533546 related with autosave plugin.
I have attached to it patch that solves this problem.

-- 
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.

Re: avoid writing parts of the contents to a file

[vitalije]

This is a FAQ.
You should read 
http://webpages.charter.net/edreamleo/FAQ.html#using-external-files
There is a FAQ entry: Can @file trees contain material not in the
external file?
and also: Why can’t I use @ignore directives in @thin trees?

I hope this would help.
Vitalije

-- 
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.

Re: error in leo.plugins.mod_scripting

[vitalije]

 Hmm, I was touching this code recently, adding the Goto Script and button 
 submenu stuff.

 But it's working for me bzr revno = 3169.

I have noticed the same error. I think it happens only if you have
@button or @command nodes somewhere in @settings tree.

I think that you should look at two methods
createAtButtonHelper
and
createAtButtonFromSettingHelper

in one of them there is a class representing callback function that
has attribute p. In the other one there is no such a class.

HTH

-- 
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.

Re: error in leo.plugins.mod_scripting

[vitalije]

 Let me know if it works.

Works for me on rev no. 3171 :-)

Vitalije

-- 
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.

bug in leoTest.py: os dependent code

[vitalije]

Hello,
I have found error in leoTest.py line 665:
env['PYTHONPATH'] = env.get('PYTHONPATH','') + ; + leoDir

it works fine on Windows, but on Linux it doesn't.
A solution would be to replace ; in the line with os.pathsep

I am having troubles with bzr so I cant push
and hope someone else will push this change in repository.
TIA
Vitalije

-- 
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.

unit testing increases number of registered handlers

[vitalije]

Hello,
while I was experimenting with registering handler for idle events,
I have noticed
that there were about 40 registered handlers for idle event. What
was most interesting is the fact that those handlers were all about
the same function onIdle in mod_autosave plugin. At first I thought
that handler is registering itself over and over, but when I looked in
the source I couldn't find anything suspicious.

So I made small script to print number of registered handlers and
manually executed it from time to time to see when it increases.

g.es(len(g.app.pluginsController.getHandlersForOneTag(idle)))

Finally, I realized that every time when I invoke unit test command Alt
+5, number of registered handlers increased.

From the above it is obvious that I have enabled plugin mod_autosave.
From the Log
Leo Log Window
Leo 4.8 final, build 3752, November 26, 2010
Python 2.6.6, qt version 4.7.0
linux2

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: A question about using leo to create unit tests

[vitalije]

I guess you need to put @test Foo in headline of the test node.
In the body you could put something like this:

import foo
f = Foo()
self.assertEqual(Foo.somemethod(), value)

or whatever you want to test

than you press Alt+5 and the results of your tests will be written in
the terminal window, therefore you must start Leo from terminal (if
you use Windows, you must start Leo using python.exe not pythonw.exe

HTH
Vitalije

On Feb 20, 9:56 pm, rulfzid rulf...@gmail.com wrote:
 My question is basically: how do I get my @unit tests to look at my code?

 For example, say I have a simple tree that looks like:

 - code
 | - @file foo.py
 - tests
 | - @unit Test Foo creation

 When I try to run the tests now, it doesn't recognize the name Foo (defined
 as a class in foo.py), even if I toss an import foo in there. I suspect
 there's something simple I'm missing, but I'm not sure what it is.

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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.

colors in headline edit

[vitalije]

Hello,
I have noticed recently an ugly combination of colors in headline
while editing that was introduced by updating Leo. Background is very
dark and text color is also dark so that it is quite unreadable. I
haven't had enough time to inspect default settings till this morning.
Today I realized that when I start editing headline with Ctrl+h (that
is the usual way I use) both colors (background and foreground) are
dark, but when I double click in headline I see colors from
myLeosettings file.

I am using:
Leo 4.8 final, build 3752, November 26, 2010
Python 2.6.6, qt version 4.7.0
linux2

bzr revno gives me 3904

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: colors in headline edit

[vitalije]

Also I can't figure how to change color of  ( and ) in
actionscript language. I like dark background with the light text and
that is the color scheme I have in myLeosettings. But ( and ) are
black and that is not compatible with my dark background color.

The only two colors in leoSettings (in syntax coloring nodes)  that
are black are 'tab_color' and 'operator_color'. I have tried to change
both of them but with no success. Leo sees my settings for tab_color
and operator_color but those settings have no influence on ( and
) .

In nodes where @language python is in effect ( ) are white, but in
nodes with @language actionscript those characters become black and I
can't find which setting I should change.

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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.

revno 3914 introduced bug in key handling

[vitalije]

Hello,
I have updated Leo to the revno 3930 and noticed that I can't type
letters other than ASCII anymore.

With a little investigation I found that revno 3914 introduced bug.
A revno  3914 log says:
  Changes for QCompleter.  More are coming.

  - Changed name from QTextBrowserSubclass to LeoQTextBrowser.
  - Add do-nothing keyPressed Event.
  - Began to update the example code in test.leo.

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: revno 3914 introduced bug in key handling

[vitalije]

revno 3936 works for me also. :-)
Thanks.
Vitalije

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: colors in headline edit

[vitalije]

Today I have updated my Leo and with the revno 4001 the problem is
still present.
And also I haven't found answer on the question about configuring
colors of  parenthesis.
I understand those questions are not so high priority but I am just
asking again here in case they got forgotten.
Vitalije.

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: colors in headline edit

[vitalije]

 I've just added this to the action-items list, which means they are
 likely to be fixed first.
Thank you Edward. There was a question in this thread that I still
need an answer, so I will repeat it again.

I can't figure how to change color of  ( and ) in
actionscript language. I like dark background with the light text and
that is the color scheme I have in myLeosettings. But ( and ) are
black and that is not compatible with my dark background color.

The only two colors in leoSettings (in syntax coloring nodes)  that
are black are 'tab_color' and 'operator_color'. I have tried to change
both of them but with no success. Leo sees my settings for tab_color
and operator_color but those settings have no influence on ( and
) .

In nodes where @language python is in effect ( ) are white, but in
nodes with @language actionscript those characters become black and I
can't find which setting I should change.

Vitalije

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: colors in headline edit

[vitalije]

 The fix is on the trunk at rev 4109.  The actionscript colorizer now
 colorizes parens like operators.  For example::

Thanks for this one.
I have tried to disable @data qt-gui-plugin-style-sheet as you have
suggested and colors were changed, but strange behavior was still
present. When I double click in headline I see one set of colors and
when I press Ctrl+H, I see different set of colors (background,
foreground and selection background, selection foreground).
I am using Ubuntu 10.10
Leo Log Window
Leo 4.8 final, build 3752, November 26, 2010
Python 2.6.6, qt version 4.7.0
linux2
revno 4123

I think that colors for editor created by Ctrl+H key combination are
the same regardless of enabling or disabling stylesheet in
myLeosettings.

I am just thinking loud. May be it is PyQt related.  Is Leo
responsible for creating headline editor in both cases (double click
and keyboard shortcut) or may be PyQt is responsible for creating
double click editor? If so, how can we tell PyQt to respect our color
settings? As mater of fact, double click created editor looks fine.
The other one does not.

Vitalije

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: colors in headline edit

[vitalije]

 You might want to put a call to g.trace(e) in getTreeEditorForItem to
 see what widget you are actually getting.

I have done as you suggested. Whenever I press Ctrl+H, I can see
several lines in terminal some of them says e is None and some of them
says it is QLineEdit.
Here is output:
...
getTreeEditorForItem None
getTreeEditorForItem PyQt4.QtGui.QLineEdit object at 0xaa3806c
getTreeEditorForItem PyQt4.QtGui.QLineEdit object at 0xaa3806c
getTreeEditorForItem PyQt4.QtGui.QLineEdit object at 0xaa3806c
getTreeEditorForItem PyQt4.QtGui.QLineEdit object at 0xaa3806c
getTreeEditorForItem PyQt4.QtGui.QLineEdit object at 0xaa3806c
getTreeEditorForItem None
...
But, when  I double click at headline I have editor but nothing in the
output.

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: Exceptions in recent revisions

[vitalije]

revno 4275:
When executing script that uses c.executeMinibufferCommand
for example: c.executeMinibufferCommand('save-file')
produces the following log
NameError: global name 'stroke' is not defined

  line 697: # stroke = None
* line 698: event =
g.app.gui.create_key_event(c,None,stroke,w)
  line 699: k.masterCommand(event,func,stroke)
  line 700: return k.funcReturn
exception executing script


revno:4284
The same script produces the following log
TypeError: masterCommand() takes at least 4 arguments (3 given)

  line 718: event =
g.app.gui.create_key_event(c,None,None,None)
* line 719: k.masterCommand(event,func)
  line 720: return k.funcReturn
  line 721: else:

and revno: 4288 at the start up produces the following log:
Leo Log Window
Leo 4.9 beta 2, build 4265, June 4, 2011
Python 2.7.1, qt version 4.7.2
linux2
setting leoID from os.getenv('USER'): 'vitalije'
load dir: /home/vitalije/programi/leo-editor/trunk/leo/core
global config dir: /home/vitalije/programi/leo-editor/trunk/leo/config
home dir: /home/vitalije
reading settings in /home/vitalije/programi/leo-editor/trunk/leo/
config/leoSettings.leo
reading settings in /home/vitalije/programi/leo-editor/trunk/leo/
config/myLeoSettings.leo
unexpected exception in g.getScript
Traceback (most recent call last):
  File /home/vitalije/programi/leo-editor/trunk/leo/core/
leoGlobals.py, line 4481, in getScript
useSentinels=useSentinels)
  File /home/vitalije/programi/leo-editor/trunk/leo/core/
leoAtFile.py, line 3305, in writeFromString
c.endEditing() # Capture the current headline, but don't change
the focus!
  File /home/vitalije/programi/leo-editor/trunk/leo/core/
leoCommands.py, line 7415, in endEditing
c.frame.tree.endEditLabel()
  File /home/vitalije/programi/leo-editor/trunk/leo/core/
leoFrame.py, line 2289, in endEditLabel
self.onHeadChanged(p)
  File /home/vitalije/programi/leo-editor/trunk/leo/core/
leoFrame.py, line 2211, in onHeadChanged
if not c.changed: c.setChanged(True)
  File /home/vitalije/programi/leo-editor/trunk/leo/core/
leoCommands.py, line 7234, in setChanged
if g.app.gui.guiName().startswith('qt') and g.app.qt_use_tabs and
hasattr(c.frame,'top'):
AttributeError: 'NoneType' object has no attribute 'guiName'

I am using ubuntu 11.04
HTH
Vitalije

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: Exceptions in recent revisions

[vitalije]

Regarding the exception introduced in revno 4288, I have found
solution

 leoCommands.py, line 7234, in setChanged
     if g.app.gui.guiName().startswith('qt') and g.app.qt_use_tabs and
 hasattr(c.frame,'top'):
 AttributeError: 'NoneType' object has no attribute 'guiName'


I think that the boolean expression in the above line (7234) should
start with g.app.gui and ...
it should be:
if g.app.gui and g.app.gui.getName().startswith(qt) and
g.app.qt_use_tabs and hasattr(c.frame,'top'):

It seems that the method setChanged get called before g.app.gui is
created.

Regarding the rest of exceptions they disappeared when I updated my
Leo to current revno  4302

Vitalije

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: Blender interface scripting

[vitalije]

I am not sure about Windows 7, but I have noticed in Windows Vista that 
Program Files folder doesn't accept changes unless you are running program 
as administrator. All changes that program make in subtree of C:\Program 
Files\ are stored in subfolder of C:\Documents and 
Settings\username\AppData\Roaming\... That's why I used to install almost 
all programs not in default location C:\Program Files\ but in some other 
like C:\myprograms\ .
HTH
Vitalije

-- 
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/-/D4pChqFrznkJ.
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: Blender interface scripting

[vitalije]

Blender is self contained folder that you can put anywhere and doesn't 
require any other registration or installation to work. So I guess it would 
be best if you move (or copy) your blender installation folder somewhere 
else in ordinary writable folder.
Vitalije

-- 
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/-/0fa7cfdc34QJ.
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.

@test assert True fails !?

[vitalije]

Hello!
I have recently noticed strange behaviour of testing in Leo. Somehow tests 
run ok, but they are still reported as broken.
Even a node with headline '@test example' and body of just one line 'assert 
True' is reported as FAILD
Here is traceback:

File .../leo-editor/trunk/leo/core/leoCommands.py, line 7056, in 
recolor_now
c.frame.body.colorizer.colorize(p,
AttributeError: 'NoneType' object has no attribute 'colorize'

--
Ran 1 test in 0.004s

FAILED (errors=1)

Revision 4591, Ubuntu 11.04, Python 2.7

Vitalije.

-- 
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/-/gXfrgrijmAoJ.
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: @test assert True fails !?

[vitalije]

I do test externally all the time and haven't noticed the above problem 
until recently.
Anyway, thanks for the fix.

PS: I don't think that assert True need any gui related function as many 
other tests. In fact I use a lot of tests just to execute some code without 
writing script file and then running it from console

-- 
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/-/kVF2Z01zfxUJ.
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: @test assert True fails !?

[vitalije]

Did I cause appearing of this problem with enabling a new plug-in previously 
disabled? (I really did change @enabled plug-ins setting recently)

I would prefer if it would be possible to launch tests externally without 
loading plug-ins.

As I see in Code--Testing--@file leoTest.py--runUnitTestLeoFile
and in Code--Testing--@file leoTest.py--class 
runTestExternallyHelperClass--runTests

there is an option to set gui for testing (g.app.unitTestGui) and default is 
'nullGui'.

Maybe there could be an option to disable loading of plug-ins also ?

For the tests that I mostly write and run, loading plug-ins is just wasting 
time.
Vitalije.

-- 
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/-/j_GXynXIzZkJ.
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: viewrendered - file not found

[vitalije]

Maybe Leo could deduce by the first character of path whether it is 
absolute or relative path. Than if it is absolute it computes relative to 
root of leo file. In pseudo code:

def root_of_leo_file():
  if os.name == 'posix':
 return '/'
 elif os.name == 'nt':
 return c.fileName()[:3]
 elif ..other names

def calculate_path(fname):
 if fname.startswith((/,\\):
___# absolute path
___return os.path.join(root_of_leo_file(), fname)
 return os.path.join(os.path.dirname(c.fileName()), fname)

my 2 cents
Vitalije

-- 
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/-/sTKVKMhbgS8J.
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: Weightless unit tests: the holy grail has been found

[vitalije]

Maybe it would be simplest to add argument '--test-externally' in 
Code--Testing--@file leoTest.py--runUnitTestLeoFile
just before spawning new process, and than check for such option in 
processing command line's arguments.
Vitalije

-- 
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/-/qSxqjdO1FAwJ.
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: viewrendered - file not found

[vitalije]

Is it too late to claim English isn't my first language?  :-}
neither is my first language.

I didn't think that /etc/hosts should be resolved as /home/.../etc/hosts
My idea was that we should deduce root folder as root of Leo file. On linux 
machines it would be '/', while on windows it would be Drive:\ . 
Concatenating, that way deduced root with the given absolute path in 
heading we would get correct absolute path on both windows and linux. I 
have no idea what would be correct on Macintosh but, AFAIK support for Mac 
is given up recently. Maybe some Mac users could suggest solution.

I agree that current directory has no meaning in Leo. As a matter of fact 
executing script could easily change cwd. OTOH folder of Leo file has 
unique meaning on both systems and root of absolute path to Leo file is 
something that we could define on:

   1.  Windows as Drive letter:\
   2. Linux as /
   

I did forget network paths like  \\machine\share\path\file.leo. That 
could be the 3rd case where root folder is computed as \\machine\share\

On my Ubuntu samba shares are mounted as ~/.gvfs/sharename, so I guess that 
on linux we should check for special case if absolute path to leo file 
starts with ~/.gvfs/sharename/  then root should be computed as 
~/.gvfs/sharename/

PS: reading again what I've just written I am not sure that I made it 
understandable at all. If it's not clear I am sorry...

-- 
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/-/7u9G10FSfPYJ.
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: viewrendered - file not found

[vitalije]

Ah - and now I think this last point was the point you were making, and
perhaps we agree?

I think we were talking the same thing. 

 Given a .leo file C:\myproject\project.leo, what does @auto 
A:projectnotes.txt mean?

IMHO perfectly nothing. I can't imagine a use case where one would like to 
have path that way defined.

and you're suggesting they should be relative to the root of the 
filesystem containing the .leo file,
No, that wasn't my suggestion. I suggested that only absolute paths that 
have no specified drive should be appended to the *root folder* where 
root folder has different meaning on different platforms. I wouldn't expect 
to break any existing outline, because relative paths would still be 
computed the same way they are computed now.

I hope this was a bit clearer.
Vitalije

PS: When there was discussion in this group about the above bug a while 
ago, I had this idea but I didn't post it because I was expecting that 
someone else would solve it anyway. Reading this thread I noticed that the 
bug is still present and decided to post my suggestion hoping it would 
help. I don't use windows any more and this bug doesn't affect my work 
flow  at all.

-- 
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/-/owBcVmJNIHwJ.
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: leoInspect: remarkable collapse in complexity and attempted assessment

[vitalije]

 Otoh, playing with the getters has exposed the difference between
 queries and far more capable programs such as pylint.  Queries may be
 useful for some purposes, but pylint is essentially a way of making
 *automatic* queries/inferences about *all* the objects in a program.

 The leoInspect project is about to run into a wall:  text-based
 queries are not nearly as useful as object-based or type-based
 queries.  Such queries require sophisticated type analysis of the kind
 that I (temporarily!) abandoned at the start of the leoInspect
 project.

Have you considered using leoInspect as a base to build some kind of 
refactoring tool(set)?
I think that leoInspect is already very useful tool for refactoring code 
manually. I believe it is possible to make some scripts using leoInspect to 
perform some kinds of refactoring. For example *extracting function* type 
of refactoring requires to check for the assignments to variables in 
selected code block and check whether some of assigned variables are used 
after selected code block. Such variables should be returned from extracted 
function. All variables used in selected code block should become input 
arguments of the extracted function. If I am not mistaken, those are 
queries that leoInspect module could answer already.
Vitalije
PS: there is a project bicyclerepair 
http://sourceforge.net/projects/bicyclerepair/ but newest release is from 
2004 :-(

-- 
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/-/vLyWiq1I-DkJ.
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.

k.insert_mode_bg_color = white and settings are ignored

[vitalije]

Today I have updated my Leo version and found that it is almost
impossible to use it because I used to have syntax colors for text
rather light and background used to be dark. Now whenever I try to
type text in Leo body it become white. I have searched through Leo
sources and found that in keyHadlerClass.__init__ those colors are
hard-coded with note that real values should be replaced in
k.finishCreate method. However, those hard-coded values for colors are
not changed in finishCreate.

Vitalije

-- 
You received this message because you are subscribed to the Google Groups 
leo-editor group.
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: k.insert_mode_bg_color = white and settings are ignored

[vitalije]

I have noticed this bug in revision 5030.

Vitalije

-- 
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/-/MNQkriJUQCsJ.
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.

Old Extract section and new extract commands are different

[vitalije]

A long time ago in Leo there were two commands with similar effect 
extract-section and extract-method. Then they were replaced with the 
extract command. When extracting method or function that is included by 
@others directive everything is working as it should. But when for example 
one want to extract section that is indented then reference line section 
name, after extraction, is moved to the beginning of line. I would expect 
that the section reference should stay where it was before extraction, i.e. 
indented.

Searching in Leo's source I have found what should be changed.

Code--Core classes--@file leoCommands.py--class commands--Command 
handlers...--Edit Menu...--Edit Body submenu--c.extract...--extract  
helpers : line 29 is

h,b,middle = ref_h,lines[1:],lines[0]

but should be (IMHO):
 

h,b,middle = ref_h, lines[1:], ' ' * ws +lines[0]

ws is calculated before and it is number of spaces before section reference 
line

I hope this would eventually be changed in future versions of Leo.

Vitalije

-- 
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/-/KAX2E-Egi3AJ.
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.

ImportError: No module pstats in revno 5035

[vitalije]

On one of my machines [Ubuntu 11.04] was not installed python-profiler 
package. When I updated Leo's installation to revision 5035, I got 
trace-back in terminal complaining that pstats module is missing and Leo 
exited. After installing python-profiler package everything is working 
fine. I suppose that this is not really required but was left after some 
testing phase.

Vitalije

-- 
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/-/vlyDbB8JR3wJ.
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: ctrl-v (paste) problem

[vitalije]

 Has anyone else been seeing similar problems?


I use Ubuntu 11.04 and have noticed some problems with Ctrl+... shortcuts 
in some applications. If I press left Alt and then Ctrl, and then release 
Alt, but still holding Ctrl down, then press key for Ctrl+ combination ( 
Ctrl+z, Ctrl+v, ...), shortcut is executed but when I try to press just 
Ctrl and z I get same as pressing just z. I haven't noticed that behavior 
with Leo though. 

Seeking for the cause of this kind of problem I found that some of applets 
in panels can cause very strange behavior so try to disable some of them. 
One that is quite disturbing is indicator applet that integrate main menu 
of active application in top panel. It is causing a nasty bug that was 
discussed recently in other thread.

HTH
Vitalije

-- 
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/-/b2nFXOBFcrsJ.
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.

no @test or @suite nodes in selected outline

[vitalije]

Hello
IIRC in earlier version of Leo if one runs test externally with the 
selected position under @test node, that @test was executed. That was very 
convenient during the development of test code itself.
Actually I used to perform some tasks like manipulating files, transforming 
files, communicating with http server,... using Leo's command run tests 
externally. That's why I find it very convenient to edit code in nodes 
under @test and then hit key for executing tests. Now I have to switch to 
@test node before executing tests :-
I have noticed this behaviour in recent revisions.
Vitalije

-- 
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/-/FUTZbuCabeQJ.
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: no @test or @suite nodes in selected outline

[vitalije]

 I have noticed this behaviour in recent revisions.

 
I tried with reverting code and have found that:

   1. revision 4987 Leo executes tests as I expected
   2. in revisions 4988-4990 Leo throws some exception
   3. in revision 4991 Leo complains that there are no @test or @suite 
   nodes under selected outline

HTH

Vitalije

-- 
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/-/kuzY3xmRZecJ.
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: no @test or @suite nodes in selected outline

[vitalije]

Sorry I forgot to write the wrong behaviour is still present in revision 
5202.

-- 
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/-/An1hXUknl2kJ.
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: no @test or @suite nodes in selected outline

[vitalije]

No Leo still forces me to select top @test node before executing 
tests.(revno 5210)

I use command run-selected-tests-externally not 
run-marked-unit-tests-externally.

To be more precise: I expect that command run-selected-tests-externally 
search for @test and @suite nodes in subtree, but if it doesn't find any 
such node, then it should search parents of selected node and if it finds 
parent with @test headline, it should run that found test.

As I said before, Leo used to work that way until revision 4988.

Vitalije

-- 
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/-/_61WTstR-8cJ.
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: no @test or @suite nodes in selected outline

[vitalije]

I think I found method that should be fixed.
LeoPyRef.leo#Code--Testing--@file leoTest.py--class 
TestManager--TM.Utils--TM.findAllUnitTestNodes

There is block of code
 
 

# An important special case: add the *selected* @test or @suite node,

# regard regardless of all other considerations.

if tm.isTestNode(c.p) or tm.isSuiteNode(c.p):

seen.append(p.v)

result.append(c.p.copy())


I think there should be tested not only isTestNode(c.p), but also it's 
parents.


# An important special case: add the *selected* @test or @suite node,

# regard regardless of all other considerations.

for p1 in c.p.self_and_parents():

if tm.isTestNode(p1) or tm.isSuiteNode(p1):

seen.append(p1.v)

result.append(p1.copy())


When I changed code the command works as I expect.

I do remember that I have send once a patch produced by bzr command, but it 
was long time ago and I am not sure how I did that. I tried making my own 
branch on my computer, changed code there, committed and then issued 
command:

bzr send -o leopatch.txt

That produced file with changes I have made, and I have attached it to this 
message.

I didn't try to apply it but I hope it should be done by:

bzr merge 

or something.


HTH Vitalije


-- 
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/-/lamJ1gc7UiMJ.
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.

# Bazaar merge directive format 2 (Bazaar 0.90)
# revision_id: -20120328085938-hqacq2ik617b1usx
# target_branch: http://bazaar.launchpad.net/~leo-editor-team/leo-\
#   editor/trunk3/
# testament_sha1: f00d7874b332c073059efafaf34cecd8799630b1
# timestamp: 2012-03-28 11:01:12 +0200
# base_revision_id: edream...@gmail.com-20120327223845-\
#   vvmphz05qojci2e8
# 
# Begin patch
=== modified file 'leo/core/leoTest.py'
--- leo/core/leoTest.py 2012-03-27 12:16:41 +
+++ leo/core/leoTest.py 2012-03-28 08:59:38 +
@@ -1418,10 +1418,11 @@
 
 # An important special case: add the *selected* @test or @suite node,
 # regard regardless of all other considerations.
-if tm.isTestNode(c.p) or tm.isSuiteNode(c.p):
-seen.append(p.v)
-result.append(c.p.copy())
-
+for p1 in c.p.self_and_parents():
+if tm.isTestNode(p1) or tm.isSuiteNode(p1):
+seen.append(p1.v)
+result.append(p1.copy())
+
 while p and p != limit:
 if p.v in seen:
 if trace and verbose: g.trace('already seen',p.h)

# Begin bundle
IyBCYXphYXIgcmV2aXNpb24gYnVuZGxlIHY0CiMKQlpoOTFBWSZTWTOkm5wAAY/f6gRUUGf/91oB
DACwEAAQQEJIYABQA77rtFJyhaJuEkpk0lM8mqfqeo/RR6p7I00mmp6noEZPU0aA0EkgjJpN
kmptNU9I0ADTQAaDQAEkSaZBNNGpp6NJNNNqZPUeUD1DQ2oADmmJgI0wIwjEwjAamo0TRtTD
QmnqAA00A0AaAaNDhKgzNBOEwRKeBHMtG6AIVBaN1deXkhIMAcwbilrEGbl7DwopGZjowjRx8JHk
qv5HjKeUIZ8JV67SNkhxqSdBxMGSeDCH7Z5DBYjMOWECuHJ5EYwT87TY6AZhCCxNVBWgsNedfF+O
cE/W+9/WFKnRFfOF1N+u3fcK5nIcwhrmTiMvkQWdZua0BAVKioNJ+6s7mVhfxYqY2yy9akuJt5Gd
uEedqV1sqew1WKtSUvHXTMXTjGC6zVwNuTiXN9VcLTfo/iuDCKCM3uq5cIK8mpuH5bhGxq4zxCNl
YXNaKnXIRhxjAjaEoWFVQvIEidoqrpReiya1QdTKMwyyjREzG/C0LFfIgy1g49gsmqOl/LtbJi9W
U9+jpizy4Z3kMLaJ+ETDbe5QuOViQ04K8gLQtLODhVeqCyJ7X8JK8VMJmEyWMpwWKhsoxaclg96W
mYz6mKS7t3kyzQtMmYK5tHQ5S6aLUEgpk1c+J24bui2Dtt9HAOojUyY+OqFbb5N2ZoxRbHF5AkCJ
W7etBJHr09ewVhTn1BuDKu1oBXB8OPYUUJPWWwiKWLhtI9Xb57waaXmU2O0zROiHos8nMGdtbxYq
Tb2HTaNlV3cy7Tvmqya7L6MFWnxPOTbaZwph16H5FJg+r01XO4UnIZLLW6JTI084U5wctkqvB7i3
p3VNvvu4Uytl+5CANoKD4pkVJVfCzM6Z99r/uw0knuQy7uV+kmyo1mFe7AmPrdv6m82NJtRxDHU1
wWEJLBXKdSkFo6sU1ObuTTccDaKoIqUrDYFP0s53Q52ZdpiHeQNzebcsE2w6xY4g4ZBMJudLFkU6
sD2/Boa9Mn4s7Dc1Q0OoMe2pa1IPC8aBwXZcETFqsp5TUC4Hi/TKF8pIpZDLbqgjmYWyn71XsDm1
ouMsaiNxRiEILdBMZs5b7uursDJ8mPK6gVk3TxNhrpqkxvV4rRU8FSTa5cKFAOTd4YSS8buq8swq
TzhphRGLpoMchuh+Fx3eGKdSEwwH4LLnolMGl6HP5hZtWnKb1Fn+4dk5tlk/GZbIoxSHcyKETENy
1aLD7nK7qUN7fjkwdmG3cBT2+aoWrpDsXQseUTwniXhIOxVsR3t7MRgr3RRT+pH8XckU4UJAzpJu
cA==

Re: Items for Leo 5.0

[vitalije]

I think that fossil http://www.fossil-scm.org is worth trying when we 
speak of distributed systems. It consists of just one executable and it has 
included http transport, standalone http server, cgi enabled,...

Actually I have made some simple script-buttons few months ago to 
disassemble Leo outline in to set of files with gnx as file names and 
content as: first-line headline, rest of lines are body. Script makes 
temporary folder and disassembles Leo outline there, and then writes Leo 
tree in file named __leotree__ in simple plain text format, and finally 
executes fossil in other process to add / remove files and commit changes.

The other script executes fossil to get time-line and offer in the 
completion tab list of check-ins contained in fossil, and when user chooses 
one then script would run fossil to get zip file of the choosen revision, 
open zip and rebuild Leo outline.

I didn't like too much extracting nodes in temporary folder so I thought it 
would be nicer to implement some kind of virtual file system in python, 
mount it, and run fossil there but I hadn't time to invest in such a 
project.

That was before cleaning of Leo's init code and I remember that it was not 
so easy to create new Leo commander to rebuild tree from repository. I 
think that I used leoBridge to rebuild outline and then to save it but I am 
sure it would be more elegant if script could rebuild outline from fossil 
repository in another tab.

If you find this interesting I could send scripts.

Vitalije

-- 
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/-/_cVsr3FgUWAJ.
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: Items for Leo 5.0

[vitalije]

On Wednesday, March 28, 2012 12:16:38 PM UTC+2, HansBKK wrote:

 Selecting any one of git/fossil/mercurial etc as a dependency for 
 distributed Leo will IMO deliver a much lower return on effort expended 
 than a solution that allows a group to go Leo on top of whatever cool 
 tool they're already committed to, without having to reinvent the wheel 
 separately for each flavor in the future.

 Without wish for arguing I think fossil as being one executable file could 
easily be distributed along with the Leo and user even doesn't need to know 
about it (if he/she isn't interested). I am afraid that if we decide not to 
use any of git/fossil/mercurial etc we will have to reinvent the weel 
of some kind.
Vitalije

-- 
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/-/uWOXYmhN6Z0J.
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.

Removed @chapter on undo

[vitalije]

Hello,
I have been using Leo 4.8 or 4.9 for a long time (and older versions too). 
Recently, I updated my Leo to Leo-5.0-final. I am using ubuntu 14.04, 
Python 2.7.6, PyQt 4.8.6.

In almost any of my leo files I have several @chapter nodes and didn't have 
any troubles until a few days ago when I realized that (at least one) 
@chapter disappeared. I thought that maybe I unintentionally pressed delete 
key. Anyway, I pulled older version of the file and manually copied/cloned 
nodes to recreate missing @chapter.

Today, I have noticed a message in log window Note: Removed chapter  
I pressed Ctrl+Z to undo action, but I was very surprised when another 
message appeared informing me that the other @chapter was removed too. I 
looked in Edit menu and there was command Redo Create Chapter which I 
executed twice and luckily my @chapters were restored. 

I am absolutely sure that I have had those @chapter nodes for some time, 
i.e. they weren't created today. Yet, Leo's undo command removed my 
@chapters as if my last action was 'chapter-create'.

I tried to reproduce the problem with the new Leo file, but with no 
success. 

It looks like a serious and dangerous bug to me.
I assume that @chapter commands and @chapter nodes are still supported (am 
I wrong with that assumption?)

Vitalije

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Removed @chapter on undo

[vitalije]

Yes, certainly there is a bug related to chapter commands.

I haven't reproduced the original bug, but I found possible related bug.
To reproduce it:

   1. open a new Leo file.
   2. Execute command from menu Cmds - Chapters - Chapter-Create.
   3. Type in mini-buffer non-ASCII name for newly created chapter for 
   example copy and paste word Проба in mini-buffer and press enter.
   4. Leo will insert two @chapter nodes and one of them will have the 
   given name, but the other one will have  as name.

When selecting non-ASCII named chapters strange things happen. Sometimes 
Leo creates a new chapter.

HTH

Vitalije.

about my installation:
 Leo Log Window
Leo 5.0-final, build 20141124101406, Mon Nov 24 10:14:06 CST 2014 
Git repo info: branch = master, commit = 7515bed9d5ad 
Python 2.7.6, PyQt version 4.8.6
linux2


-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Removed @chapter on undo

[vitalije]

 I'd also file a report at https://github.com/leo-editor/leo-editor/issues, 
 to help insure it doesn't get lost in the holiday goings on.


Done.

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: A serious bug in handling unicode @chapter names

[vitalije]

 ​Thanks for this report.  Please file a bug report at 
 https://github.com/leo-editor/leo-editor/issues.
  

I did. 

https://github.com/leo-editor/leo-editor/issues/126 

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

@nosent and multiline comments bug

[vitalije]

Hello,
I have updated my Leo installation yesterday and bumped in a bug with new 
@nosent code. Most of my files have been kept in @nosent nodes. Whenever I 
open leo file with @nosent nodes, Leo reports Recovered nodes. All those 
nodes are using multiline comments between @ and @c directives. With every 
opening Leo adds single line comments in front of those lines.

I have attached Leo-file which demonstrates the problem.
HTH
Vitalije

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.


nosent-comment-bug.leo
Description: Binary data

Re: @nosent and multiline comments bug

[vitalije]

 ​This is a nasty problem.  It's been around since day one of the @shadow 
 algorithm, but it's only been reported now. It will requires some kind of 
 special case for @...@c.  I'll have to think about what is the best way to 
 proceed.

 Edward


Well, I could live without @ and @c, but it would be useful if Leo delete @ 
and @c lines and replace all those lines with properly language specific 
commented block.
Vitalije

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

@nosent goto line bug

[vitalije]

For quite a long time I have noticed that command goto global line (Alt+G) 
doesn't work properly on @nosent files. It seems that it counts 
non-existing sentinel lines so it positions cursor few lines before the 
requested. The exact difference between required line number and found one 
depends on size of file and number of nodes, and also grows with required 
line number.

You can exhibit this by looking in attached Leo file. For example Alt+g 45 
should position cursor on the declaration line of function temp7(a), but it 
positions cursor on line 39.

HTH Vitalije

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.


nosent-goto-line-bug.leo
Description: Binary data

Re: @nosent and multiline comments bug

[vitalije]

 I am wondering whether it might not be better simply to prohibit @...@c in 
 @nosent files.  How odious would that be for you?

 Edward

As I said, I could live with such restriction, but it would help if Leo 
change such blocks of code without user intervention. I think that no user 
using @nosent would object this Leo behaviour.

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: @nosent and multiline comments bug

[vitalije]

about my installation: Ubuntu 14.04

** isPython3: False
Leo 5.0-final, build 20150127110559, Tue, Jan 27, 2015 11:05:59 AM
Git repo info: branch = master, commit = f2ca65ecf8e8
Python 2.7.6, PyQt version 4.8.6
linux2

Vitalije

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Watch out! clones get corrupted

[vitalije]

Hello
this morning I found one of my Leo files,  that I worked on a few days ago, 
corrupted. While opening the file, Leo hanged and I had to kill it. After 
some examination of xml source I found that some of my last added nodes got 
the same gnx. One of them had child with the same gnx and that caused Leo 
to hang. I have changed manually gnx of the parent node in xml. When I 
finally open outline in Leo I found few other nodes were missing or had 
wrong headline/body.
I don't know what caused this and can't reproduce it but I strongly suspect 
it has something to do with recent changes in Leo write.
Unfortunately I can't say which revision I used to write the problematic 
file. It was one of the revisions after 
934537266cf5d3e556025adc6ba39ff35be81741 
which solved bug #138. This morning I pulled latest Leo revision before 
trying to open file.

I am using Ubuntu 14.04 64bit,
 Leo 5.0-final, build 20150305163031, Thu Mar  5 16:30:31 CST 2015
Git repo info: branch = master, commit = 4dddcc1ac5d8 
Python 2.7.6, PyQt version 4.8.6
linux2 


Vitalije

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Travails of a newbie

[vitalije]

 Finally, there is some mysterious key combination that makes the outline 
 disappear, and makes Leo unresponsive to any further file operation.  This 
 has happened twice. What is going on with that?  I have to use the Task 
 Manager to force Leo to close, and lose my updates.


 ​This is the first I have heard of such problems.  I recommend running Leo 
 from a console, as described here: 
 http://leoeditor.com/running.html#running-leo-from-a-console-window
 The console often will tell you when something mysterious happens.
 ​


It could be connected with problem with corrupted node indexes that I wrote 
about in another thread. When some node become child to itself, Leo stops 
responding.
 

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Watch out! clones get corrupted

[vitalije]

I think that methods which manipulate nodes on lowest level should check 
and alarm user if ever node with same gnx is added, inserted, moved,... in 
children (or maybe even in subtree in general).

That way we could easily detect when something goes wrong and save outline 
in different file.
Vitalije.

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: @nosent goto line bug

[vitalije]

 Fixed at rev 3ee6afd.  Let me know if you find any further problems.


I must admit it seemed to me that this bug was fixed, but here is another 
example that demonstrate error in goto-global-line.

In attached Leo file I just put one organizer node and goto-global-line can 
not find any requested line in file.

Vitalije

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.


nosent-goto-line-bug.leo
Description: Binary data

Re: Any reason to keep @auto or @shadow?

[vitalije]

 I'll add support for @clean today. Leo 5.1 will come out in a few days.

 Edward​


Please take a look into global-goto-line bug 
https://github.com/leo-editor/leo-editor/issues/138 before releasing 5.1, 
especially  because it relates to @clean files, and I guess it wont be too 
hard to deal with.

It can be frustrated to new Leo users if they try to find exact line 
reported by some compiler and Leo shows them wrong line.

Vitalije.

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Any reason to keep @auto or @shadow?

[vitalije]

No, it can't be frustrated, but it can be frustrating new users.
Sorry, English is not my first language.


 Vitalije.


-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: @nosent goto line bug

[vitalije]

Again, I have read in another thread: Leo 5.1 will be soon released. 
Just to bring Edward's attention to this thread and the fact that this bug 
has not been fully fixed yet.
Vitalije.

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

goto-global-line doesn't work properly in @clean files

[vitalije]

A few months ago I have filled similar bug report against @nosent files. 
Well that bug is fixed and Leo properly finds global line in @nosent files. 
:-)

OTOH, since then @clean files are introduced and suggested as better 
replacement for @nosent files. Well, command goto-global-line can't find 
proper line in @clean files. If turned into @nosent file, command 
goto-global-line works as advertised. 
I pulled newest version of Leo from git this morning and problem is still 
there.

Leo Log Window

Leo 5.1-final, build 20150529185559, Fri May 29 18:55:59 CDT 2015

Git repo info: branch = master, commit = 9122fe9233cb

Python 2.7.6, PyQt version 4.8.6
linux2

You can see the problem in example.leo file 
https://11707503125000652521.googlegroups.com/attach/63f325cf79f6b2e9/nosent-goto-line-bug.leo?part=0.1vt=ANaJVrEFOqs7FjwohsShTGNcPvTY-neL0Bo1HM69Du4ut9S9FNhvRdiBCr5P9xR8iVVp53Mv15nj28FJb7AWRn6WCrWuTp12GR91I-HvbIlypzqXs6SVYh8
 
that I send for the former bug report, just turn @nosent test.js into 
@clean test.js. Link is here 
https://11707503125000652521.googlegroups.com/attach/63f325cf79f6b2e9/nosent-goto-line-bug.leo?part=0.1vt=ANaJVrEFOqs7FjwohsShTGNcPvTY-neL0Bo1HM69Du4ut9S9FNhvRdiBCr5P9xR8iVVp53Mv15nj28FJb7AWRn6WCrWuTp12GR91I-HvbIlypzqXs6SVYh8


HTH Vitalije.

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: goto-global-line doesn't work properly in @clean files

[vitalije]

I presume Edward missed this topic, so I am just touching it again.
IMHO this bug can easily repel newbies. If one is not able after seeing 
stack trace in console, to easily find a specific line in source code using 
Leo, he could get very wrong impression about Leo's capabilities. 
Vitalije 

-- 
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Leo and fossil

[vitalije]

On Tuesday, January 17, 2017 at 3:19:58 PM UTC+1, Terry Brown wrote:
>
> I assume you mean it's just one Python file, that could be distributed 
> with Leo?  That is an advantage. 
>
> Fossil is native application not python script. 

>
> backend.snapshot_node(, ) 
> backend.node_versions()  # list version_ids of available versions 
> backend.get_node(, ) 
> Cheers -Terry 
>

Well, I can easily change my script to provide API that Terry suggested, 
using fossil.

I'm not sure there's enough difference in convenience there to put a lot 
> of weight on that distinction. 


You are right. It maybe just matter of preference and therefore not so 
important. IMO, sharing, moving, copying is much faster(=easier) for a 
single file than for a subfolder.

As I have seen in links that you pointed to, you have done some node 
versioning before. I didn't study it very thoroughly so I maybe very wrong, 
but I feel that you had some unnecessary difficulties with the UNLs, so you 
encoded them into base64. In my outline encoding scheme, I believe those 
problems are voided. 

Vitalije

-- 
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 and fossil

[vitalije]

On Monday, January 16, 2017 at 11:45:56 AM UTC+1, Edward K. Ream wrote:
>
> So now I am more receptive to these ideas.  
> Edward
>
Glad to hear that.  

-- 
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 and fossil

[vitalije]

Database is just a part of fossil. It isn't question of where Leo can keep 
its data. It's about keeping a history of data. Fossil keeps (in efficient 
way) all versions of the data, it can show the diffs in several formats, 
... pretty much all that git does. The advantage of using fossil instead of 
git, IMHO, is that:

   - it doesn't need to be installed (it is just one executable file, 
   available for all platforms that  Leo supports)
   - it keeps all its data in just one file, while git creates .git subtree


On Monday, January 16, 2017 at 5:25:22 PM UTC+1, Terry Brown wrote:
>
> Another question is whether the integration is just at the load/save 
> level or at the node traversal level, i.e. constantly using a data 
> backend.  I think if we started with the load/save level, the sweet 
> spot might be some subtree / node level live refresh from a data 
> backend. 
>
> For diffs, seems an xml to yaml conversion would achieve that?  Like I 
> say, haven't been following the conversation too closely. 
>
> Cheers -Terry 
>
> I don't expect integration to be at node traversal level. At the load/save 
phase (or even on an explicit user request), fossil would record the new 
version of the outline. Later, a user might want to see how and when some 
node has changed, or what was it like in some earlier version. The simple 
script I made for the experiment already enables all that functionality. 
The next more challenging task is to create an elegant GUI that user can 
use to run all those functions.
I haven't programed in PyQt for a long time. Many things I used to know I 
forgot  and there seem to be a lot of changes in PyQt since. Nevertheless, 
I can imagine how GUI might be like. For example, imagine a small slider 
widget along the bottom of body, or in status line, that represents time. 
User can slide it left or right and the selected body would change 
accordingly as it was at the selected moment. When focused slider would 
enable user to switch to the previous/next version using the arrow keys.

I am not sure that all this would be useful at all. I can't recall when was 
the last time that I needed something like this. But maybe I would use it 
more often if it was possible in the first place. The way I see it, this 
can be interpreted as "undo/redo" functionality but persistent between 
editing sessions and spread at node levels, i.e. every node has its own 
"undo/redo" timeline. It may be useful, who knows?

Vitalije

-- 
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: Syntax coloring cloned node

[vitalije]

One possible solution would be to use Leo-UNL instead of clones. For 
example in your @rst file you put somewhere following:

.. code:: nasm
LEOUNL:: 

Then run the following script (could be turned in to button) to generate 
your rst files:
@first # -*- coding:utf-8 -*-
import re
import os
LEOUNLpat = re.compile(u'LEOUNL::([^#]*)#(.*)$', re.M)
def process_rst_files():
for p1 in c.allNodes_iter():
if p1.h.startswith(u'@rst '):
fname = p1.h[5:].strip()
g.es(u'processing %s'%fname)
do_one_file(p1, fname)

def do_one_file(p1, fname):
c.rstCommands.processTree(p1, None, toString=True, justOneFile=True)[0]
fname = os.path.join(c.getNodePath(p), fname + '.txt')
s = c.rstCommands.source.decode('utf-8')
s = putLeoCode(s).encode('utf-8')
s1 = getfile(fname)
if s1 != s:
putfile(fname, s)
g.es('changed')
else:
g.es('unchanged')

def getfile(fname):
try:
s = open(fname,'rb').read()
except IOError:
s = ""
return s

def putfile(fname, s):
out = open(fname, 'wb')
out.write(s)
out.close()

def putLeoCode(txt):
i = 0
res = []
while i < len(txt):
m = LEOUNLpat.search(txt, i)
if not m:
res.append(txt[i:])
break
else:
res.append(txt[i:m.start()])
ind = u'\n' + indentation(txt, m.start())
leofile = m.group(1)
unl = m.group(2)
found, depth, p1 = g.recursiveUNLSearch(unl.split(u"-->"), c)
if found:
kod = c.p.b.splitlines(False)
res.append(ind.join(kod))
else:
print (u"Leofile:"+leofile)
print (u"unl:[%s]"%unl)
print (u'not found')
raise ValueError, unl
i = m.end()
return u''.join(res)

def indentation(txt, i):
j = i
while j > 0 and txt[j-1] == ' ':
j -= 1
return ' '*(i-j)
process_rst_files()

I am still using python2. If you use python3 I believe it would complain a 
little about syntax. In that case remove all .encode('utf-8') and 
.decode('utf-8') and all string literals that are prefixed with u should be 
without that prefix.
HTH VItalije

-- 
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's real weaknesses

[vitalije]

I suppose it can be done with the git also. But in that case user would 
need to have git installed and also git would need to recreate '.git' 
subfolder inside temporary folder every time. Fossil OTOH, keeps all its 
data in just one file which is in fact just sqlite3 database file. One can 
access its content with sqlite3 python module. Fossil itself is just one 
executable file about 1.5 - 2Mb which can be downloaded by a python script 
if it is not already available in the system path. Fossil executable 
contains also a standalone web server and can communicate and synchronize 
data with remote repositories through HTTP or SSH.

Scripts do not depend that much on fossil. They just run fossil through 
subprocess module. All that is needed to replace fossil with git is to 
change command line arguments. I believe fossil and git have similar 
commands but they use different names. 

If you are interested in those scripts I will try to find (or recreate) and 
share them.
Vitalije

On Friday, January 13, 2017 at 5:31:48 PM UTC+1, Edward K. Ream wrote:
>
> On Fri, Jan 13, 2017 at 4:53 AM, vitalije <vita...@gmail.com 
> > wrote:
>
> Converting from xml to (say) json, won't help.
>>>
>> IMHO it is not necessarily true. I don't suggest changing Leo document 
>> format from xml to json or any other format. But there can be found a 
>> scheme of encoding a Leo document in such a way that its changes can be 
>> expressed in a human readable diffs.
>>
>
> ​This is very interesting.  Do you think your ideas/scripts can be adapted 
> to git?
>
> > I didn't go any further in developing that idea mostly because I 
> couldn't find a good way to show those choices to the user and to show 
> different versions of a node. 
>
> Yes, this a real problem. I'm not sure even perfect, high-level diffs do 
> much good if the user can't use them easily.
>
> 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.

Re: Leo's real weaknesses

[vitalije]

I couldn't find my earlier works but I have (re)created some script that 
can be used for experiments. In the attachment of this message is 
`fossil-leo.leo` file which contains one @button script.
Before running this script one should provide that fossil executable is 
somewhere in the path. Fossil can be downloaded from fossil-scm.org

The script performs two different actions depending on the switch in its 
root node.
The first action is to create a repository (if it doesn't exist), and then 
to put current content of the Leo outline in the repository. One should 
perform this action several times after making any changes in outline. 
Every time this script is executed new version is added (unless there are 
no changes).

After you create several versions you can change the switch in the root of 
script so that script performs another action. The other action is to 
retrieve content of any given node at the given time. Before performing 
this action one should adjust the arguments of the function call `
fossil_cat_at_time` to reflect his/her own Leo document. Time should be 
after the first version, and the name of file should be existing gnx that 
has been already stored using the first action. Content of the given node 
is presented in the log pane named 'History'. 

If you put the gnx which didn't exist at the given time, script would 
produce an error.

This is just for experimenting. Someone good with the Qt may find a better 
way to show versions and also to allow user to choose particular version. 

function fossil_timeline can be used to retrieve names of the last 20 
versions, or  with some tweaking any other list of versions. Every version 
has canonical name like hexadecimal literal and the time it was committed. 
This list can be parsed and displayed as a list, combo or scale widget 
where user can easily choose version. A gnx can be either a gnx of the 
current position or position that was selected when the widget was 
constructed.
Together gnx and version name (SHA1 hash) can be used by function `
fossil_cat` to retrieve content of the node in specified version.

If this should become a plugin than perhaps it could also check whether 
there is fossil on system path or not and if it is not installed to 
retrieve correct version for the platform and install it somewhere in Leo 
folder and all fossil commands should be adjusted to use the downloaded 
executable.
HTH Vitalije

-- 
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.


fossil-leo.leo
Description: Binary data

Re: Leo's real weaknesses

[vitalije]

FYI the above script will create a repository in current directory. If you 
execute the following command:

fossil ui leohistory.fossil

(you may need to provide a full path to leohistory.fossil)
it should open your default browser and show you the home page of the 
repository. There you can find timeline, diffs in different formats, 
content of each node, etc.
Vitalije

-- 
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's real weaknesses

[vitalije]

>
> Converting from xml to (say) json, won't help.
>
> IMHO it is not necessarily true. I don't suggest changing Leo document 
format from xml to json or any other format. But there can be found a 
scheme of encoding a Leo document in such a way that its changes can be 
expressed in a human readable diffs. That scheme can be just an additional 
format. Its purpose is not to replace xml. 

First let us analyze what kind of changes can we made by editing any given 
Leo document.

   1. we can edit content of any body, which means a standard plain text 
   changes (adding a line, deleting a line or changing some part of a line). A 
   standard diff tools are good in dealing with those kind of changes.
   2. or we can rearrange nodes. A simple edit such as sorting children of 
   one node, can make a very hard to understand diffs. 
   
A few years ago I tried to combine Leo with fossil <http://fossil-scm.org/>to 
make it possible to see how any particular Leo document evolved. A fossil 
is just one executable file which can be easily incorporated with the Leo 
itself, it doesn't need to be installed or configured to work. 

I have made a script that encodes entire Leo tree into bunch of files one 
per each node named after gnx, and one special file named __LEOTREE__. The 
__LEOTREE__ file contents was just a list of lines that describe 
connections between nodes. Each line started with the level of the node it 
represents followed by its gnx. The node files were encoded with the simple 
scheme. Headline was a first line, followed by the body content of the 
node. The script would generate all those files in a temporary folder and 
then invoke a `fossil commit` there. Fossil would analyze content of the 
folder and record all changes.

The other script I have made would invoke fossil to print a timeline with 
all recorded versions, and offer a user to choose one of them. After user 
makes a choice that particular version would be extracted and content of 
the any given node that existed in that version would be displayed. 

I didn't go any further in developing that idea mostly because I couldn't 
find a good way to show those choices to the user and to show different 
versions of a node. That was before a view rendered plugin appeared, (which 
I still don't use). I guess maybe it could be used to show diffs or 
different versions of a node.
Vitalije

-- 
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: I've declared war on fit and finish problems :-)

[vitalije]

> For example, I recently ignored an apparent problem with Alt-G, 
> goto-global-line.  It would have been best to *stop everything* and make 
> careful notes about how to recreate the problem, but I didn't do that. Now 
> I can't find anything wrong with Alt-G. Live and learn.


I remember posting an example leo file that demonstrates problems with 
goto-global-line. Here is the original post 
https://groups.google.com/forum/#!searchin/ 
<https://groups.google.com/forum/#%21searchin/leo-editor/author$3Ame/leo-editor/zJtp1nkFTZM/tFgWmBqDgfoJ>
leo-editor/author$3Ame/leo-editor/zJtp1nkFTZM/tFgWmBqDgfoJ 
<https://groups.google.com/forum/#%21searchin/leo-editor/author$3Ame/leo-editor/zJtp1nkFTZM/tFgWmBqDgfoJ>

There was attached file 
<https://11707503125000652521.googlegroups.com/attach/63f325cf79f6b2e9/nosent-goto-line-bug.leo?part=0.1=ANaJVrEFOqs7FjwohsShTGNcPvTY-neL0Bo1HM69Du4ut9S9FNhvRdiBCr5P9xR8iVVp53Mv15nj28FJb7AWRn6WCrWuTp12GR91I-HvbIlypzqXs6SVYh8>.
 
I have just updated my Leo and tested this file and once again 
goto-global-line is not working correctly.
AFAIR problems were somehow connected with the presence of the doc parts in 
code.

HTH Vitalije

-- 
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: @clean nodes stopped updating

[vitalije]

I have bisected and found that the culprit is change in default setting.
Here is relevant commit:
2a0eca1635457b379e6e1cbfab6595e55afbd635 is the first bad commit
commit 2a0eca1635457b379e6e1cbfab6595e55afbd635
Author: Edward K. Ream 
Date:   Fri Dec 16 15:06:40 2016 -0500

Set @bool check_for_changed_external_files = False by default, and 
reference #262,
@bool check_for_changed_external_files may hang on network files.

Leo build: 20161216150641

:04 04 a946721dce8ae22363024fd5eedd9caea780e930 
81c2141e6c4404f6dab63b3d93971e9d7f930551 Mleo


 

On Tuesday, April 11, 2017 at 10:45:23 PM UTC+2, Edward K. Ream wrote:
>
> On Tuesday, April 11, 2017 at 3:40:38 PM UTC-5, Edward K. Ream wrote:
>
> > HTH.  We'll get to the bottom of this.
>
> And be sure to verify that your tool chain is actually updating the files 
> you think it is.
>
> The symptom that you must reload Leo to see changed files is quite 
> strange.  It argues that your tool chain *is* updating files, but we have 
> to check everything.
>
> We have to run Leo in a console so we can see all exceptions, especially 
> uncaught exceptions.
>
> For sure something strange is going on. A silently hidden exception, an 
> invisible popup, files not actually being saved, on_idle checks not 
> happening at all...
>
> 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.

Re: @clean nodes stopped updating

[vitalije]

Just add :
@bool check_for_changed_external_files = True


to myLeoSettings.leo in your configuration file.
Vitalije

-- 
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.

Possible bug in pluginsController.registerOneHandler

[vitalije]

# from leoPlugins.py file

def registerOneHandler(self, tag, fn):

"""Register one handler"""

try:

moduleName = self.loadingModuleNameStack[-1]

except IndexError:

moduleName = ''

...

items = self.handlers.get(tag, [])

if fn not in items:

   bunch = g.Bunch(fn=fn, moduleName=moduleName, tag='handler')

   items.append(bunch)

self.handlers[tag] = items

It looks like the above code checks to see if given function has already 
been registered, (`if fn not in items:`) but then it puts a bunch instance 
in items not the handler function. Unless I am mistaken, it will never be 
the case that the above condition is False, because handler function will 
never be added to items array.
Vitalije

-- 
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: Possible bug in pluginsController.registerOneHandler

[vitalije]

On Wednesday, April 5, 2017 at 7:24:15 PM UTC+2, Edward K. Ream wrote:
>
> ​Good catch. The test above looks like mistaken defensive programming. We 
> could eliminate the test entirely, or test each bunch in items:  if 
> bunch.fn == fn:...
>
> Care to change this yourself?
>
> Edward
>

I'll try ASAP (in a day or two).
Vitalije

-- 
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: Possible bug in pluginsController.registerOneHandler

[vitalije]

I tried to `git push` my corrections but was refused with status 403.

So I forked leo-editor and pushed changes to my fork of leo-editor. I have 
added two new @test nodes in leo/test/unitTest.leo that test expected 
behavior of registerOneHandler and registerOneExclusiveHandler. After that 
I have made some corrections in leo/core/leoPlugins.py to make new tests 
pass. 

However, when I tried to run all unit tests to check that I didn't broke 
something else in Leo codebase, I've got more than 100 failed tests?! Am I 
missing something? What is the correct way to run all tests before 
committing changes to main branch?

Besides, method registerOneExclusiveHandler of leoPluginsController was 
even more broken. It is most unlikely that any plugin used this method ever 
because it was replacing the handlers map with the array of one bunch 
containing one exclusive handler.
def registerOneExclusiveHandler(self, tag, fn):
   
   if tag in self.handlers:
   g.es("*** Two exclusive handlers for", "'%s'" % (tag))
   else:
   bunch = g.Bunch(fn=fn, moduleName=moduleName, tag='handler')
   self.handlers = [bunch]
The last line would broke all other plugins.


Vitalije

-- 
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: Possible bug in pluginsController.registerOneHandler

[vitalije]

Pull request is here <https://github.com/leo-editor/leo-editor/pull/468>
Vitalije

-- 
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: @clean nodes stopped updating

[vitalije]

>
> I'm dithering about @bool check_for_changed_external_files.  On the one 
> hand, it seems unreasonable not to enable it by default.  It's the expected 
> behavior for most editors and IDE's.  Otoh, there are rare performance 
> problems with network drives.​
>

Is it possible for Leo to discover if some file path is in fact path to 
network drive? If possible then perhaps we can have the default settings 
set to True and refuse to check network paths and maybe warn user that 
those paths are not going to be checked.
Vitalije

-- 
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: @clean nodes stopped updating

[vitalije]

>
> ​I would have done something similar.  But you don't have to use a temp 
> folder​. You can do the git bisect "in place", in your normal leo-editor 
> folder. When you are done, git will leave your folder just as it was.
>
> Edward
>
Yes, I knew it would, but in my Leo folder there are myLeoSettings.leo, and 
some plug-ins that can affect the behavior  of the Leo. If I have had  @bool 
check_for_changed_external_files set to True in my Leo settings, I wouldn't 
be able to reproduce the bug at all. Besides, I wanted to have normal 
operational Leo at hand, ready to create and edit script files used in 
experiment. Perhaps, for some (or even many) bugs, it doesn't really 
matter, but with some more dangerous bug it would. 
Vitalije

-- 
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: @clean nodes stopped updating

[vitalije]

I am not certain but it could be caused with the fixing of other bug I have 
reported recently in checkTimeStamp method. It used to report non-existing 
files in some cases as changed and to fix that the above method was changed 
to return True by default which means "file not changed". Try to test it 
with the version before this fix.
The change was introduced in b7638799d6 commit.
HTH Vitalije

-- 
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: New backend for Leo Cacher

[vitalije]

>
> I think I've been using this pretty consistently without any issues on 
> three installs - I only notice when I `git pull` and have to re-edit 
> leoCache.py.  So wondering if we should switch to True for everyone for 
> wider testing? 
>
> I am also using this and few problems that I have noticed so far, I have 
fixed and pushed corrected version. There maybe some problems that will 
show up once more people start to use it. I will do my best to fix any 
problem reported ASAP. So, I am also for setting `SQLITE=True` in master 
branch.

Vitalije

-- 
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: New backend for Leo Cacher

[vitalije]

>
> ​Did you push master?  I don't see SQLITE=True in leoCache.py​.  And yes, 
> it's working for me.
>
> Edward
>

Done at a1043408d.

>  

-- 
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.