Re: Is it a bug of Nav

[huliuhe]

I see. but Leo doesn't  search body text if the count of node is more then 
 1;
I hit enter,  but it is no use.


在 2017年5月30日星期二 UTC+8上午10:57:09，Terry Brown写道：
>
> On Mon, 29 May 2017 19:21:47 -0700 (PDT) 
> huliuhe  wrote: 
>
> > I don't know How to hit enter. can you tell me?  thanks. 
>
> I'm referring to pressing the key you use to start a new line, 
> sometimes also called Return.  It's labeled Enter on my keyboard. 
>
> https://upload.wikimedia.org/wikipedia/commons/a/a5/Enter.png 
>
> (the red one, not the green one) 
>
> Cheers -Terry 
>
> > 在 2017年5月30日星期二 UTC+8上午9:47:34，Terry Brown写道： 
> > > 
> > > On Mon, 29 May 2017 18:44:06 -0700 (PDT) 
> > > huliuhe  wrote: 
> > > 
> > > > < 
> > > 
> https://lh3.googleusercontent.com/-3IkHowN4API/WSzOWuqI72I/AJI/4whh8eoJlhYgHPzOREgYvog4RmFRhGePQCLcB/s1600/abc.jpg>
>  
>
> > > 
> > > > not body text ?   
> > > 
> > > It normally searches body text, but only after you hit enter. 
> > > Before hitting enter, it does a kind of live search of headlines 
> > > only.  After hitting enter, it shows hits in both body and 
> > > headlines. 
> > > 
> > > Cheers -Terry 
> > > 
> > > > 在 2017年5月27日星期六 UTC+8下午12:39:08，lewis写道： 
> > > > > 
> > > > > At first you might think so, but the Quicksearch plugin 
> > > > > searches node headlines only, *not* body text. 
> > > > > 
> > > > > There are a set of filters that can be applied to limit the 
> > > > > search: All: Subtree: File: Chapter: Node. 
> > > > > However the chapter filter is not working. You get hits outside 
> > > > > @chapter nodes. 
> > > > > 
> > > > > Regards 
> > > > > Lewis 
> > > > > 
> > > > > On Friday, May 26, 2017 at 10:34:40 AM UTC+10, huliuhe wrote: 
> > > > >> 
> > > > >> I want to search sth by Nav , But it doesn't work.   I attach 
> > > > >> the leo file and a jpg. 
> > > > >> 
> > > > >> < 
> > > 
> https://lh3.googleusercontent.com/-Xr6jAg6oKEc/WSd31ZL3S1I/AI4/9fe9T1fRV_QNAjWzCopQW1hrx2K3Yr-xACLcB/s1600/abc.jpg>
>  
>
>

-- 
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: Is it a bug of Nav

[Terry Brown]

On Mon, 29 May 2017 19:21:47 -0700 (PDT)
huliuhe  wrote:

> I don't know How to hit enter. can you tell me?  thanks.

I'm referring to pressing the key you use to start a new line,
sometimes also called Return.  It's labeled Enter on my keyboard.

https://upload.wikimedia.org/wikipedia/commons/a/a5/Enter.png

(the red one, not the green one)

Cheers -Terry

> 在 2017年5月30日星期二 UTC+8上午9:47:34，Terry Brown写道：
> >
> > On Mon, 29 May 2017 18:44:06 -0700 (PDT) 
> > huliuhe  wrote: 
> >
> > > <
> > https://lh3.googleusercontent.com/-3IkHowN4API/WSzOWuqI72I/AJI/4whh8eoJlhYgHPzOREgYvog4RmFRhGePQCLcB/s1600/abc.jpg>
> >  
> >
> > > not body text ?   
> >
> > It normally searches body text, but only after you hit enter.
> > Before hitting enter, it does a kind of live search of headlines
> > only.  After hitting enter, it shows hits in both body and
> > headlines. 
> >
> > Cheers -Terry 
> >
> > > 在 2017年5月27日星期六 UTC+8下午12:39:08，lewis写道： 
> > > > 
> > > > At first you might think so, but the Quicksearch plugin
> > > > searches node headlines only, *not* body text. 
> > > > 
> > > > There are a set of filters that can be applied to limit the
> > > > search: All: Subtree: File: Chapter: Node. 
> > > > However the chapter filter is not working. You get hits outside 
> > > > @chapter nodes. 
> > > > 
> > > > Regards 
> > > > Lewis 
> > > > 
> > > > On Friday, May 26, 2017 at 10:34:40 AM UTC+10, huliuhe wrote: 
> > > >> 
> > > >> I want to search sth by Nav , But it doesn't work.   I attach
> > > >> the leo file and a jpg. 
> > > >> 
> > > >> <
> > https://lh3.googleusercontent.com/-Xr6jAg6oKEc/WSd31ZL3S1I/AI4/9fe9T1fRV_QNAjWzCopQW1hrx2K3Yr-xACLcB/s1600/abc.jpg>
> >  

