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
On Mon, Jul 29, 2019 at 9:04 AM Terry Brown wrote:
rabbitMQ - high performance cross language / cross machine (cloud) message
queue system..it seems like the missing link in easy decoupling /
connecting of software.
Thanks for this. I've bookmarked https://www.rabbitmq.com/
Edward
--
You
On Mon, Jul 29, 2019 at 9:33 AM vitalije wrote:
> I didn't want to say that this command should be used rarely. I was just
pointing out that unless you have changed the code in a node, there is no
point in executing this command.
The node selection logic already compares the old and new
On Mon, Jul 29, 2019 at 8:06 AM vitalije wrote:
That would be rather invasive and most of the time unnecessary spending CPU
> time. Selecting nodes is already too complicated and not very fast (to say
> the least). Please don't add any more burden to it.
>
Blackening nodes automatically would
On Monday, July 29, 2019 at 4:04:57 PM UTC+2, Terry Brown wrote:
>
> I disagree with Vitalije's assessment of how often you'd execute it,
>
I didn't want to say that this command should be used rarely. I was just
pointing out that unless you have changed the code in a node, there is no
point
Now that I think about it I started using Black before I stopped using
Leo. I disagree with Vitalije's assessment of how often you'd execute it,
I found I quite often wanted a node tidied up. But I would agree with
Vitalije on taking a minimalist light weight approach to using Black in
Leo. I
On Monday, July 29, 2019 at 2:44:10 PM UTC+2, Edward K. Ream wrote:
>
> So it looks like Leo could optionally run blacken-node whenever selecting
> and/or unselecting a node for which @language python is in effect.
>
>
That would be rather invasive and most of the time unnecessary spending CPU
On Sunday, July 28, 2019 at 4:03:37 PM UTC-5, Edward K. Ream wrote:
> black looks considerably slower than Leo's beautify commands.
On second thought, it looks like Leo *can* use black with very little extra
work.
*Black looks fast enough*
The blacken-node command (in the "black" branch)
On Sunday, July 28, 2019 at 4:03:37 PM UTC-5, Edward K. Ream wrote:
[improving] Leo's existing beautify commands so they follow black's
> line-breaking strategy [should] be relatively straightforward. This would
> be a major departure for Leo's beautify commands.
>
A quick prototype of Leo's
On Sun, Jul 28, 2019 at 5:15 PM Terry Brown wrote:
> I've been using black for quite a while. I agree it's probably not
> fast enough to continuously reformat a file as you type, but that would
> probably be annoying.
Thanks for these comments. The prototype code in the "black" branch could
13 matches
Mail list logo
