On 2020-12-03, Ludovic Courtès wrote:
> Mathieu Othacehe skribis:
>
>>> … but I don’t think we can assume that the checkout is in the
>>> ‘%load-path’ when this code is executed. WDYT, Mathieu?
>>
>> Cuirass happens to add checkouts to the %load-path just before loading
>> this file.
>
> Is that
Hi,
Mathieu Othacehe skribis:
>> … but I don’t think we can assume that the checkout is in the
>> ‘%load-path’ when this code is executed. WDYT, Mathieu?
>
> Cuirass happens to add checkouts to the %load-path just before loading
> this file.
Is that systematic? Isn’t it only when ‘load_path_i
Hey,
> … but I don’t think we can assume that the checkout is in the
> ‘%load-path’ when this code is executed. WDYT, Mathieu?
Cuirass happens to add checkouts to the %load-path just before loading
this file.
I tested your path, it works fine. I think it is acceptable as this (gnu
ci) interfa
Hi!
Vagrant Cascadian skribis:
> My *wild* guess is it maybe has something to do with the use of
> canonicalize-path:
>
> (define (find-current-checkout arguments)
> "Find the first checkout of ARGUMENTS that provided the current file.
> Return #f if no such checkout is found."
> (let ((cu