-- 
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: Is it a bug of Nav

[huliuhe]

I don't know How to hit enter. can you tell me?  thanks.

在 2017年5月30日星期二 UTC+8上午9:47:34，Terry Brown写道：
>
> On Mon, 29 May 2017 18:44:06 -0700 (PDT) 
> huliuhe  wrote: 
>
> > <
> https://lh3.googleusercontent.com/-3IkHowN4API/WSzOWuqI72I/AJI/4whh8eoJlhYgHPzOREgYvog4RmFRhGePQCLcB/s1600/abc.jpg>
>  
>
> > not body text ?   
>
>
> It normally searches body text, but only after you hit enter.  Before 
> hitting enter, it does a kind of live search of headlines only.  After 
> hitting enter, it shows hits in both body and headlines. 
>
> Cheers -Terry 
>
> > 在 2017年5月27日星期六 UTC+8下午12:39:08，lewis写道： 
> > > 
> > > At first you might think so, but the Quicksearch plugin searches 
> > > node headlines only, *not* body text. 
> > > 
> > > There are a set of filters that can be applied to limit the search: 
> > > All: Subtree: File: Chapter: Node. 
> > > However the chapter filter is not working. You get hits outside 
> > > @chapter nodes. 
> > > 
> > > Regards 
> > > Lewis 
> > > 
> > > On Friday, May 26, 2017 at 10:34:40 AM UTC+10, huliuhe wrote: 
> > >> 
> > >> I want to search sth by Nav , But it doesn't work.   I attach the 
> > >> leo file and a jpg. 
> > >> 
> > >> <
> https://lh3.googleusercontent.com/-Xr6jAg6oKEc/WSd31ZL3S1I/AI4/9fe9T1fRV_QNAjWzCopQW1hrx2K3Yr-xACLcB/s1600/abc.jpg>
>  
>
>

-- 
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: Are multiple cursors and selections suported in the body pane?

[Terry Brown]

On Mon, 29 May 2017 17:56:13 -0700 (PDT)
Robert Cholette  wrote:

> Hello, 
> 
> Back from not using leo for many years, 
> 
> After using the multiple cursor/selection that other popular editors
> offer (often made available by CTRL+clicking), I'm wondering if Leo
> now supports a way to have multiple simultaneous cursors (and
> selections) in the body pane?

99.9% sure the answer is no.  There are some old and little used emacs
emulation commands, there might be one that supports pushing / popping
selections, but I don't think so, and that's probably not exactly what
you where looking for anyway.

Cheers -Terry

> (sorry if this question was asked before i searched for this on this 
> google-group and did not get results)
> 
> thanks again -  Leo rocks!
> 

-- 
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: Is it a bug of Nav

[Terry Brown]

On Mon, 29 May 2017 18:44:06 -0700 (PDT)
huliuhe  wrote:

> 
> not body text ?   


It normally searches body text, but only after you hit enter.  Before
hitting enter, it does a kind of live search of headlines only.  After
hitting enter, it shows hits in both body and headlines.

Cheers -Terry

> 在 2017年5月27日星期六 UTC+8下午12:39:08，lewis写道：
> >
> > At first you might think so, but the Quicksearch plugin searches
> > node headlines only, *not* body text.
> >
> > There are a set of filters that can be applied to limit the search:
> > All: Subtree: File: Chapter: Node.
> > However the chapter filter is not working. You get hits outside
> > @chapter nodes.
> >
> > Regards
> > Lewis
> >
> > On Friday, May 26, 2017 at 10:34:40 AM UTC+10, huliuhe wrote:
> >>
> >> I want to search sth by Nav , But it doesn't work.   I attach the
> >> leo file and a jpg.
> >>
> >> 

-- 
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: Is it a bug of Nav

[huliuhe]

not body text ?   



