Hi,
Dariqq skribis:
>> The situation actually depends on the action you’re running.
>> Starting from 1a8d686b7fa617d9b1df33858957a240b7e11787, shepherd no
>> longer changes directory to the client’s directory. So now it’s up to
>> its action to interpret file names as it wants. We should updat
Hi Ludo,
On 05.02.25 11:21, Ludovic Courtès wrote:
Hi Dariqq,
Dariqq skribis:
Was reading through the shepherd manual and it seems to contain
contradictory information regarding relative file names:
In Chapter 3 ('herd' and 'shepherd') the manual reads
Since herd passes its current workin
Hi Dariqq,
Dariqq skribis:
> Was reading through the shepherd manual and it seems to contain
> contradictory information regarding relative file names:
>
> In Chapter 3 ('herd' and 'shepherd') the manual reads
>
>> Since herd passes its current working directory to ‘shepherd’, you can pass
>> r
Hello,
Was reading through the shepherd manual and it seems to contain
contradictory information regarding relative file names:
In Chapter 3 ('herd' and 'shepherd') the manual reads
Since herd passes its current working directory to ‘shepherd’, you can pass
relative file names without troub
