Re: MACOS M2 Ventura

[Geoff Evans]

Thanks Thomas,
When I worked up the courage to adjust my qt.conf file as suggested, 
everything worked! :-)
I'll have to get used to the options living at the top of the main screen 
and not the top of the leo window.  But that's a minor issue.

geoff

On Sunday 7 April 2024 at 05:39:32 UTC-2:30 Edward K. Ream wrote:

>
>
> On Sat, Apr 6, 2024 at 6:27 AM Thomas Passin  wrote:
>
>> Solved in
>>
>>
>> https://stackoverflow.com/questions/76898551/qt-qpa-plugin-could-not-find-the-qt-platform-plugin-cocoa-in
>
>
> Thanks for your help, Thomas.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c3b3c809-5153-4116-aad1-bcc7612ee8c3n%40googlegroups.com.

MACOS M2 Ventura

[Geoff Evans]

I've tried to get leo via pip:

pip install pyqt6 leo

but when I try to run it I get:

 ~/WXP/OGMAP/now/base > leo ogmap.leo 
qt.qpa.plugin: Could not find the Qt platform plugin "cocoa" in ""
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem.

The obvious "pip install cocoa" didn't help.  Any ideas?

geoff


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/08babe16-3846-4eb7-b29f-d2f705e99e57n%40googlegroups.com.

Re: FYI: Simplified installation instructions

[Geoff Evans]

Obvious question: if I use both Anaconda *and* MacOS (Ventura), which part 
of the Installation instructions supersedes the other?  Is Homebrew 
necessary?
I've still not succeeded with pyqt6.

Unrelated question:
The traffic on this site is, quite understandably, dominated by the latest 
exciting innovations.  So that I'm not sure where to find beginnings any 
more.  
Where do I go to find a gentle introduction to, say, ViewRendered or LeoJS: 
the bit that tells me what might be the payoff if I jump into the details 
of them?
[Though I probably won't jump in: a nice editor-outliner with clones and a 
literate approach will let me organize my science nicely, alongside jupyter 
notebooks that do the details.
Maybe the main thing I need to learn, for sharing with colleagues, is 
make-sphinx?]

geoff

On Sunday 3 March 2024 at 09:12:40 UTC-3:30 Edward K. Ream wrote:

> Leo's "devel" and "6.7.8" branches now contain simplified installation 
> instructions. These instructions are now live on Leo's website.
>
> A few changes turned into general housecleaning:
>
> - Greatly simplified the Getting Started 
> and 
> Installation  
> pages.
> - Removed all "download" links. The "installation" instructions suffice!
> - Use PyPi links for most dependencies.
> - Moved several obsolete related FAQ and HowTo entries to the "archive" 
> node in LeoDocs.leo.  I'll delete these archive entries in the release 
> *after* 6.7.8.
> - Simplified the instructions (in LeoDocs.leo) about generating the 
> documentation:
>   Just use the make-sphinx button from the gh-pages branch!
>
> All questions and comments are welcome.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/3626652e-18fb-409b-b115-fd2fe761f9f4n%40googlegroups.com.

Re: Leo's PyPi page will remain

[Geoff Evans]

Thanks Thomas for the pyqt6 reminder (I remembered doing something like 
that years ago, but not precisely what ;-)
Now I get 
"qt.qpa.plugin: Could not find the Qt platform plugin "cocoa" in ""
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem. "

re-installing didn't make any difference.

geoff

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/fa8a2104-ca77-427a-abc4-aa7643ca9648n%40googlegroups.com.

Re: Leo's PyPi page will remain

[Geoff Evans]

(Sorry; forgot to say this is in MacOS)

On Sunday 11 February 2024 at 16:03:48 UTC-3:30 Geoff Evans wrote:

> Thanks Edward, I tried that and got further than I did 2 weeks ago.  "pip 
> install leo" apparently works but when I then type  "leo" I get
> Can not load the requested gui: qt
> Then when I try "pip install qt" I get "ERROR: No matching distribution 
> found for qt".  What am I missing?
>
> Cheersgeoff
>
> On Sunday 11 February 2024 at 08:27:39 UTC-3:30 Edward K. Ream wrote:
>
>> I have deleted the ill-fated 6.7.7.1 release from Leo's PyPi page 
>> <https://pypi.org/project/leo/>.
>>
>> pip install leo should work again as before.
>>
>> Issue #3767 <https://github.com/leo-editor/leo-editor/issues/3767> now 
>> suggests supporting pip install -r requirements.txt
>> as an easy way to install requirements *from within a cloned GitHub repo*
>> .
>>
>> All comments and questions are welcome.
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/a6a31191-b8b0-40e3-b9cb-26b8367348f9n%40googlegroups.com.

Re: Leo's PyPi page will remain

[Geoff Evans]

Thanks Edward, I tried that and got further than I did 2 weeks ago.  "pip 
install leo" apparently works but when I then type  "leo" I get
Can not load the requested gui: qt
Then when I try "pip install qt" I get "ERROR: No matching distribution 
found for qt".  What am I missing?

Cheersgeoff

On Sunday 11 February 2024 at 08:27:39 UTC-3:30 Edward K. Ream wrote:

> I have deleted the ill-fated 6.7.7.1 release from Leo's PyPi page 
> .
>
> pip install leo should work again as before.
>
> Issue #3767  now 
> suggests supporting pip install -r requirements.txt
> as an easy way to install requirements *from within a cloned GitHub repo*.
>
> All comments and questions are welcome.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/5bd4a31b-06a9-4ff2-be98-f7cd13a8c9adn%40googlegroups.com.

Re: Thumb-nail Explanation Of Leo

[Geoff Evans]

This reminds me of something I posted in 2012 (!)  It takes its starting 
point not from what Leo is, but from the sorts of things people might want 
to use and program a computer for in the first place which, for many of us, 
have very little to do with editing.  Here is is again:



I should start by saying that I use Leo daily and wouldn't now consider 
starting any project lasting more than a week without it. I'm immensely 
grateful to Edward and the community of collaborators for creating and 
polishing it. Two things prompt me nevertheless to write. First, I have 
a strong feeling that there are ways I could be using it better, to make 
my life even easier, if only I could manage to break into them; secondly, 
Edward asks from time to time something like "Why isn't everybody using 
Leo and what would it take to convert more people?" Maybe the following 
will be a contribution. 

When I started programming in Python a couple of years ago, and started 
learning about object-oriented principles, one that struck me especially 
was "Program to the interface, not the implementation." (It often takes 
me a while to remember this when I'm working; but it always makes things 
better when I do.) My "Aha" moment a couple of months ago came when I 
realized that this wasn't true only of programming -- the same principle 
applies to writing as well. Papers that jump right in to telling me what 
the author did don't work nearly as well as those that start with the 
reader and what s/he might care about and how the author proposes to 
help with that. 