在 2017年5月27日星期六 UTC+8下午12:39:08，lewis写道：
>
> At first you might think so, but the Quicksearch plugin searches node 
> headlines only, *not* body text.
>
> There are a set of filters that can be applied to limit the search: All: 
> Subtree: File: Chapter: Node.
> However the chapter filter is not working. You get hits outside @chapter 
> nodes.
>
> Regards
> Lewis
>
> On Friday, May 26, 2017 at 10:34:40 AM UTC+10, huliuhe wrote:
>>
>> I want to search sth by Nav , But it doesn't work.   I attach the leo 
>> file and a jpg.
>>
>>
>> 
>>
>>
>>
>>

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

Are multiple cursors and selections suported in the body pane?

[Robert Cholette]

Hello, 

Back from not using leo for many years, 

After using the multiple cursor/selection that other popular editors offer 
(often made available by CTRL+clicking), I'm wondering if Leo now supports 
a way to have multiple simultaneous cursors (and selections) in the body 
pane?

(sorry if this question was asked before i searched for this on this 
google-group and did not get results)

thanks again -  Leo rocks!

-- 
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: Python 3 Debug Version can't run Leo-Editor

[Edward K. Ream]

On Mon, May 29, 2017 at 5:19 PM, SegundoBob  wrote:

> The problem is that in order to use the debug version of Python, all the
> c-language Python-extensions that are used with the debug version must also
> be compiled for debugging.
>
> That is, PyQt and SIP must be compiled for debugging.  But thankfully, it
> is *NOT* necessary to compile all of Qt for debugging.
>

​Thanks for this detailed explanation.

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: Python 3 Debug Version can't run Leo-Editor

[SegundoBob]

The problem is that in order to use the debug version of Python, all the 
c-language Python-extensions that are used with the debug version must also 
be compiled for debugging.

That is, PyQt and SIP must be compiled for debugging.  But thankfully, it 
is *NOT* necessary to compile all of Qt for debugging. PyQt source is 
available and it is possible to compile PyQt for debugging, but 
documentation for doing this is probably inadequate.  I don't know how big 
a chore this will be if I eventually try.  There may be other c-language 
Python-extensions used by Leo-Editor that will also need to be compiled for 
debugging.

When Python3-dbg is used to run Leo-Editor, it error terminates during 
start up in module qt_events.py because  the statement "from PyQt5 import 
Qt" fails with error message "ImportError: cannot import name 'Qt'".  The 
import paths at this point is the same for both Python3 (which works) and 
Python3-dbg (which fails).  For Python3 the "Qt" module is .  
This is not a "debug" module.  Python3-dbg requires a module with something 
like a .dm extension.

Possibly useful links:

>
> https://unix.stackexchange.com/questions/168068/python3-dbg-fails-to-import-setproctitle
>
> https://www.riverbankcomputing.com/pipermail/pyqt/2012-April/031385.html
>
>
> https://github.com/spyder-ide/spyder/wiki/How-to-debug-PyQt-PySide-internal-crashes-(segfaults)-affecting-Spyder
>
> http://pyqt.sourceforge.net/Docs/PyQt5/installation.html
>

https://sourceforge.net/projects/pyqt/files/PyQt5/

-- 
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: An unusable outline ...

[Edward K. Ream]

On Mon, May 29, 2017 at 2:41 PM, Viktor Ransmayr 
wrote:

>

>
​I have been thinking what kinds of failures could write zeros instead of
>> proper contents.  At present I can not think of any, but I will keep this
>> question in the back of my mind.
>>
>
> I do appreciate a *lot* that you don't take this issue lightly!
>

​You're welcome. Failures of whatever kind are important, and should be
interesting to any engineer :-)

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: LaTex to PDF workflow using Leo

[Largo84]

Josef, I work with large LaTex files also and have for several years; 
almost all of which contain multiple \input files. My system may not work 
for you, but it works well for me. A few things to note about my system:

   1. My master document outline is a shell only (no actual content). It 
   contains only the preamble, document class and anything else that helps to 
   determine what the document will look like. It's usually auto-created from 
   a set of standard templates.
   2. *All* content resides in separate file outline nodes that might be 
   anywhere and almost never is in the same place as the master document file. 
   I generally use either @file (if sentinels are OK) or @clean (if not) for 
   the content files.
   3. The master document outline nodes will have a sectioning environment, 
   maybe \section{Some Section} followed by \input{"\path\Some_Section.tex"}. 
   This pulls in the content from Some_File.tex wherever it happens to be.
   4. I prefer to *not* include sectioning environments in the content 
   files because for one document, Some_Section content might be a 
   \section{Some Section}, where another document might have the same content 
   as a \subsection{Some Section}.

