> On 31. Aug 2022, at 13:21, Jan Rękorajski wrote:
>
> On Wed, Aug 31, 2022 at 11:41 AM Arkadiusz Miśkiewicz via pld-devel-en
> wrote:
>>
>> On 31.08.2022 11:27, Jan Rękorajski wrote:
>>> Where will it land now? If you want to protect against landing in
>>> non-existing directory you can use
On Wed, Aug 31, 2022 at 11:41 AM Arkadiusz Miśkiewicz via pld-devel-en
wrote:
>
> On 31.08.2022 11:27, Jan Rękorajski wrote:
> > Where will it land now? If you want to protect against landing in
> > non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"'
> > I really prefer to be
On 31.08.2022 11:27, Jan Rękorajski wrote:
Where will it land now? If you want to protect against landing in
non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"'
I really prefer to be staying in the same directory where I launched
the script in.
Do you include (via source/dot)
On 31.08.2022 11:27, Jan Rękorajski wrote:
> Where will it land now? If you want to protect against landing in
> non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"'
> I really prefer to be staying in the same directory where I launched
> the script in.
I considered doing `test -d`
Where will it land now? If you want to protect against landing in
non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"'
I really prefer to be staying in the same directory where I launched
the script in.
On Wed, Aug 31, 2022 at 12:59 AM atler wrote:
>
> commit
