Hi,
On 30/07/19 10:26 a. m., Matt Wilkie wrote:
>
> It has been a very long time since I've got this idea of combining
> Leo with fossil. For all these years I felt that there was a great
> potential in this mixture, but I haven't got the time to do
> anything about it until
Hi Vialije,
Genius!
IH
On Wednesday, 31 July 2019 13:50:50 UTC+1, vitalije wrote:
>
>
>> I envisioned this and in addition "saving" as simply tagging one of these
>> revisions.
>>
>> I am thinking about having Leo send some tag along with the snapshot. For
> example somewhere in Leo UI or in
>
>
> I envisioned this and in addition "saving" as simply tagging one of these
> revisions.
>
> I am thinking about having Leo send some tag along with the snapshot. For
example somewhere in Leo UI or in one special node user is asked to write
short description of what task is he/she doing
I think many of us have had a similar vision for development and
development environments. I have long dreamed of this kind of omnipresent
"history" integrated into every aspect of computing, but it never seemed to
show up. Now you've demonstrated the power it holds.
I envisioned this and in
Much better. Thanks.
A plugin would still be good. :-)
Chris
On Tue, Jul 30, 2019 at 1:56 PM vitalije wrote:
>
>
> On Tuesday, July 30, 2019 at 10:24:32 PM UTC+2, Chris George wrote:
>>
>> I tried to open the Leo file and it crashed the tree widget. Clicking on
>> the tree kills Leo.:
>>
>
>
On Tuesday, July 30, 2019 at 10:24:32 PM UTC+2, Chris George wrote:
>
> I tried to open the Leo file and it crashed the tree widget. Clicking on
> the tree kills Leo.:
>
Can you be more specific about what steps did you take to get this error. I
can open fossil-delta-ref.leo and click in the
I tried to open the Leo file and it crashed the tree widget. Clicking on
the tree kills Leo.:
bad .leo file: fossil-delta-ref.leo
g.toUnicode: unexpected argument: ParseError('not well-formed (invalid
token): line 44, column 86')
Traceback (most recent call last):
File
Hah - convergent evolution, I've been looking at Jupyter lab. in that kind
of context recently too.
The rest of this is off-topic, but I encourage people to play with the
Jupyter *lab* (not notebook) UI for Leo ideas.
It's basically multiple notebooks in multiple kernels plus consoles and
regular
>
> It has been a very long time since I've got this idea of combining Leo
> with fossil. For all these years I felt that there was a great potential in
> this mixture, but I haven't got the time to do anything about it until
> recently.
>
I've long been enamored with Fossil, though I've
Indeed.
I haven't used Leo in a while, been playing with docker containers
which configure and serve Jupyter lab on non-gui machines.
This time machine kind of capability is the kind of thing to lure
me back to Leo.
Terry, I remember you mentioning that you're using Docker, do
you have Leo
On Mon, Jul 29, 2019 at 2:11 PM vitalije wrote:
It has been a very long time since I've got this idea of combining Leo with
> fossil. For all these years I felt that there was a great potential in this
> mixture, but I haven't got the time to do anything about it until recently.
>
Many thanks
On Monday, July 29, 2019 at 9:31:49 PM UTC+2, Terry Brown wrote:
>
> That is very cool. I hope Kent sees it, he's talked about such things
> more than once.
>
Yes I just tried to find the exact date when this idea appeared on this
list. I haven't found my message that I am rather sure I had
That is very cool. I hope Kent sees it, he's talked about such things more
than once.
Cheers -Terry
On Mon, Jul 29, 2019 at 2:11 PM vitalije wrote:
> It has been a very long time since I've got this idea of combining Leo
> with fossil. For all these years I felt that there was a great
It has been a very long time since I've got this idea of combining Leo with
fossil. For all these years I felt that there was a great potential in this
mixture, but I haven't got the time to do anything about it until recently.
Fossil uses an extremely good algorithm to calculate the
14 matches
Mail list logo
