On Fri, Aug 9, 2013 at 9:55 PM, Terry Brown terry_n_br...@yahoo.com wrote:
Well, yes and no. Your comments and those of someone else make it
clear that you're not looking for a rich text editor that can do this:
http://ckeditor.com/demo#full so much as one that gives bold / italics
etc.
Rev 5885 fixes the crash you mention in unregisterOneHandler.
File /home/ville/b/leo-editor/leo/core/leoPlugins.py, line 735, in
unregisterOneHandler
bunches = [bunch for bunch in bunches if bunch.fn != fn]
TypeError: 'NoneType' object is not iterable
The fix was just to add a guard:
On Saturday, August 10, 2013 8:09:51 AM UTC-5, Edward K. Ream wrote:
Where is this work now, and how would you like it described in the
release notes?
Oh. I see it's on the contrib branch. Anything more you would like to say
about it?
EKR
--
You received this message because you are
The first draft of the notes are in LeoDocs.leo, the nodes::
Leo 4.11 a1 Release notes--Gui improvements--Dark colorizing theme
and::
Leo 4.11 a1 Release notes--Gui improvements--Sublime Text 2 (A dark
colorizing theme)
which is just a link to
Hi Edward,
Just noticed that the docs at http://leoeditor.com/plugins.html are out
of date. Namely:
Viewrendered - now renders @md nodes as markdown. Also creates more
than just the `viewrendered` command.
printing.py (Qt only plugin) - offers printing commands. No docs up
there at all.
In Getting Things Done, David Allen recommends that we stop and ask we are
doing our projects. Here are two answers.
I do formal releases for two, no three reasons:
1. To force myself to document features.
2. To announce that the particular code base is to be trusted.
3. To test and correct
On Sat, 10 Aug 2013 07:14:43 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
In Getting Things Done, David Allen recommends that we stop and ask we are
doing our projects. Here are two answers.
I do formal releases for two, no three reasons:
1. To force myself to document features.
On Sat, Aug 10, 2013 at 9:31 AM, Terry Brown terry_n_br...@yahoo.comwrote:
Releases also tend to follow a round of bug squashing, which I suppose
is the same thing. I guess part of doing a release is clearing bugs
from the tracker.
Yes. However, 4.11 a-1 will focus on installation
On Sat, Aug 10, 2013 at 9:05 AM, gatesphere gatesph...@gmail.com wrote:
Hi Edward,
Just noticed that the docs at
http://leoeditor.com/plugins.**htmlhttp://leoeditor.com/plugins.htmlare out
of date.
Thanks for this. I'm working on docs for all recently-changed plugins as
we speak, but I
https://github.com/leo-editor/snippets/blob/master/rich_text_editor.py
paste the above (click the Raw button) into a node and run it (Ctrl-B).
Then you can Alt-X rich-text-open to switch to rich text mode (that
command could be bound to a key in @settings, there's also
rich-text-close).
Rich
On Sat, 10 Aug 2013 06:50:59 -0500
Edward K. Ream edream...@gmail.com wrote:
On Fri, Aug 9, 2013 at 9:55 PM, Terry Brown terry_n_br...@yahoo.com wrote:
Well, yes and no. Your comments and those of someone else make it
clear that you're not looking for a rich text editor that can do
On Sat, 10 Aug 2013 06:54:32 -0500
Edward K. Ream edream...@gmail.com wrote:
On Fri, Aug 9, 2013 at 10:01 PM, gatesphere gatesph...@gmail.com
wrote:
As for a book... the docs are large, and the code is pervasive.
I'm not sure a book could cover all the salient topics.
My advice is
On Sat, 10 Aug 2013 07:14:43 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
Documentation has several purposes:
1. Most importantly, to announce that a particular feature exists.
People have no way of trying feature otherwise.
2. To provide the *minimum* need for people to start
13 matches
Mail list logo