Good luck and maybe we can share some other ideas to make this work better. 
I'm not a Leo expert, but I depend on it a lot for my writing. HTH

Rob


On Monday, May 29, 2017 at 12:16:14 PM UTC-4, Josef wrote:
>
> Hello Edward,
>
> much of my work involves editing LaTeX files, but I do have to work 
> together with others. I tried Leo's @shadow and @thin nodes, for minimal 
> interference, with mixed success. The main problem is the way Latex uses 
> multi-file input.
>
> As you may remember, the way the rst plugin automatically translates the 
> Leo hierarchy into headings came from a tiny piece of code I once 
> contributed. So, naturally I also thought about creating a latex plugin 
> with automatic hierarchy translation to headings. That would work well as 
> long as the Latex file is one single, large file. 
>
> Most people writing large Latex documents break them down into different 
> chunks and then glue them together with \input. That's where the problems 
> start with using Leo: Leo would have to recreate the same file structure in 
> order to work well together with others, but that would mean one @file 
> statement per .tex file. These @file headings do not necessarily correspond 
> to the document structure. The \input can appear anywhere in the text. An 
> \input may correspond to a new (sub-)section but it also may not. Not every 
> heading will have a corresponding \input either. The Leo tree therefore 
> will not only contain section headings, but also @file nodes corresponding 
> to \input statements and not necessarily corresponding to the document 
> structure. 
>
> Also, one must find the master tex file in order to see the complete 
> hierarchy. Since the files may be distributed over different directories, 
> the importer would have to be told about the master file and would then 
> have to look for all the \input statements recursively (and ignoring 
> commented out \inputs).
>
> I don't know how to solve this problem yet.
>
> - Josef
>
> On Wednesday, 12 April 2017 17:35:21 UTC+2, Edward K. Ream wrote:
>>
>> On Wed, Apr 12, 2017 at 12:10 AM, Largo84  wrote:
>>
>>> Hmm, not sure how that would work. It might be relatively easy to invoke 
>>> such a script when setting up the node at first, but what happens if/when 
>>> you decide to move the node and its level changes? 
>>>
>>
>> ​The situation is much like the rst3 command. I envisage invoking the 
>> script manually whenever you change the source tree.  That would at least 
>> be a good prototype.
>>
>> 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: An unusable outline ...

[Viktor Ransmayr]

Hello Edward,

2017-05-29 13:57 GMT+02:00 Edward K. Ream :

> On Sun, May 28, 2017 at 4:25 PM, Viktor Ransmayr <
> viktor.ransm...@gmail.com> wrote:
> ​>> ​It would seem that backups are your only protection.
>

> ​> ​Agreed for the moment. - But for me it still leaves a bad aftertaste
> ...
>
>
​I have been thinking what kinds of failures could write zeros instead of
> proper contents.  At present I can not think of any, but I will keep this
> question in the back of my mind.
>

I do appreciate a *lot* that you don't take this issue lightly!

With kind  regards,

VR

-- 
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: LaTex to PDF workflow using Leo

[Josef]

Hello Edward,

much of my work involves editing LaTeX files, but I do have to work 
together with others. I tried Leo's @shadow and @thin nodes, for minimal 
interference, with mixed success. The main problem is the way Latex uses 
multi-file input.

As you may remember, the way the rst plugin automatically translates the 
Leo hierarchy into headings came from a tiny piece of code I once 
contributed. So, naturally I also thought about creating a latex plugin 
with automatic hierarchy translation to headings. That would work well as 
long as the Latex file is one single, large file. 

Most people writing large Latex documents break them down into different 
chunks and then glue them together with \input. That's where the problems 
start with using Leo: Leo would have to recreate the same file structure in 
order to work well together with others, but that would mean one @file 
statement per .tex file. These @file headings do not necessarily correspond 
to the document structure. The \input can appear anywhere in the text. An 
\input may correspond to a new (sub-)section but it also may not. Not every 
heading will have a corresponding \input either. The Leo tree therefore 
will not only contain section headings, but also @file nodes corresponding 
to \input statements and not necessarily corresponding to the document 
structure. 

