Re: @shadow and what should I put under version control
I do a good bit of clones getting expanded into multiple locations, and it works well for me. Important things to remember: * If you're using @thin, it means the .leo file is thin, and the derived file is fat. * If you've got nodes cloned into multiple @thin or @file locations, and their contents gets changed outside of Leo, then the last version encountered during the reading of the derived files wins. * If the sentinels are damaged outside of Leo, Leo can sometimes get confused -- more often with @file than with @thin. * Unless your versioning system is extremely short of disk space, tell your versioning system that the .leo file is a binary. Trying to do reconciliations between XML files is close to impossible except in the very most trivial cases. I've only done it successfully twice; you're almost always better off abandoning your changes, checking out from a known coherent version, and redoing the work from there. Good luck, - Stephen On Jun 22, 8:32 pm, Lucas Thode wrote: > On Mon, Jun 22, 2009 at 1:01 PM, Edward K. Ream wrote: > > > > > > > <> > > >> The .leo file differs from simple project files of various IDEs in > >> that it can have valuable content that's not trivially derived from > >> anywhere else. You may want to have it in version control outside you > >> normal development tree, but it's still handy to have it somewhere. > > > True, but this is not recommended. I recommend the approach discussed at: > > >http://webpages.charter.net/edreamleo/FAQ.html#how-should-i-use-leo-w... > > > where most information is in @thin trees and the "reference" .leo file > > changes only when new @thin nodes are added. > > > Edward > > What do you do about nodes and structure that is shared among multiple @thin > trees in that scenario? Also, what about things that should be kept with > the code, but are not part of the code itself? (Leo's clones provide a nice > facility for associating code and high-level documentation such as business > requirements.) > > --Lucas --~--~-~--~~~---~--~~ 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: Leo 4.6 beta 2 released
Except that now I am getting structure comments appearing in my
tangled code even with the @silent directive before my @root directive
eg: I now see amongst my tangled code
# << Rebol Header >> (1 of 3)
I didn't see this with 4.5.1 final which is what I have been using.
On Wed, Jun 24, 2009 at 9:37 AM, Graham Chiu wrote:
> Thanks ... both Qt and tangling are now working.
>
> On Wed, Jun 24, 2009 at 1:06 AM, Edward K. Ream wrote:
>>
>>
>> On Mon, Jun 22, 2009 at 4:02 PM, Graham Chiu wrote:
>>>
>>> Oh yeah still won't tangle for me.
>>
>> Fixed on the trunk at rev 2083.
>>
>> My apologies for letting this bug go for so long. Somehow it slipped
>> through the cracks.
>>
>> The fix is apparent from the traceback:
>>
>>> File "C:\Leo-4-6-b2\leo\core\leoTangle.py", line 3393, in standardize_name
>>> name = name.lower().name.replace('\t',' ').replace(' ',' ')
>>
>> Change this line to:
>>
>> name = name.lower().replace('\t',' ').replace(' ',' ')
>
> --
> Graham Chiu
>
--
Graham Chiu
--~--~-~--~~~---~--~~
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: Leo on ubuntu karmic
On Tue, Jun 23, 2009 at 12:10 PM, Ville M. Vainio wrote: > > Since there has been various problems reported with this... > > Just upgraded my Ubuntu to Karmic (in order to proceed with packaging). > > I can confirm that leo *does* work with karmic, both qt and tk. Thanks for your packaging work. It is greatly appreciated. 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: New colorizer enabled again
On Tue, Jun 23, 2009 at 3:34 PM, Edward K. Ream wrote: > > There are substantial problems with languages like C that use delegate > colorizer. I've patched up the obvious problems with C, but I > wouldn't be at all surprised if there were other problems. There are some cute puzzles lurking in the delegate code. I'll write more tomorrow, probably. 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: Leo 4.6 beta 2 released
Thanks ... both Qt and tangling are now working.
On Wed, Jun 24, 2009 at 1:06 AM, Edward K. Ream wrote:
>
>
> On Mon, Jun 22, 2009 at 4:02 PM, Graham Chiu wrote:
>>
>> Oh yeah still won't tangle for me.
>
> Fixed on the trunk at rev 2083.
>
> My apologies for letting this bug go for so long. Somehow it slipped
> through the cracks.
>
> The fix is apparent from the traceback:
>
>> File "C:\Leo-4-6-b2\leo\core\leoTangle.py", line 3393, in standardize_name
>> name = name.lower().name.replace('\t',' ').replace(' ',' ')
>
> Change this line to:
>
> name = name.lower().replace('\t',' ').replace(' ',' ')
--
Graham Chiu
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
New colorizer enabled again
I have spent all day trying to get the new colorizer to work. It looks pretty good with Python. Please report any problems immediately. There are substantial problems with languages like C that use delegate colorizer. I've patched up the obvious problems with C, but I wouldn't be at all surprised if there were other problems. Anyway, I'm going to enable the new code on the trunk so more people can try it. If you have problems, you can always set newColoring=False. 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 -~--~~~~--~~--~--~---
Leo on ubuntu karmic
Since there has been various problems reported with this... Just upgraded my Ubuntu to Karmic (in order to proceed with packaging). I can confirm that leo *does* work with karmic, both qt and tk. AFAICT, anyway, by quick fiddling around & running the unit tests. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: Leo 4.6 beta 2 released
On Tue, Jun 23, 2009 at 4:06 PM, Edward K. Ream wrote: > You can do this by hand if using bzr is inconvenient for you. > > I improved the single unit test for @root so that it actually tests > tangling! Since @root & tangling is used relatively little (and hence is badly tested, it appears), I think it's time to ask "what are @root nodes good for", with the eye on showing some deprecation warnings suggesting users to switch to @thin/@nosent nodes instead. Of course the support for @root is still needed (because people have documents with @root), but it may be wise to advice against them early enough. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: Leo 4.6 beta 2 released
On Mon, Jun 22, 2009 at 4:02 PM, Graham Chiu wrote:
>
> Oh yeah still won't tangle for me.
Fixed on the trunk at rev 2083.
My apologies for letting this bug go for so long. Somehow it slipped
through the cracks.
The fix is apparent from the traceback:
File "C:\Leo-4-6-b2\leo\core\leoTangle.py", line 3393, in standardize_name
>name = name.lower().name.replace('\t',' ').replace(' ',' ')
Change this line to:
name = name.lower().replace('\t',' ').replace(' ',' ')
You can do this by hand if using bzr is inconvenient for you.
I improved the single unit test for @root so that it actually tests
tangling!
During testing, I noticed that tangling @root x.py from test.leo wrote x.py
to the leo directory, rather than the expected leo/test directory. This
seems like a fairly serious bug, but I haven't done anything about it yet.
If it is a bug, it's been around for a long time, and I want to make sure
that "fixing" it won't cause you further problems.
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: Leo 4.6 beta 2 released
On Mon, Jun 22, 2009 at 3:59 PM, Graham Chiu wrote: > > How do I get Qt to load? Oops. I forgot to tell how to install Qt in the installation notes. For Windows, install PyQt using the binary installer at http://www.riverbankcomputing.co.uk/software/pyqt/download 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 -~--~~~~--~~--~--~---