[Isn't it interesting that the maxim I quoted above disobeys itself, 
because 
it refers to the implementation in a computer program whereas the 
real interface is the general act of communication and the primacy of the 
receiver over the transmitter.] 

So I envisage a tutorial starting as follows (sketch only): 

Suppose you have a project that entails using some data, doing some 
computations, and writing up the results. If you want to easily: 

-- work on / store / contemplate the project as a unified whole 
[Leo manages all relevant files in one outline] 

-- see and work on one small part in its context 
[Leo is an outliner] 

-- copy thoughts, results from one context to another 
[clones] 

-- switch between interactive and batch processing 
[iPython interface] 

-- produce nice printed (literate?) documentation for those who don't 
use Leo or don't do all their work glued to a computer screen 
[rst3? noweb? Fweb? maybe little sample batch files with all the 
required steps?] 

-- ??? 
[scripting] 
And here I'm stuck: Leo documentation assures me that scripting is an 
amazingly powerful answer, but doesn't tell me what questions I might 
like to ask, or what needs I might have, that it is an answer to. It 
simply tells me what to do if I already know why I want to. 

-- Here is where the community may want to contribute ways Leo has made 
their working lives easier and more productive, by meeting existing needs 
or wishes that had nothing intrinsically to do with Leo. 

I envisage this as complementing the existing tutorial in leodocs. It 
may provide an entrance that a different class of potential user would 
find attractive. Or maybe I just need someone to gently point me to 
where what I am suggesting already exists ;-) 

Cheers, geoff evans

---

Major offshoots in the last decade (e.g.ViewRendered) suggest further 
examples of "if you want to easily ..." that people who use and understand 
them could provide.

Confession:  Most of what I used to do with Leo I now do with Jupyter 
notebooks.  This is partly because my collaborators are more likely to know 
and use it,
but also possibly because the documentation tends to take it for granted 
that a feature is valuable so all that is necessary is to show me how (but 
not why)
to use it.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/65fd0504-2985-4dd1-9b1c-80b728ae5cd2n%40googlegroups.com.

Re: leo stops working

[Geoff Evans]

< pip install leo >   appeared to work (once I banished all the 5.9 stuff 
to a directory outside anaconda), but when I tried to run leo:

(base) geoff:1520>leo mbr.leo

setting leoID from os.getenv('USER'): 'geoff'
Leo 6.2.1 final
Segmentation fault (core dumped)

But at least the complaint about meta went away ;-)
On Saturday, 25 July 2020 at 20:36:34 UTC-2:30 tbp1...@gmail.com wrote:

> I assumed from one of your sentences that somehow it had been provided by 
> apt.  Probably not - I'd just been thinking that apt upgraded Python, 
> really..  As I just found out, a system upgrade can require a whole new 
> installation of Leo using pip/pip3, which brings in new versions of all 
> Leo's dependencies.
>
>
> On Saturday, July 25, 2020 at 4:17:25 PM UTC-4, Geoff Evans wrote:
>>
>> Thanks, I'll try that when I'm better able to concentrate if things start 
>> going wrong.
>> One puzzle, though: you refer to the Ubuntu package manager providing it: 
>> I didn't think leo was part of the Ubuntu distribution.
>> (What I'd really love is if it was part of the Anaconda distribution :-)
>>
>> geoff
>>
>> On Saturday, 25 July 2020 at 11:24:36 UTC-2:30 tbp1...@gmail.com wrote:
>>
>>> v5.9 is very old by now.  I'm surprised that the Ubuntu package manager 
>>> is still providing it.  The chances of troubleshooting this package are 
>>> probably small at this point.
>>>
>>> I'd suggest installing the current version of Leo directly using pip.  
>>> Make sure that you have python 3.6+ on your system.  You may have to use 
>>> apt-get to get pip installed - some distros don't include it with Python, 
>>> some do, and I don't remember about Ubuntu.  It may need to be called pip3 
>>> to make sure it's the one for Python 3.x. Then install Leo:
>>>
>>> pip3 install leo  # pip3 instead of pip should make sure you are using 
>>> the Python 3.x version instead of the Python 2.7 version.
>>>
>>> Or to see which versions are available:
>>>
>>> pip3 install leo==
>>>
>>> On some systems you might need to use sudo:
>>>
>>> sudo pip3 install leo
>>>
>>> Or, if the system isn't finding the correct version of pip:
>>>
>>> python3 -m pip install leo# python3 will launch the available 
>>> version of pip for Python 3.x
>>>
>>> As of today, the latest version of Leo available this way is 6.2.1.
>>>
>>> On Saturday, July 25, 2020 at 9:30:30 AM UTC-4, Geoff Evans wrote:
>>>>
>>>> When I try to run leo now (in Ubuntu 18.04) I get:
>>>>
>>>> (base) geoff:1427>leo ogmap.leo
>>>>
>>>> setting leoID from os.getenv('USER'): 'geoff'
>>>> Leo 5.9-b2, build 20190409061733, Tue Apr  9 06:17:32 UTC 2019
>>>> livecode.py: can not import meta
>>>> pip install meta
>>>> Segmentation fault (core dumped)
>>>>
>>>> It used to work fine; all I can think of that's changed is that I've 
>>>> done "apt-get update/upgrade": cuold that have broken a prerequisite?
>>>>
>>>> Best,   geoff
>>>>
>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/000e7cdb-ef6d-4803-86a5-24ab73359b75n%40googlegroups.com.

Re: leo stops working

[Geoff Evans]

Oohhh!  So maybe after I upgraded Ubuntu I needed to "conda update 
anaconda" ??  I'll try that first and see what happens.

On Saturday, 25 July 2020 at 20:36:34 UTC-2:30 tbp1...@gmail.com wrote:

> I assumed from one of your sentences that somehow it had been provided by 
> apt.  Probably not - I'd just been thinking that apt upgraded Python, 
> really..  As I just found out, a system upgrade can require a whole new 
> installation of Leo using pip/pip3, which brings in new versions of all 
> Leo's dependencies.
>
>
> On Saturday, July 25, 2020 at 4:17:25 PM UTC-4, Geoff Evans wrote:
>>
>> Thanks, I'll try that when I'm better able to concentrate if things start 
>> going wrong.
>> One puzzle, though: you refer to the Ubuntu package manager providing it: 
>> I didn't think leo was part of the Ubuntu distribution.
>> (What I'd really love is if it was part of the Anaconda distribution :-)
>>
>> geoff
>>
>> On Saturday, 25 July 2020 at 11:24:36 UTC-2:30 tbp1...@gmail.com wrote:
>>
>>> v5.9 is very old by now.  I'm surprised that the Ubuntu package manager 
>>> is still providing it.  The chances of troubleshooting this package are 
>>> probably small at this point.
>>>
>>> I'd suggest installing the current version of Leo directly using pip.  
>>> Make sure that you have python 3.6+ on your system.  You may have to use 
>>> apt-get to get pip installed - some distros don't include it with Python, 
>>> some do, and I don't remember about Ubuntu.  It may need to be called pip3 
>>> to make sure it's the one for Python 3.x. Then install Leo:
>>>
>>> pip3 install leo  # pip3 instead of pip should make sure you are using 
>>> the Python 3.x version instead of the Python 2.7 version.
>>>
>>> Or to see which versions are available:
>>>
>>> pip3 install leo==
>>>
>>> On some systems you might need to use sudo:
>>>
>>> sudo pip3 install leo
>>>
>>> Or, if the system isn't finding the correct version of pip:
>>>
>>> python3 -m pip install leo# python3 will launch the available 
>>> version of pip for Python 3.x
>>>
>>> As of today, the latest version of Leo available this way is 6.2.1.
>>>
>>> On Saturday, July 25, 2020 at 9:30:30 AM UTC-4, Geoff Evans wrote:
>>>>
>>>> When I try to run leo now (in Ubuntu 18.04) I get:
>>>>
>>>> (base) geoff:1427>leo ogmap.leo
>>>>
>>>> setting leoID from os.getenv('USER'): 'geoff'
>>>> Leo 5.9-b2, build 20190409061733, Tue Apr  9 06:17:32 UTC 2019
>>>> livecode.py: can not import meta
>>>> pip install meta
>>>> Segmentation fault (core dumped)
>>>>
>>>> It used to work fine; all I can think of that's changed is that I've 
>>>> done "apt-get update/upgrade": cuold that have broken a prerequisite?
>>>>
>>>> Best,   geoff
>>>>
>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ab2df605-0f97-44e3-9e44-6a60cae8d9a2n%40googlegroups.com.

Re: leo stops working

[Geoff Evans]

Thanks, I'll try that when I'm better able to concentrate if things start 
going wrong.
One puzzle, though: you refer to the Ubuntu package manager providing it: I 
didn't think leo was part of the Ubuntu distribution.
(What I'd really love is if it was part of the Anaconda distribution :-)

geoff

On Saturday, 25 July 2020 at 11:24:36 UTC-2:30 tbp1...@gmail.com wrote:

> v5.9 is very old by now.  I'm surprised that the Ubuntu package manager is 
> still providing it.  The chances of troubleshooting this package are 
> probably small at this point.
>
> I'd suggest installing the current version of Leo directly using pip.  
> Make sure that you have python 3.6+ on your system.  You may have to use 
> apt-get to get pip installed - some distros don't include it with Python, 
> some do, and I don't remember about Ubuntu.  It may need to be called pip3 
> to make sure it's the one for Python 3.x. Then install Leo:
>
> pip3 install leo  # pip3 instead of pip should make sure you are using the 
> Python 3.x version instead of the Python 2.7 version.
>
> Or to see which versions are available:
>
> pip3 install leo==
>
> On some systems you might need to use sudo:
>
> sudo pip3 install leo
>
> Or, if the system isn't finding the correct version of pip:
>
> python3 -m pip install leo# python3 will launch the available 
> version of pip for Python 3.x
>
> As of today, the latest version of Leo available this way is 6.2.1.
>
> On Saturday, July 25, 2020 at 9:30:30 AM UTC-4, Geoff Evans wrote:
>>
>> When I try to run leo now (in Ubuntu 18.04) I get:
>>
>> (base) geoff:1427>leo ogmap.leo
>>
>> setting leoID from os.getenv('USER'): 'geoff'
>> Leo 5.9-b2, build 20190409061733, Tue Apr  9 06:17:32 UTC 2019
>> livecode.py: can not import meta
>> pip install meta
>> Segmentation fault (core dumped)
>>
>> It used to work fine; all I can think of that's changed is that I've done 
>> "apt-get update/upgrade": cuold that have broken a prerequisite?
>>
>> Best,   geoff
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/6058ddc4-6e9b-410e-a883-299cd4b89eabn%40googlegroups.com.

leo stops working

[Geoff Evans]

When I try to run leo now (in Ubuntu 18.04) I get:

(base) geoff:1427>leo ogmap.leo

setting leoID from os.getenv('USER'): 'geoff'
Leo 5.9-b2, build 20190409061733, Tue Apr  9 06:17:32 UTC 2019
livecode.py: can not import meta
pip install meta
Segmentation fault (core dumped)

It used to work fine; all I can think of that's changed is that I've done 
"apt-get update/upgrade": cuold that have broken a prerequisite?

Best,   geoff

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/0b5b0f5d-9e2a-4622-bc5c-f6cd7bdb47c2o%40googlegroups.com.

Re: Guide to writing better software documentation

[Geoff Evans]

Thanks Edward, that clears that up for me.  I still find it a bit odd that 
there was an announcement that Leo now supports jupyter, without any 
account of what the support consisted of and whom it might be useful for.

Leaving aside this specific example, I think my overall point about another 
component of documentation is still valid, even if I'm having trouble 
formulating it.  Maybe a better way to say it would be to break Tutorials 
into "for the committed" and "for the curious".  In the latter, experienced 
Leo people could be encouraged to write simple examples of "How this Leo 
feature helps me to accomplish the things I actually use a computer for."

Best,   geoff

On Saturday, 9 November 2019 07:30:27 UTC-3:30, Edward K. Ream wrote:
>
> On Sat, Nov 9, 2019 at 3:52 AM Geoff Evans  > wrote:
>
> Okay, the basic question:  What is a very simple .leo file that will 
>> create a .ipynb file for a notebook with one markdown cell and one code 
>> cell that reports the outcome of some calculation?
>>
>
> Leo doesn't provide that kind of support, and none is planned at present.
>
> Leo's ipynb importer and corresponding writer allow limited 
> round-tripping.  It's probably not all that useful.
>
> You could define an abbreviation that would create an empty Jupyter 
> notebook, but that would likely be of even less use.  Far better to create 
> your notebooks in Jupyter.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/226f516c-5c46-4069-8a40-db081a641aa7%40googlegroups.com.

Re: Guide to writing better software documentation

[Geoff Evans]

Okay, the basic question:  What is a very simple .leo file that will create 
a .ipynb file for a notebook with one markdown cell and one code cell that 
reports the outcome of some calculation?
I tried:

@file Note.ipynb
  @others
- - -title
   @language markdown
   ## Title
- - -calculation
@language python
x=4
print(x+3)

but got something that didn't look like the format of other .ipynb files I 
have.

On Friday, 8 November 2019 09:38:40 UTC-3:30, Edward K. Ream wrote:
>
>
>
>  
>
>> The sort of thing I envisage goes:
>> "Can I do this useful (for my end purpose) thing with Leo?"
>>
>
> Leo's FAQ contains how-to's.  Feel free to suggest additions.
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/d17969d3-e06e-41bf-839b-1fdfe5ba530b%40googlegroups.com.

Re: Guide to writing better software documentation

[Geoff Evans]

I wonder if there's a fifth function missing from the list, especially if 
one construes 'documentation' broadly as 'what a person wants to be able to 
find out about the tool'.  I'm torn between calling it Invitation or 
Questions, but it's basically "What sorts of things can this program, or 
feature, do for me; why might I want to invest in learning it?"

Leo seems to me to be somewhat lacking here, especially at its growing 
points.  An example that bothers me particularly: I was happy when I read 
that Leo now supports jupyter notebooks.  But I've tried to go through the 
documentation carefully and I can't discover what the support consists of.  
How can Leo enhance how I use a jupyter notebook?  The sort of thing I 
envisage goes:
"Can I do this useful (for my end purpose) thing with Leo?"   "Yes:  there 
is a module called yyy that can help you do that sort of thing.  Here's a 
sketch of how."

Scripting seems to be another candidate: start with an ability that a 
newbie can see an immediate use for, and demonstrate the script that 
accomplishes it.  Make this the first thing in the tutorial perhaps (so 
maybe what I'm saying is that tutorials would work better if they made it 
clear at the start why one might want to take them?)  Or there are other 
projects discussed in this group (ViewRendered, pyzo, ...) that I have paid 
no attention to because I never found a statement of what they could do for 
me or how they could enhance what I want to do.

Saying this in yet another way, I was struck ages ago by a sentence of 
Edward's:  "After that, leoPyRef.leo contains all the answers."   To which 
my immediate response was: "Yes, but where do I find the questions (for 
end-use purposes) that Leo offers good answers to?"

- geoff

On Saturday, 26 October 2019 19:05:57 UTC-2:30, Matt Wilkie wrote:
>
> Found by way of Guido von Rossum in python discussion forum:
> https://www.divio.com/blog/documentation/
>
> Basically: recognize there are 4 kinds of documentation, serving different 
> functions. Design, write and store them differently. It's in mixing them up 
> in one document/place that leads to mess and confusion on both the author 
> and consumer side. The four are: Tutorials, How-to's, Explanations, and 
> Reference.
>
> I found it to be a good read and intend to see how I can apply it to my 
> work.
>
> -matt
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/31426ca4-7f52-4b6d-9ad0-8fd7d82be57c%40googlegroups.com.

Re: problem installing Leo on Linux

[Geoff Evans]

That worked!  Leo starts nicely now.
Many thanks Matt and Vitalije.

geoff

On Monday, 5 August 2019 13:33:44 UTC-2:30, Matt Wilkie wrote:
>
> PyQt v5.13.0 should work, it does for sure on Windows. Is PyQtWebEngine 
> installed? Try `pip show PyQtWebEngine`. If not then try `pip install 
> PyQtWebEngine`.
>
> It's supposed to be installed automatically but adding it as a distinct 
> package was a change added recently 
>  and it hasn't been 
> widely tested.
>
> -matt
>
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/33e1e59a-871b-4164-ada2-51e16322fdcb%40googlegroups.com.

Re: problem installing Leo on Linux

[Geoff Evans]

Thanks Vitalje
I get:
5.13.0

On Monday, 5 August 2019 08:24:03 UTC-2:30, vitalije wrote:
>
> Most probably it is the PyQt5 version that is newer than Leo expects.
> Try executing the following line in the terminal.
> python -c "from PyQt5 import Qt;print(Qt.qVersion())"
>
> And report here what is the output you get.
>
> I remember having to install an older version of PyQt5 in order to make 
> Leo work.
>
> Vitalije
>
> On Monday, August 5, 2019 at 11:59:47 AM UTC+2, Geoff Evans wrote:
>>
>> I'm using Leo happily on different computers and operating systems, but 
>> when I try to install on a new Linux computer I run into trouble.
>> I started by installing Anaconda (version current as of the week before 
>> last) as Edward suggests, and then followed instructions on the 
>> leoeditor.com web site.  I first tried "pip install leo", and then 
>> downloaded the source code and tried to run "python pathname/launchLeo.py" 
>> and got the same error messages both times:
>>
>> cannot import name 'QtWebKit' from 'PyQt5'
>>
>> additional error:
>> ...
>>
>> from PyQt5 import QtWebEngineCore as QtWebKit
>> PyCapsule_GetPointer called with an incorrect name
>>
>> Can anyone help?  (1) What did I do wrong?  (2) How can I fix it?  (3) 
>> How should I have been able to use the documentation to find out for myself?
>>
>> Thanks,   geoff evans
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/68b7cdb1-69d0-4456-8e82-cc2632bbdce6%40googlegroups.com.

problem installing Leo on Linux

[Geoff Evans]

I'm using Leo happily on different computers and operating systems, but 
when I try to install on a new Linux computer I run into trouble.
I started by installing Anaconda (version current as of the week before 
last) as Edward suggests, and then followed instructions on the 
leoeditor.com web site.  I first tried "pip install leo", and then 
downloaded the source code and tried to run "python pathname/launchLeo.py" 
and got the same error messages both times:

cannot import name 'QtWebKit' from 'PyQt5'

additional error:
...

from PyQt5 import QtWebEngineCore as QtWebKit
PyCapsule_GetPointer called with an incorrect name

Can anyone help?  (1) What did I do wrong?  (2) How can I fix it?  (3) How 
should I have been able to use the documentation to find out for myself?

Thanks,   geoff evans

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/04a653a2-1d05-41d6-8cb4-45d35162350e%40googlegroups.com.

Re: Noobie to try Leo on Mac OS for thoughts IDE

[Geoff Evans]

Hi Andy,
   For me at least, all it took was installing the Anaconda distribution of 
python.  This includes all the tools you need (pyqt for example) so that 
there's no need to get into Homebrew.
A command in a Terminal window, in the directory where you want your .leo 
file to live, something like

python /Users/gte/Leo-5.3-final/launchLeo.py ogmap.leo &

should get you going.  [Oh dear!  Here I'm accidentally confessing how lax 
I am in updating to the latest and greatest version.]  Good luck:  it's 
definitely worth the investment of effort!

geoff

On Sunday, January 7, 2018 at 12:26:31 AM UTC-3:30, andyjim wrote:
>
> I want an IDE/organizer for thoughts, ideas, journaling, writing.  I have 
> hundreds of past files of journals/thoughts to parse and organize plus my 
> ongoing thinking/journaling addiction.  Only thing I know of that may be 
> close is Zettelkasten, but I haven’t dug into that yet, and don’t know if 
> there’s a mature app for it.  I may be barking up the wrong tree here but 
> thought I'd give Leo a try. 
>
>
> Not only am I a noobie to Mac, I am not a programmer and not a Linux user. 
> Quite a case (refugee from Windows and don't think I'll go back).  I do not 
> know whether Leo will suit my needs but nothing else does and I’d like to 
> give it a shake, though it seems the learning curve will be steep for me.
>
>
> So my first challenge is getting it installed in High Sierra.  I see what 
> is for me a complex and somewhat cryptic guide for installing on MacOs 10.7 
> (I know nothing of Homebrew, for example). Is this the most current 
> information on a Mac installation?  Will that guide get me through it?
>
>
> Perhaps someone here just needs to gently steer me away from Leo as 
> unsuitable for my needs or my noobie-ism.  Or perhaps someone will say 
> ‘You’ve come to the right place and here’s how to get started!’
>
>
> Happy New Year!
>
>
> Andy
>

-- 
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: Turning to documentation

[Geoff Evans]

This encouraging development prompts me to throw something into the mix 
that's been on my mind for a while.

1.  It starts with Edward's Stupendous Aha about tests from months ago, 
which goes roughly:
A good test is both
  (a)  an illustration of something the program should do;
  (b)  an ability to detect if the program isn't doing it.
In this light, tests appear as helpers toward understanding rather than 
obstacles to be overcome.

2.  Then there's a perennial question: Why don't more people use Leo (or 
more of its capabilities)?  In my mind (and there are those who agree with 
this), one part of the answer is that the documentation is hard to use.

3.  So:  ** What are the tests for documentation? **
Saying that documentation needs tests implies saying that it should *do* 
something, not just *contain* something.  I suggest that at the top level 
what it should do is:
  (a) Invite.  Persuade potential users that Leo offers something they 
want, that their current tools don't supply.  And that they can get at 
least a working version of what they want with a modest investment of 
effort.  Possible subjects for invitations: Leo as a whole; scripts; ILeo 
(how is it better than using %cpaste in a separate IPython window?); vi 
emulation.
  (b) Guide.  (aka Tutorial?)  Given someone who has decided to invest some 
effort, take her through the steps to reach some worthwhile goal.  Perhaps 
best implemented as a set of plateaus, each plateau having a set of 
signposts for choices of where to be guided next.
  (c) Be consulted.  Someone has started to use Leo regularly has a 
detailed question (How do I change the font size?  How do I make python 
indent using 3 spaces instead of 4?) and a generic question:  How do I 
navigate the documentation to answer the detailed question?  For the first 
of my examples, the best I can come up with is "Poke around in leoSettings 
for something that says 'font' and play with changing that in 
myLeoSettings"; for the second example, "I have no idea".

Of course, if I knew Leo better I could have said more sensible things 
here.  Chicken and egg.

Cheers,   geoff

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

lost bits of code

[Geoff Evans]

Every once in a while, after working on an outline and closing it, I find 
that I'm missing bits of code when I next reopen it.  As far as I can tell, 
this happens when I intermix comment (following @) and code (following @c) 
in the same node.  When I write something like

@c
first code block
@
comment block
@c 
second code block

the second code block might not be there the next time I open the outline. 
 Am I doing something silly or prohibited?

Cheers,   geoff

-- 
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: open: window or tab?

[Geoff Evans]

Thanks Edward,
I shan't bug you with a bug report: you have more interesting or 
important things to do.
(I assume it's an issue with OS X and not with Leo 5.3)

geoff

On Tuesday, September 20, 2016 at 11:54:29 AM UTC-2:30, Edward K. Ream 
wrote:
>
> On Tue, Sep 20, 2016 at 8:54 AM, Geoff Evans <gtev...@nl.rogers.com 
> > wrote:
>
>> In the environment I'm trying to get working (OS X El Capitan / Anaconda 
>> / Leo 5.3), there is no tab at the top of the Leo window and when I open a 
>> new .leo file it opens in a new window.   What do I change to make it open 
>> in a new tab instead?
>>
>
> ​You don't.  I don't remember what the problem is/was, but the workaround 
> was not to use tabs.
>
> Feel free to file a bug report.  This will remind me to attempt a fix.
>
> 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.

open: window or tab?

[Geoff Evans]

In my usual Leo environments (4.11 in one place, 5.1 in another, both 
Ubuntu) the top of the Leo window is a tab with the name of the .leo file 
I'm using.  When I open another .leo file, it appears in a new tab.

In the environment I'm trying to get working (OS X El Capitan / Anaconda / 
Leo 5.3), there is no tab at the top of the Leo window and when I open a 
new .leo file it opens in a new window.   What do I change to make it open 
in a new tab instead?

Also in the OS X environment neither Ctrl-F not Apple-F gives me a search; 
only going to the Search tab works.

And, as ever:  Where should I have looked in the documentation to find out 
without bothering this list?

Cheers,geoff

-- 
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: A note to new users

[Geoff Evans]

As the 'new' (since 2009) user John mentioned, I totally endorse what he 
says about how friendly and helpful the Leo community is in dealing with 
questions.   But I'm also old enough to be fond of written documentation. 
 This note is one offering towards Edward's desire for outreach to more 
users and how the documentation could serve that purpose.  I am looking for 
something that will persuade a non-user to try leo, and persuade a new user 
that a small effort in learning a bit more often brings a big reward. 
 Years of editing and reviewing for international scientific journals, plus 
decades of making my own mistakes, have taught me the value of just-in-time 
delivery of ideas, and of writing to the interface not the implementation. 
 So before even the Tutorial (which is still basically about How rather 
than What and Why) I envisage a section built around people's needs and 
indicating how they would go about meeting them with Leo.  Something like 
(trying to use the format in Jacob Peck's scripting example):
-A Taste of Leo
  Leo is a system that lets you enter information and keep track
  of how it's organized.  Leo's main window has two large parts 
  that contain your information:  an outline pane toward the top
  left and a body pane [I always toggle the split direction] on
  the right.  The body pane contains information related to the
  highlighed headline in the outline pane; headline and body pane
  together are referred to as a node.
-Staples
  There are many ways to instruct Leo: commands, directives,
  scripts, buttons, abbreviations   This part gives
  brief examples of the kind of thing each does.
-Command
  Does something immediately.
  You want to insert a new node into your outline:
Alt-X insert-node  [Ctrl-I]
  Typing 'Alt-X' put you in a minibuffer at the bottom of
  the main window, where you type the rest of the 
  command.  This is such a common command that there is a
  keyboard shortcut for it.  But there are scores of
  commands, most of which have to be entered the Alt-X
  way (tab completion can make it less onerous).
  You want to seach for something in the outline:
Alt-X find   [Ctrl-F]
  is a flexible command that, for example, lets you 
  search only headlines, and offers search-and-replace.
-Directive
  Doesn't do anything immediately, but sets up ground
  rules that will be followed in that node and all 
  children until overridden.
  You want syntax colouring appropriate the the language
  you're programming in
@language python
  turns it on.
  You want to save a subtree in an external file where
  another program can access it.
@file file.name
  directs that the node and all children will be saved in
  a separate file called file.name .
-Setting
  Controls how a whole Leo session will look.
  You always want your body pane to the right of the
  outline pane, whereas by default Leo will put it below.
  Edit the file myLeoSetttings.leo (which you access by
  clicking the Settings tab near the top of the main
  window -- or the Help tab in older Leo versions such
  as the picture in the current Leo5.1 documentation) by
  adding a line
@bool split_direction = vertical
  Settings don't take efffect immediately, but only in
  the next leo session you open.  [Though when you're
  experimenting to see how they work, you can put a
  @settings tree in the outline you're working on,
  add your lines there, and they take effect when you
  save and reopen the file in the same Leo session.]
-Script
  I can't give an example of something I want that a 
  script will do for me.
-Treats
  This is the place to put some representative gems.  I seem
  to recall Edward suggesting this somewhere in the thread on 
  Leo's future, though I can't find it now.  But they have to
  be things that make a new user say: "I hadn't thought of
  using Leo for that.  Now that I think of it, I can see
  wanting to.  I'm confident now I can work out how for my
  own needs."  
  But the first treat is obvious:
-Clone
  You have a task that belongs in Project A, that you 
  need to work on next week.  So you enter a node for
  the task under , type Ctrl-` , and you have
  a copy of the node you can move to under 
  *and* when you modify your description in one place,
  the same modifications happen in the other.
Okay, that's enough ignorant comment from me.  People who really know Leo 
can correct all the mistakes I've made and add more and better treats and 
examples.  
One other thought:  there are places 

Re: Does @clean go too far?

[Geoff Evans]

Thanks, all, for your thoughts (and sorry I couldn't respond over the 
weekend)
 
1)  I agree it's not a big issue.  As Edward writes: It's not something 
that would add a great deal to Leo in any case: if you are using Leo the 
sentinels don't matter.  Though the same could be said for @clean istelf.  
The point would be to add something to extra-Leo use, which includes not 
only colleagues who won't use Leo but also the modes of my brain that are 
switched on by working with and on paper.
 
2)  Perhaps the strongest case would be for outlines that make heavy use of 
Organizer nodes with no text in the body pane:  @clean will remove all 
evidence they existed.
 
3)  A solution is in my own hands:  Copy what I want from the headline to 
the top of the body node.  This may be my impetus to learn enough about 
scripting to automate that :-)   And I should study Terry's suggestion.
 
Cheers,  geoff
 
 

-- 
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: Does @clean go too far?

[Geoff Evans]

Okay, that python program was a bad example because the artificial 
headlines were redundant.  But there are many instances of outlines where 
the text in the headline is nothing like the text in the body pane.

The essence of what I wanted to say:

My intuition of a 'clean' file is one that reflects just what I typed.
What I typed includes the body panes *and* the outline pane (including its 
indentations).
@clean as implemented includes only the body panes.
  
I am sorry I wrote you such a long letter; I didn't have time to write a 
short one.  -- Blaise Pascal

On Friday, August 21, 2015 at 7:34:35 AM UTC-2:30, john lunzer wrote:

 I would be inclined to agree, it does look like redundant information. 
 There would however be some benefit to some sort of delineation made 
 between nodes, but I'm not proposing a new node type to do so. I think to 
 be perfectly honest there will always be a struggle when editing a shared 
 code base when using Leo and others are not using Leo. 

 Edward has addressed this many times at many levels. Leo is already pretty 
 smart with Python code for small edits.  I'm not certain there is a great 
 answer other than adding in even MORE intelligence into Leo's algorithms 
 which chop up the Python code into nodes. For example Leo could, but 
 doesn't, create a new node(s) when a new method class or function 
 definition is created. This seems odd given that Leo has the ability to 
 chop things up initially. Seems like it wouldn't be a huge stretch to 
 extend this behavior.

 On Friday, August 21, 2015 at 5:48:26 AM UTC-4, reinhard...@googlemail.com 
 wrote:

 How much more informative if instead it could become something like
 #*** Imports and magic
 import mypackage
 my_magic_number = 42
 #*** class definition
 class A(object):
#*** *** method 1
def method1(self):
pass
# description of aims of method
#*** *** method 2
def method2(self):
pass


 What do you gain by such redundant comments?

 Every Python programmer knows that 'class' is a class definition and 
 'def' (within a class) a method definition. The aims of a method should be 
 expressed by its name. And for additional commentary information is ample 
 room within the method itself.

 Reinhard
  



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

Does @clean go too far?

[Geoff Evans]

It seems to me that the file produced by an @clean node is not only clean 
but sterile.  I quite agree that many of the sentinel lines are nothing 
but a distraction for people; but not the ends of the node lines --
they are the headlines which you presumably chose to be meaningful,
and also the level of indentation in the outline.  For example the
following produced by @file

#@+leo-ver=5-thin
#@+node:gtevans.20150820072801.2: * @file classA.py
#@+others
#@+node:gtevans.20150820072837.1: ** Imports and magic
import mypackage
my_magic_number = 42
#@+node:gtevans.20150820072854.1: ** class definition
class A(object):
   #@+others
   #@+node:gtevans.20150820072948.1: *3* method 1
   def method1(self):
   pass
   #@+at
   # description of aims of method
   #@+node:gtevans.20150820073050.1: *3* method 2
   def method2(self):
   pass
   #@-others
#@-others
#@-leo

becomes, under @clean

import mypackage
my_magic_number = 42
class A(object):
   def method1(self):
   pass
   # description of aims of method
   def method2(self):
   pass

How much more informative if instead it could become something like

#*** Imports and magic
import mypackage
my_magic_number = 42
#*** class definition
class A(object):
   #*** *** method 1
   def method1(self):
   pass
   # description of aims of method
   #*** *** method 2
   def method2(self):
   pass


Would this be possible?  It would have the additional advantages of
making clear which method description of aims of method referred to,
and also resolve any ambiguity when the file is edited outside Leo with
new lines at a boundary between nodes.

Meanwhile, immense thanks (once more) for Leo and for the Leo commmunity.
It makes my professional life so much easier.

Cheers,   geoff evans

-- 
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: Another shock: Leo scripts are *dense* (aka elegant)

[Geoff Evans]

On Sunday, October 13, 2013 5:24:34 PM UTC-2:30, Edward K. Ream wrote:

 On Sun, Oct 13, 2013 at 10:17 AM, Edward K. Ream 
 edre...@gmail.comjavascript:
  wrote:

 Below is the first draft of an introductory example, supposedly to 
 start off the scripting chapter.

 This is *way* too much data!  Newbies will run away screaming. Somehow, 
 it must be greatly simplified.


 It seems that the twin challenges of technical writing are:

 - Knowing what *not* to say, or at least when not to say it.
 - Knowing the order of what *to* say.
  

 These seem more difficult, and thus more interesting(!), than many 
 programming puzzles.

 EKR

 
May I demur?   I read the example and its explanation with care, and for 
the first time I had a sense of what scripting is about: doing things with 
generators, positions and vnodes -- each of which is then briefly 
explained.  So for me at least it was the perfect level of introduction.  
The only thing I would change:  The execute-script command (for example 
from the Edit menu or type ctrl-B) 
 
Agreed:  just-in-time delivery of ideas is a skill, and one well worth 
acquiring.
 
geoff

-- 
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/groups/opt_out.

Re: Leo in a nutshell, including the Leo Aha

[Geoff Evans]

 Programmable: Leo scripts (Python scripts in Leo outlines) have *easy* 
 access to all Leo outlines, and *easy* access to all of Leo's own source 
 code. Conversely, Leo outlines naturally organize even the largest computer 
 programs.

 The *Leo Aha* is the moment when someone realizes how well Leo outlines 
 and Leo scripts work together.

 I'm writing as someone who uses Leo outlines daily (thank you so much for 
making this possible) and has never written a Leo script.  So what I 
personally need next is an intuition pump (thank you, Daniel Dennett).  
That is, follow the last quoted sentence by For example, suppose you want 
to ..., where the sentence is completed by some real task (in science for 
example) that a person with no interest whatever in writing editors might 
imagine wanting to perform.  Then a couple of sentences to sketch how an 
outline and a script would play nicely together to accomplish what I want, 
plus a pointer to the actual file that accomplishes it (which I would then 
study in detail once I got out of the elevator).

geoff

-- 
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/groups/opt_out.

Re: another way in to Leo?

[Geoff Evans]

Thanks Terry,
Maybe I'm beginning to get a sense of what it's about.  In two stages:

First, to get the same effect I might have opened a Python window, opened 
the data file, imported a module that had the appropriate function, and 
executed the function.  Scripting says in effect:  Why go to all that 
overhead?  If you're in Leo you're already running python, already have the 
data file open, and already have access to the code.  Just do it.

Second stage:  Yours is not a monolithic file; it has structure and in fact 
contains a description of its structure.  And Leo has vocabulary to 
understand this description and make use of it.  So, for example, I am 
currently working with data comprising different experimental treatments, 
different sampling times, and a couple of hundred samples from each.  At 
the moment the treatment and time are repeated in the file for each sample; 
they really belong just once in the headline of a node.  And then it's 
trivial (think clones) to create treatment/time subsets appropriate to 
different questions I want to ask of the data.

Possible drawbacks (though I haven't thought carefully enough to be sure):  
There's a large and somewhat cryptic vocabulary to be learned, and maybe to 
be relearned each time I want to use it.  And it seems to lack some of the 
safety features of Python, where functions can't have side effects outside 
their namespace unless I explicitly say they can.

So, reverting to the tutorial that some knowledgeable and generous person 
might feel moved to write, I now envisage an entry on structured data sets 
[easy to suppose you migght want such things] and a sub-entry on scripts to 
manipulate them.

Cheers,   geoff

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

another way in to Leo?

[Geoff Evans]

I should start by saying that I use Leo daily and wouldn't now
consider
starting any project lasting more than a week without it.  I'm
immensely
grateful to Edward and the community of collaborators for creating and
polishing it.  Two things prompt me nevertheless to write.  First, I
have
a strong feeling that there are ways I could be using it better, to
make
my life even easier, if only I could manage to break into them;
secondly,
Edward asks from time to time something like Why isn't everybody
using
Leo and what would it take to convert more people?  Maybe the
following
will be a contribution.

When I started programming in Python a couple of years ago, and
started
learning about object-oriented principles, one that struck me
especially
was Program to the interface, not the implementation.  (It often
takes
me a while to remember this when I'm working; but it always makes
things
better when I do.)  My Aha moment a couple of months ago came when I
realized that this wasn't true only of programming -- the same
principle
applies to writing as well.  Papers that jump right in to telling me
what
the author did don't work nearly as well as those that start with the
reader and what s/he might care about and how the author proposes to
help
with that.

[Isn't it interesting that the maxim I quoted above disobeys itself,
because it refers to the implemetation in a computer program whereas
the
real interface is the general act of communication and the primacy of
the
receiver over the transmitter.]

So I envisage a tutorial starting as follows (sketch only):

Suppose you have a project that entails using some data, doing some
computations, and writing up the results.  If you want to easily:

-- work on / store / contemplate the project as a unified whole
[Leo manages all relevant files in one outline]

-- see and work on one small part in its context
[Leo is an outliner]

-- copy thoughts, results from one context to another
[clones]

-- switch between interactive and batch processing
[iPython interface]

-- produce nice printed (literate?) documentation for those who don't
use
Leo or don't do all their work glued to a computer screen
[rst3? noweb? Fweb? maybe little sample batch files with all the
required
steps?]

-- ???
[scripting]
And here I'm stuck:  Leo documentation assures me that scripting is an
amazingly powerful answer, but doesn't tell me what questions I might
like to ask, or what needs I might have, that it is an answer to.  It
simply
tells me what to do if I already know why I want to.

-- Here is where the community may want to contribute ways Leo has
made
their working lives easier and more productive, by meeting existing
needs
or wishes that had nothing intrinsically to do with Leo.

I envisage this as complementing the existing tutorial in leodocs.  It
may provide an entrance that a different class of potential user would
find attractive.  Or maybe I just need someone to gently point me to
where what I am suggesting already exists ;-)

Cheers,   geoff evans

-- 
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: Don't be such a (computer) scientist

[Geoff Evans]

 I agree the engine room was a bad idea; in fact I was ready to
discard it even before reading Edward's reaction.  I've been thinking
since that it might help to split the second power tool into two:

=

2.  You have easy access to a powerful programming language.
3.  You can easily automate operations on your outline.

2:   Leo is written in Python: when you are editing a Leo
outline your are -- from a different perspective -- running
scripts in a Python session.  More than that, Leo makes it easy
for you to write your own Python script in a node of your outline,
and execute it when you want.  Or, by opening a Leo session and
and an IPython session, you can 

3:   The components and organization of your outline are Python
objects, and you can write Python scripts to see them and act on
them.  (Let us define a Leo script as a Python script that acts
on the Leo outline it is a component of.)  It is hard to grasp the
power of this at first; but suppose, for example, you have ...
and you want to ...

==

Reasons for the split:  There really are two ideas here and I found
it easy to get confused when documentation talked sometimes of Leo
scripts and sometimes of Python scripts.  The first idea has more
applications: if my own learning experience is typical, one will want
to start by using Leo to help do the work one really wants to do, and
only later worry about making it an even more powerful tool.

Another thought:  I know it's not Leo, but if someone could put into
quickstart.leo (is there a pointer to this file on Leo's home page?)
what I have to do to turn a restructured text file into LaTex, with
a trivial example, it would flatten my learning curve a lot.

geoff
--~--~-~--~~~---~--~~
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: problems running Leo

[Geoff Evans]

Okay, if I'm going to reinstall Ubuntu (maybe real rather than
Xubuntu) can
anyone suggest the least obtrusive window manager that doesn't
have the blackout problem?  openbox?

geoff

On Oct 1, 3:26 pm, Edward K. Ream edream...@gmail.com wrote:
 On Thu, Oct 1, 2009 at 5:48 AM, Geoff Evans gtevan...@nl.rogers.com wrote:

  Weird: this
  doesn't seem to strike a chord with any other user, but it
  has happened to me with three different versions.  Any ideas?
  Maybe some fossil I need to purge?

 It does seem that some part of your Linux install needs fixing.

 Edward
--~--~-~--~~~---~--~~
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: problems running Leo

[Geoff Evans]

 ctrl-I for creating a new node no longer works.
 In the Outline menu the shortcut is now given as Key-O;
 clicking on the Insert node option does nothing.
 (Actually, just once, it did insert a node; but I couldn't
 get the behaviour to repeat.)

 What am I doing wrong, please?

I just tried re-installing, using Ville's 4.7 Debian package:
same symptoms.  I haven't actually tried Key-O because
I don't know what keystrokes it represents.  Weird: this
doesn't seem to strike a chord with any other user, but it
has happened to me with three different versions.  Any ideas?
Maybe some fossil I need to purge?

Best,geoff
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

problems running Leo

[Geoff Evans]

I'm having two problems, one annoying, one fatal, when I
try to run recent versions of Leo.
I am running either:
Leo 4.6.2 final, build 2276, August 3, 2009
Python 2.6.2, qt version 263424
linux2
obtained from Ville's Debian package, or

Leo 4.7 devel, build 2277, August 28, 2009
Python 2.6.2, qt version 4.5.0
linux2
obtained from bzr, on

Xubuntu jaunty, blackbox

More often than not, when I click in the outline or log pane,
it turns mostly black and I need to right-click to revert
to the usual colours.

ctrl-I for creating a new node no longer works.
In the Outline menu the shortcut is now given as Key-O;
clicking on the Insert node option does nothing.
(Actually, just once, it did insert a node; but I couldn't
get the behaviour to repeat.)

What am I doing wrong, please?

Best,   geoff

--~--~-~--~~~---~--~~
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: problems running Leo

[Geoff Evans]

  More often than not, when I click in the outline or log pane,
  it turns mostly black and I need to right-click to revert
  to the usual colours.

 Some minimal window managers have this problem (apparently blackbox
 too - though the name does seem appropriate here ;-). I'd recommend a
 mainstream window manager for this reason (I abandoned my LXDE
 experiment because of this).

Okay, but on a different machine (Ubuntu hardy, blackbox) I never have
the problem.  Also it happened to me when I used xfce on the 'problem'
machine.

geoff
--~--~-~--~~~---~--~~
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: The next big thing: documentation

[Geoff Evans]

Great idea!  What can I, as a newbie and therefore target of your
efforts (and also a scientific editor in a former life) do to help?

I wonder if making a new group leo-editor-newbie or leo-editor-doc
would help.  I fully appreciate that leo-editor has first to serve the
cognoscenti who are building it [and heartfelt thanks to all of you!];
but it is an overwhelming list for someone not involved in that
effort.

Geoff Evans
--~--~-~--~~~---~--~~
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: help with reading documentation

[Geoff Evans]

Thanks Jesse,
 I want to edit LeoSettings.leo so that the window split direction
 starts out toggled the other way.  What is the specific option I
 need to change (assuming that's the way to do it)?

 I don't think this is possible as of yet.  I know it has been
 requested before.

I got something that worked for me: edit the file leoSettings.leo
(with vim rather than leo), and in the line that starts
initial_splitter_orientation  change the word vertical to
horizontal.

 The rectangles denoting nodes sometimes have extra decorations - a
 black rather than grey border, or one of an assortment of red marks.
 Is there a list of what they all mean?

It looks as though the black rather than grey border means the node
has
been changed since it was last saved.   Handy -- but so much more
handy if there were a place to find out that's what it means.
Probably
other markings, like the red vertical line to the left of the blue
square
in one of my nodes, are equally handy.

Feel free to improve the
 documentation if you have some free time.  Docs written from a
 newbie's perspective could be valuable to other newbies.

That had occurred to me -- but it looks as though it would need to be
a collaboration: as a newbie I might write the first part of a
sentence,
like A black (rather than grey) border for a node rectangle
means ...;
but someone else would have to complete the sentence.

geoff
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

help with reading documentation

[Geoff Evans]

This is a *neat* product, worth learning how to use well.  But I'm
having trouble navigating the documentation.  I'm looking for answers
to the following questions; but more importantly I'm looking to be
told where I should have looked to get the answers without pestering
you people :-)

The rectangles denoting nodes sometimes have extra decorations - a
black rather than grey border, or one of an assortment of red marks.
Is there a list of what they all mean?

Is there a way to colour bits of text the way I want to rather than
Leo's automated decisions?

I want to edit LeoSettings.leo so that the window split direction
starts out toggled the other way.  What is the specific option I
need to change (assuming that's the way to do it)?

Thanks,geoff evans

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