Also, one must find the master tex file in order to see the complete 
hierarchy. Since the files may be distributed over different directories, 
the importer would have to be told about the master file and would then 
have to look for all the \input statements recursively (and ignoring 
commented out \inputs).

I don't know how to solve this problem yet.

- Josef

On Wednesday, 12 April 2017 17:35:21 UTC+2, Edward K. Ream wrote:
>
> On Wed, Apr 12, 2017 at 12:10 AM, Largo84  
> wrote:
>
>> Hmm, not sure how that would work. It might be relatively easy to invoke 
>> such a script when setting up the node at first, but what happens if/when 
>> you decide to move the node and its level changes? 
>>
>
> ​The situation is much like the rst3 command. I envisage invoking the 
> script manually whenever you change the source tree.  That would at least 
> be a good prototype.
>
> 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: Killing script

[Adrian Calvin]

Thank you as always, Edward.

On Sunday, May 28, 2017 at 11:15:08 AM UTC-5, Adrian Calvin wrote:
>
> Hello,
>
> Is there a way to kill a script without killing leo?
>

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

ENB: Completing the event handlers

[Edward K. Ream]

This is an Engineering Notebook post. It consists of notes to myself. It is 
pre-writing for a Theory of Operation for the curses gui code.

This post discusses what is still to be done (not very much) and compares 
the event handlers in the Qt and curses guis.

Definitions:  *User Events* are mouse-down and key events and (Qt only) 
other events generated as the direct result of mouse-downs and key 
presses.  *Leo Events* are events generated by Leo scripts (including 
commands and plugins).

*Qt vs curses*

*Leo events happen only the Qt gui code.* Indeed, Qt itself generates 
events when outline nodes expand or contract, an outline node is selected, 
and the body text changes.  *No such events exist in the curses gui*.

This makes the curses gui code *much* simpler than the Qt gui code. The 
question naturally arises, could the Qt gui code be simplified?  Yes, but 
only if Qt mouse events could do *all* the work of selecting, expanding and 
contracting outline nodes.  If I had it to do over again, I would 
definitely investigate this possibility. Another possible simplification of 
the Qt code would be to use *persistent* headline editors. If this works, 
it would eliminate a lot of bookkeeping in the Qt tree code.

*Strategy*

The curses redraw code is trivial:

if self.widget and not self.busy():
self.widget.update()

This code already works. All but one unit tests pass. Some notes:

1. In the Qt code, the busy() guard prevents endless loops.  This guard 
might go away completely in the curses gui. Most kinds of loops simply 
can't happen because Leo events don't generate user events. At present, the 
code does contain a few lockouts. I'm not sure they can be removed.

2. The overridden LeoMLTree.update method draws only the nodes presently 
visible on the screen. When the user "scrolls" the tree, the newly-visible 
nodes are drawn from scratch.

3. There are no real headline widgets to worry about.  Instead, there are 
LeoTreeLine objects.

*Remaining work*

1. Support more standard key bindings in the body pane.  This will require 
overriding some, perhaps all, of the h_* handlers of the base classes of 
the LeoBody class, namely the InputHandler, MultiLine and MultiLineEditable 
classes. Note that overriding h_* handlers is not enough.  Various tables 
must be updated, so this is a bit tricky.

2. The key handlers must update p.b and p.h as required. In the Qt gui, 
this involves very tricky calls to onBodyChanged and onHeadChanged.  I 
expect that these calls will be simpler in the curses gui.

3. Fixing the one failing unit test. This tests whether all text is 
selected when creating a new node. This is a localized failure, but 
attempts to fix it have spoiled other tests...

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: An unusable outline ...

[Edward K. Ream]

On Sun, May 28, 2017 at 4:25 PM, Viktor Ransmayr 
wrote:

​>> ​
It would seem that backups are your only protection.

​> ​
Agreed for the moment. - But for me it still leaves a bad aftertaste ...

​I have been thinking what kinds of failures could write zeros instead of
proper contents.  At present I can not think of any, but I will keep this
question in the back of my mind.

In particular, I do not think g.FileLikeObject can have this failure mode.​
It's a mystery.  I am inclined to think it is a strange failure of your
hardware or OS.

I myself suffer from a very strange problem on my Windows 10 system. It
seems that files are not closed properly in some cases. This clearly is
unrelated to Leo.

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.