Hey Daniel, I just tested that, and it works for me, but it will take
several seconds to show the text (and I have very powerful computer, just
bought) so be patient maybe the text will appear. Also control-z works.
But its true it is so slow it makes it not so worth it to use two editing
panes.
On a side note, I learned about using other editor thanks to trying this =)
On Saturday, June 22, 2013 8:30:48 PM UTC+2, daniel wrote:
>
> Hi,
>
> I searched the group for some similar issue but could not find anything,
> so I am starting a new topic.
>
> Unfortunately, I can't seem to reproduce this behaviour in a new leo file,
> but once a file shows the behaviour I can reproduce it in that file as many
> times as I want. That is why I am attaching one of my leo files where this
> happens. It is a simple file with two long R scripts and a few other
> organizing nodes.
>
> Since I have experienced this problem three times so far, I am sharing it
> here to see if someone has experienced something similar or maybe someone
> can come up with an explanation on how to fix this.
>
> Here is my Leo log pane info:
> ---------------------------------------------------
> Leo Log Window
> Leo 4.11 devel, build 5814, 2013-06-22 14:46:10
> Python 3.2.3, qt version 4.8.2
> linux2
> setting leoID from os.getenv('USER'): 'daniel'
> load dir: /home/daniel/bin/leo-editor/leo/core
> global config dir: /home/daniel/bin/leo-editor/leo/config
> home dir: /home/daniel
> reading settings in /home/daniel/bin/leo-editor/leo/config/leoSettings.leo
> docutils loaded
> reading settings in /home/daniel/.leo/workbook.leo
> reading: /home/daniel/.leo/workbook.leo
> ----------------------------------------------------
> I have tested this with and without a myLeoSettings.leo file, to rule out
> the possibility of a spurious setting in my personal settings file being
> responsible for the problem.
>
>
> To see the problem just do the following:
>
> 1) Open the teste.leo file attached and open one of the long R scripts in
> the body editor.
> 2) Go to the end of this node and start adding text and newlines.
> Everything should work fine.
> 3) Now add another body editor with "Cmds->Body Editors...->Add-Editor"
> and open the other script (or the same script, it doesn't matter) in this
> new pane.
> 4) If now you go to the end of this script and try to add something
> (newlines or text, ...), you will see that the row and column counters
> change but the body pane won't update anything.
> 5) I also note that Leo becomes very sluggish (try deleting text with
> backspace, delete key or using CTRL+Z to undo) whenever this happens.
>
> I have seen this behaviour three times so far in different files, always
> when editing long nodes. I do not know how to reproduce the moment when
> this first happens.
>
> Whenever this happens, if I want to keep on editing the node, I either
> have to split the node using section references, or edit the node in an
> external editor. Leo won't let me go on editing the whole file anymore in
> the body pane.
>
> I appreciate if anyone can shed some light on this and point me to a
> possible solution.
>
> Best regards to all,
>
> Daniel
>
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.