Mis-using clones?

After reading several posts by Edward about clones and refresh-from-disk command dangers, I've come to the conclusion that I may be using clones incorrectly, or at least having unrealistic expectations for them. One of the features of Leo that attracted me in the first place was the ability to

Re: How to usage Leo as team?[was] Leo in the wild

2013/10/23 Edward K. Ream : > On Wed, Oct 23, 2013 at 8:36 AM, Edward K. Ream wrote: ... > I really am getting exasperated, but perhaps there is some value to be had > in my frustration. > > I wonder, how hard would it be to create an Emacs leo-python mode (major?, > minor?) > > that would hide (o

Re: The docs are ready for b1. Please review

On Wed, 23 Oct 2013 18:07:11 -0500 "Edward K. Ream" wrote: > On Wed, Oct 23, 2013 at 6:01 PM, Edward K. Ream wrote: > > The title is not quite accurate. Still to do: a step-by-step for rst3 > command, and probably one or two others. Not sure on the relationship between rst3 command and @auto-

Re: The docs are ready for b1. Please review

On Wed, Oct 23, 2013 at 6:01 PM, Edward K. Ream wrote: The title is not quite accurate. Still to do: a step-by-step for rst3 command, and probably one or two others. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

The docs are ready for b1. Please review

Today's work did the following: - Added quotes to the home page, all tutorial pages, the preface, and the main Users Guide page. Imo, these quotes are great marketing. Much easier to read and much zippier than my previous blah-blah-blah :-) The introductory quotes give the pages much better l

Re: Traceback with revision 6176

Hello Edward, I do not know if it is relevant in this case, but my intention was to create the newest Leo documentation locally, and I had been successful previously ... With kind regards, Viktor -- You received this message because you are subscribed to the Google Groups "leo-editor" group

Traceback with revision 6176

Hello Edward, After having upgraded to the latest revision of Leo I receive the following traceback when I try to open the outline 'LeoDoc.leo' 2013-10-23 ~ 21:20 * Update local snapshot of Leo * OK. - See 'Log-001' - Snapshot is now on revision 6176 * Restart Leo - OK. - See 'Log-00

Coming soon: work flow patterns

There is a real chance now that newbies will be able to get the Leo Aha much more quickly than before. And the Aha that clones are *first* about work flow, and only *second* about view has made a big difference. The new hello world step-by-step is a revolution in my thinking. I'm going to cont

Re: Check out the introductory quotes.

On Wed, Oct 23, 2013 at 1:12 PM, Jacob Peck wrote: > http://leoeditor.com/tutorial-basics.html is missing a closing quote. Fixed. > Other than that, I think you picked nice quotes. Thanks. It was fun to add real juice to the docs. EKR -- You received this message because you are subscrib

Re: Check out the introductory quotes.

On Wed, Oct 23, 2013 at 1:00 PM, Edward K. Ream wrote: > They are on Leo's home page, and on each of the tutorial pages. > And now, also on http://leoeditor.com/usersguide.html. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubsc

Re: Check out the introductory quotes.

On 10/23/2013 2:00 PM, Edward K. Ream wrote: They are on Leo's home page, and on each of the tutorial pages. I think they are great, and you'll have a hard time convincing me otherwise. Not only do they convey people's authentic enthusiasm for Leo, they introduce Leo's important features in a

Re: oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

I put the bug report in, but I'm not sure what "smallest files (public and private)" means (sorry!). File? Does that mean a full leo file or just the node? To recreate the problem, all I need is an @shadow node with é or à etc... Pretty simple! Public and private? I'm assuming that "public an

Check out the introductory quotes.

They are on Leo's home page, and on each of the tutorial pages. I think they are great, and you'll have a hard time convincing me otherwise. Not only do they convey people's authentic enthusiasm for Leo, they introduce Leo's important features in a smooth way. I've also followed Seth's advice

Re: oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

On Wednesday, October 23, 2013 12:43:08 PM UTC-5, wgw wrote: > > Thanks! > > I was working in a2, I believe. not a3. So "previous" means way back when. > > You know your code! The problem is only in the @shadow nodes. I will file > a bug report. > Thanks. If possible, please submit the smal

Re: oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

Thanks! I was working in a2, I believe. not a3. So "previous" means way back when. You know your code! The problem is only in the @shadow nodes. I will file a bug report. I also noticed a slightly odd file: stand_along_globals.leo. Should that be stand_alone_globals.leo ? Thanks for the

Re: Proposal: c.create_node_hierarchy and p.create_node_hierarchy

On 10/23/2013 12:07 PM, Edward K. Ream wrote: On Wed, Oct 23, 2013 at 10:50 AM, Jacob Peck > wrote: On 10/23/2013 11:03 AM, Jacob Peck wrote: When I have time I'll give it a go. -->Jake Well... that was way easier than expected. The fo

Re: @shadow path names

On Wed, 23 Oct 2013 11:04:26 -0500 "Edward K. Ream" wrote: > On Wed, Oct 23, 2013 at 10:54 AM, Terry Brown wrote: > > > Current defaults > > > > @string shadow_prefix = x > > @string shadow_subdir = .leo_shadow > > > > > so editing README.TXT with @shadow will put .leo_shadow/xREADME.TXT > > *i

Re: Proposal: c.create_node_hierarchy and p.create_node_hierarchy

On Wed, Oct 23, 2013 at 10:50 AM, Jacob Peck wrote: > On 10/23/2013 11:03 AM, Jacob Peck wrote: > >> When I have time I'll give it a go. >> >> -->Jake >> > Well... that was way easier than expected. > > The following is the new version of the code, and it works so far... > Edward, do you see any

Re: @shadow path names

On Wed, Oct 23, 2013 at 10:54 AM, Terry Brown wrote: > Current defaults > > @string shadow_prefix = x > @string shadow_subdir = .leo_shadow > > so editing README.TXT with @shadow will put .leo_shadow/xREADME.TXT > *in the same folder* as README.TXT. Don't want it there, if @shadow is > the key t

@shadow path names

Current defaults @string shadow_prefix = x @string shadow_subdir = .leo_shadow so editing README.TXT with @shadow will put .leo_shadow/xREADME.TXT *in the same folder* as README.TXT. Don't want it there, if @shadow is the key to collaboration, I don't want to make weird .folders in the shared s

Re: Proposal: c.create_node_hierarchy and p.create_node_hierarchy

On 10/23/2013 11:03 AM, Jacob Peck wrote: When I have time I'll give it a go. -->Jake Well... that was way easier than expected. The following is the new version of the code, and it works so far... Edward, do you see any issues with the undoer code? = @language python def create_node_

Re: Proposal: c.create_node_hierarchy and p.create_node_hierarchy

On 10/23/2013 10:58 AM, Edward K. Ream wrote: On Wed, Oct 23, 2013 at 8:54 AM, Jacob Peck > wrote: > So, I wrote a function that will create a hierarchy of nodes with a list of given headlines. Interesting. > With the proper undo code added, I think that it would

Re: Proposal: c.create_node_hierarchy and p.create_node_hierarchy

On Wed, Oct 23, 2013 at 8:54 AM, Jacob Peck wrote: > So, I wrote a function that will create a hierarchy of nodes with a list of given headlines. Interesting. > With the proper undo code added, I think that it would be right at home as c.create_node_hierarchy ... I agree. > I would find t

Re: Writers workshop: describing Leo

Thanks Edward, Im looking forward to the cool things Leo cando tutos, and excited about the impact it will have on Leo's popularity =) On Wednesday, October 23, 2013 4:45:45 PM UTC+2, Edward K. Ream wrote: > > On Tue, Oct 22, 2013 at 2:37 PM, Fidel N > > wrote:I still think the best way to do is

Re: Writers workshop: describing Leo

On Tue, Oct 22, 2013 at 2:37 PM, Fidel N wrote:I still think the best way to do is to put examples. I was not able to realize how to -clearly- say this until I read a recent post talking about how tutos are right now regarding the hello world, and how they should be. > > That made me realize that

Re: Approaching Leo

On Wed, Oct 23, 2013 at 7:25 AM, Edward K. Ream wrote: On Mon, Oct 21, 2013 at 8:55 PM, gatesphere wrote: > > >> Here's another step-by-step: >> >> [big snip] >> > > Excellent. I'll revise > http://leoeditor.com/tutorial-programming.html#creating-source-code-with-others > along the lines you

Re: How to usage Leo as team?[was] Leo in the wild

On Wed, Oct 23, 2013 at 8:36 AM, Edward K. Ream wrote: > if you, as a team member, can't convince management and other team members > that sentinels are worthwhile, then there are, imo, *no* reasonable > alternatives to @auto or @shadow. > > It's really that simple. > I really am getting exas

Proposal: c.create_node_hierarchy and p.create_node_hierarchy

So, I wrote a function that will create a hierarchy of nodes with a list of given headlines. Here's the code, along with a test script: = @language python def create_node_hierarchy(heads, parent=None, forcecreate=False): ''' create the proper hierarchy of nodes with headlines defined in

Re: How to usage Leo as team?[was] Leo in the wild

On Wed, Oct 23, 2013 at 8:03 AM, Zoom.Quiet wrote: > > - H?! > - in hg/git can delpoy different hook in local for matter ... > - and even in server, hook script can base user acount do different ... > If you have a scheme that works for sharing private @shadow files, that's great. Don't let

Re: How to usage Leo as team?[was] Leo in the wild

On Wed, Oct 23, 2013 at 8:01 AM, Kent Tenney wrote: > I think that attitude would be very counter-productive in selling Leo. > ... > > > How hard would it be, really, for non-users of Leo > > not to destroy your *valuable* sentinel comments? > > I'd have big problems with a team member who d

Re: How to usage Leo as team?[was] Leo in the wild

2013/10/23 Edward K. Ream : > On Wed, Oct 23, 2013 at 7:04 AM, Edward K. Ream wrote: > >> Fundamentally, this is a management problem, not a technical problem. >> Imo, it is a matter of others respecting your tools. > > > I let my annoyance show in this reply, but sometimes annoyance is helpful. >

Re: How to usage Leo as team?[was] Leo in the wild

2013/10/23 Edward K. Ream : > On Wed, Oct 23, 2013 at 7:04 AM, Edward K. Ream wrote: > >> >> Correct. The shadow files, starting with x_, are *private* files. The >> whole point is that they can *not* to be shared. They are your own personal >> view of the data in the public files. > > ... > >>

Re: How to usage Leo as team?[was] Leo in the wild

On Wed, Oct 23, 2013 at 7:04 AM, Edward K. Ream wrote: > On Wed, Oct 23, 2013 at 5:24 AM, Zoom.Quiet wrote: > >> >> @edit is new command for me, but in try: >> - "@edit nodes must not have children" >> - Huuu this is realy not fun. > > > Correct. Not fun at all. > > >> so flowing this kind of nat

Re: How to usage Leo as team?[was] Leo in the wild

2013/10/23 Jacob Peck : > On 10/23/2013 8:47 AM, Zoom.Quiet wrote: >> btw: >> the SCCS means? >> i only search out in FAQ: >> ... most problems with using Leo in cooperative (SCCS) environments >> >> guess is: >> Source Code Cooperative Situation >> ? > > Source Code Control System. Popular cho

Re: How to usage Leo as team?[was] Leo in the wild

On 10/23/2013 8:47 AM, Zoom.Quiet wrote: > btw: > the SCCS means? > i only search out in FAQ: > ... most problems with using Leo in cooperative (SCCS) environments > > guess is: > Source Code Cooperative Situation > ? Source Code Control System. Popular choices include git, svn, bzr, cvs, merc

Re: How to usage Leo as team?[was] Leo in the wild

2013/10/23 Edward K. Ream : > On Wed, Oct 23, 2013 at 5:24 AM, Zoom.Quiet wrote: ... >> 5. there is no way to merge others fix into own organizer nodes?! > > > Correct. The shadow files, starting with x_, are *private* files. The > whole point is that they can *not* to be shared. They are your

Re: How to usage Leo as team?[was] Leo in the wild

On Wed, Oct 23, 2013 at 7:04 AM, Edward K. Ream wrote: > Correct. The shadow files, starting with x_, are *private* files. The > whole point is that they can *not* to be shared. They are your own > personal view of the data in the public files. > ... > If your team members are indeed anti-

Re: How to usage Leo as team?[was] Leo in the wild

On Wed, Oct 23, 2013 at 7:04 AM, Edward K. Ream wrote: Fundamentally, this is a management problem, not a technical problem. Imo, > it is a matter of others respecting your tools. > I let my annoyance show in this reply, but sometimes annoyance is helpful. Leonistas must stand up for their too

Re: Approaching Leo

On 10/23/2013 8:25 AM, Edward K. Ream wrote: On Mon, Oct 21, 2013 at 8:55 PM, gatesphere > wrote: So next I figured, hmmm, let's try getting the thing to make some Python files. Well, I got as far as putting @others into a headline, and just stone gave up

Re: Approaching Leo

On Mon, Oct 21, 2013 at 8:55 PM, gatesphere wrote: > So next I figured, hmmm, let's try getting the thing to make some > Python files. Well, I got as far as putting @others into a headline, > and just stone gave up. It was impenetrable as currently documented. > > Keep pushing! Here's another

Re: Approaching Leo

On Mon, Oct 21, 2013 at 7:00 PM, Steve Litt wrote: Take a look at this: > http://leoeditor.com/tutorial-scripting.html#hello-world > Take a look at it now :-) The changes you suggested are crucial. Not only do they make clear what is going on in the hello-world example, they set the stage for e

Re: How to usage Leo as team?[was] Leo in the wild

On Wed, Oct 23, 2013 at 5:24 AM, Zoom.Quiet wrote: > @edit is new command for me, but in try: > - "@edit nodes must not have children" > - Huuu this is realy not fun. > Correct. Not fun at all. so flowing this kind of nature team cooperate process, > there is one core problems: > in s > tep >

Re: oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

On Wed, Oct 23, 2013 at 12:03 AM, wgw wrote: > 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 ha

Re: How to usage Leo as team?[was] Leo in the wild

2013/10/23 Edward K. Ream : > 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 co