On Fri, Dec 1, 2017 at 5:05 PM, lewis wrote:
> Leo's documentation at http://leoeditor.com/installing.html now has an
> obsolete link at
> Installing Leo > Installing packages
> Download PyQt5 from http://www.riverbankcomputing.com/
> software/pyqt/download5.
>
> It seems the PyQt webpage has b
Leo's documentation at http://leoeditor.com/installing.html now has an
obsolete link at
Installing Leo > Installing packages
Download PyQt5 from
http://www.riverbankcomputing.com/software/pyqt/download5.
It seems the PyQt webpage has been recently updated. The link for PyQt5 via
the Riverbank
thank you Lewis, that would be much appreciated. :) I continually struggle
with how to balance level of detail between anemic and overwhelming.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving ema
I'll try and squeeze some time from the weekend and slap on my user's
hat
Lewis
On Friday, December 1, 2017 at 9:54:54 PM UTC+11, Edward K. Ream wrote:
>
>
> Instead, the remarks should be folded into the node:
>
> @rst html/installing.html-->Installing packages
>
> This is not a trivial
On Thursday, November 30, 2017 at 10:59:27 PM UTC-6, Matt Wilkie wrote:
ok, in future I'll do that. For this time see .../leo/doc/LeoDocs.leo#Leo's
> Documentation-->Installing & running Leo-->@rst html/quick.html
>
Imo, putting instructions in a separate section would slow users down.
Worse, i
On Friday, December 1, 2017 at 3:36:02 AM UTC-6, Edward K. Ream wrote
There are three nodes in the "quick" tree. Imo, all three nodes must have
> some introductory words succinctly explaining what is being discussed. This
> is not easy to do. Lewis, do you have any suggestions?
>
Also, the t
On Thu, Nov 30, 2017 at 10:59 PM, Matt Wilkie wrote:
>
> Where are the new docs? In future, it would be easiest to put clone new
>> nodes as the last top-level nodes of LeoDocs.leo That way devs and
>> interested users can see at a glance what has changed.
>>
>
> ok, in future I'll do that. Fo
> Where are the new docs? In future, it would be easiest to put clone new
> nodes as the last top-level nodes of LeoDocs.leo That way devs and
> interested users can see at a glance what has changed.
>
ok, in future I'll do that. For this time see .../leo/doc/LeoDocs.leo#Leo's
Documentation-->I
On Wed, Nov 29, 2017 at 6:09 PM, Matt Wilkie wrote:
> Eeep! sorry about that!
>
No problem. As long a nobody uses --force we can easily recover from
mistakes ;-)
> I fixed the botched LeoDocs.leo edit, and have now uploaded a package to
> https://pypi.python.org/pypi/leo :)
>
> `pip install
Eeep! sorry about that!
I fixed the botched LeoDocs.leo edit, and have now uploaded a package to
https://pypi.python.org/pypi/leo :)
`pip install leo` for end users and `pip install leo[develop]` for the
extras like pylint should work for most people now.
WRT to the docs, I'm not sure if I used
On Tuesday, November 28, 2017 at 5:00:26 PM UTC-6, Matt Wilkie wrote:
>
>
> https://github.com/leo-editor/leo-editor/commit/3b6b820c105df6f7c53cadedcec776c0974542d9
>
> Note: they don't work yet because there is no package on pypi.org! I got
> to fighting with git conflicts and have run out of t
https://github.com/leo-editor/leo-editor/commit/3b6b820c105df6f7c53cadedcec776c0974542d9
Note: they don't work yet because there is no package on pypi.org! I got to
fighting with git conflicts and have run out of time. More later. Sorry
Matt
--
You received this message because you are subscrib
12 matches
Mail list logo
