On Mon, Oct 21, 2013 at 7:00 PM, Steve Litt wrote:
> Hi all,
>
> I think this has some bearing on the recent discussion about increasing
>
> Leo's mindshare.
>
> Today I successfully completed Gatesphere's Leo "Hello World", and you
>
> know what I discovered? Leo, as it's documented currently
As indicated in another thread, we Leonistas have for years tried (and
failed!) to describe just why we are so excited about Leo.
It's vital that we be able to do so in a few words. In this "workshop"
I'll allow myself to start with a more "relaxed" exploration. In later
posts here I'll attem
On Monday, October 21, 2013 10:32:40 AM UTC-5, stevelitt wrote:
>
> On Mon, 21 Oct 2013 07:17:09 -0700 (PDT)
> "Edward K. Ream" > wrote:
>
> The first words of the announcement [might] even say why Leo trumps Emacs
> org mode and
> > vimoutline mode...
>
> I'd be careful about making such as
On Mon, 21 Oct 2013 20:26:53 -0700 (PDT)
David McNab wrote:
> Hi,
>
> I'm wanting to use Leo for writing university essays, reports, case studies
> etc. But to make this practical, when editing works of thousands of words,
> I really need to increase the line spacing to support easier reading
On Tuesday, October 22, 2013 3:23:59 AM UTC-5, Edward K. Ream wrote:
> I am starting to get inklings about what we all have missed for so long:
Leo's core benefits. The fundamental Aha: we *must not* confuse benefits
with features!!
In the "This, and *only* this" thread I have just stated why
There's an ugly hack at the end of this thread:
http://www.qtforum.org/article/32901/double-spacing-changing-line-height-in-qtextedit.html
I doubt that would work well in Leo, but it could be attached to a
'select' event on @doublespaced nodes?
-->Jake
On 10/22/2013 9:12 AM, Terry Brown wrot
On Tue, Oct 22, 2013 at 8:12 AM, Terry Brown wrote:
I'm not sure that Qt supports line-height. I see no mention of it here:
>
> http://qt-project.org/doc/qt-4.8/stylesheet-reference.html#list-of-properties
>
Thanks, Terry, for this and the rest of your response.
There *might* be a workaround us
On 10/22/2013 9:15 AM, Edward K. Ream wrote:
- Perhaps the best (only?) way to convey how *much* easier Leo makes
life for programmers and non-programmers is to sprinkle testimonials
throughout Leo's tutorial. I'm seriously considering it.
I agree on this point, but one must tread a careful lin
On Tue, Oct 22, 2013 at 8:28 AM, Jacob Peck wrote:
On 10/22/2013 9:15 AM, Edward K. Ream wrote:
>
>> - Perhaps the best (only?) way to convey how *much* easier Leo makes life
>> for programmers and non-programmers is to sprinkle testimonials throughout
>> Leo's tutorial. I'm seriously considerin
On Tuesday, October 22, 2013 8:29:25 AM UTC-5, Edward K. Ream wrote:
> Leo's documentation uses the following docutils(?) markup that
effectively inserts a element:
>
> .. |br| raw:: html
>
>
>
Oops. I misspoke. This does *not* insert a . It defines |br| so you
can use |br| later to i
2013/10/22 Zoom.Quiet :
> 2013/10/22 Edward K. Ream :
...
>>> 2. Leo can not usage as Team!
>>> - whatever @file/@shadow
>>> - after through DVCS(hg/git/bzr etc.)
>>> - Leo can not perfect merged others fixed into myself Leo node tree !
>>
>> I assume you meant that there are problems u
On 10/22/2013 9:35 AM, Zoom.Quiet wrote:
> 2013/10/22 Zoom.Quiet :
>> 2013/10/22 Edward K. Ream :
> ...
2. Leo can not usage as Team!
- whatever @file/@shadow
- after through DVCS(hg/git/bzr etc.)
- Leo can not perfect merged others fixed into myself Leo node tree !
>
> - Perhaps the best (only?) way to convey how *much* easier Leo makes life
> for programmers and non-programmers is to sprinkle testimonials throughout
> Leo's tutorial. I'm seriously considering it.
I still think the best way to do is to put examples. I was not able to
realize how to -cl
On Tue, Oct 22, 2013 at 8:35 AM, Zoom.Quiet wrote:
How to support Leo user can work with own organizer nodes in Team?
>
The Leo community must acknowledge that problems do exist. Having said
that, the problems aren't as big as some people say.
>
> of course, the problem had difference backgro
On Mon, 21 Oct 2013 21:55:26 -0400
gatesphere wrote:
> Keep pushing! Here's another step-by-step:
>
> 1) Create a node, headline named "@file myfile.py" (henceforth "node
> A") 2) In the body of that node, put the following:
> @language python
> << docstring >>
> @others
> if __name__ == '__ma
On 10/22/2013 7:38 PM, Steve Litt wrote:
On Mon, 21 Oct 2013 21:55:26 -0400
gatesphere wrote:
Keep pushing! Here's another step-by-step:
1) Create a node, headline named "@file myfile.py" (henceforth "node
A") 2) In the body of that node, put the following:
@language python
<< docstring >>
In the previous version, I had no problem writing unicode files (I'm in
ubuntu 12.04, utf-8 everywhere). I did a bzr pull for the latest version of
leo and now I'm getting :
UnicodeEncodeError: 'ascii' codec can't encode character
I must have overwritten something but not sure what: everything
17 matches
Mail list logo
