> Thanks for this explanation. BTW, I just found this explanation of %~dp0
>
>
> http://stackoverflow.com/questions/5034076/what-does-dp0-mean-and-how-does-it-work
>
sorry for using an opaque syntax without comment! To round out the
reference links, SS64 is usually my first stop for all things Wi
On Wed, Oct 15, 2014 at 12:00 PM, Matt Wilkie wrote:
> In it's simplest possible (non-automated, bulky) form creating Windows
> portable Leo is:
[snip]
Thanks for this explanation. BTW, I just found this explanation of %~dp0
http://stackoverflow.com/questions/5034076/what-does-dp0-mean-and-how
On Wed, Oct 15, 2014 at 6:20 PM, Matt Wilkie wrote:
> My only complaint with portablepython is it's size, but that's not a
> stopper.
I've just started the process of making LeoPortable. The big question
is whether to put Portable Python 2.7.6.1 *inside* LeoPortable or not.
As someone has poin
On Thu, Oct 16, 2014 at 3:05 PM, bobS wrote:
> Thanks, Edward. The make-sphinx button now works for me as well.
Excellent. Thanks for the confirmation.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and s
Thanks, Edward. The make-sphinx button now works for me as well.
Regards,
bobS
On Tuesday, October 14, 2014 11:27:45 AM UTC-5, Edward K. Ream wrote:
>
> On Tue, Oct 7, 2014 at 1:57 PM, Edward K. Ream > wrote:
> > On Tue, Oct 7, 2014 at 1:01 PM, bobS >
> wrote:
>
> The make-sphinx button works
On Thu, Oct 16, 2014 at 1:05 PM, Matt Wilkie wrote:
> It seems to me the problem is that right now gnx have no local/global
> distinction, in effect making them all global.
Correct. All gnx's are based on a single, global, timestamp.
However, that's not really a problem, nor did it cause bug #
A comment from afar, from one who does not have a clear understanding of
the mechanics involved. Feel free to ignore, if this thought has no
bearing. ;-)
It sounds to me like the discussion is about "how can Leo have namespaces
for nodes, trees, and/or .leo files?", which makes me wonder if there'
On Thu, Oct 16, 2014 at 10:06 AM, Edward K. Ream wrote:
> Bob reports that the post scan does not fix the problem.
> Possible causes:
>
> - The post scan is buggy.
> - Caching bypasses the post scan.
> - (My guess) The hidden root vnode's gnx is the culprit.
> - (Gasp) Something else.
Rev 934f29
On Thu, Oct 16, 2014 at 10:35 AM, Kent Tenney wrote:
> I was wondering if Leo could use an arbitrary function provided by a plugin to
> generate the key. Arbitrary, other than the requirement for uniqueness.
Only core Leo developers should mess with gnx's. Break that code; break Leo.
Edward
-
Let a plugin override gnx form.
I don't know how deep the gnx machinery is,
I just see it as the key joining the t and v nodes.
Probably too naive, I was wondering if Leo could
use an arbitrary function provided by a plugin to
generate the key. Arbitrary, other than the requirement
for uniqueness
On Thu, 16 Oct 2014 10:14:53 -0500
Kent Tenney wrote:
> Could a plugin offer a get_gnx() function?
You mean plugin specific gnxs? Or let a plugin override gnx form?
Cheers -Terry
> On Thu, Oct 16, 2014 at 10:06 AM, Edward K. Ream
> wrote:
> > On Thu, Oct 16, 2014 at 8:19 AM, 'Terry Brown' vi
Could a plugin offer a get_gnx() function?
On Thu, Oct 16, 2014 at 10:06 AM, Edward K. Ream wrote:
> On Thu, Oct 16, 2014 at 8:19 AM, 'Terry Brown' via leo-editor
>
>> It's not clear to me that uuids are needed. #35 is a bug because Leo
>> is creating clashing gnxs *on load*, which it shouldn't.
On Thu, Oct 16, 2014 at 8:19 AM, 'Terry Brown' via leo-editor
> It's not clear to me that uuids are needed. #35 is a bug because Leo
> is creating clashing gnxs *on load*, which it shouldn't. Bob's
> always incrementing time stamp actually fixed the problem in hand, the
> case when things were d
On Thu, 16 Oct 2014 04:51:46 -0700 (PDT)
"Edward K. Ream" wrote:
> This is an Engineering Notebook post re
> https://github.com/leo-editor/leo-editor/issues/35
> leoBridge sometimes assigns the same gnx to two distinct vnodes
>
> I am going to start a new thread so as not to clutter the
> alre
This is an Engineering Notebook post re
https://github.com/leo-editor/leo-editor/issues/35
leoBridge sometimes assigns the same gnx to two distinct vnodes
I am going to start a new thread so as not to clutter the
already-way-to-long discussion in the bug thread.
First, let's all remind ourselve
15 matches
Mail list logo
