On 2020-06-20 at 14:02 -0400, Chet Ramey wrote:
> It's a way to make sure PWD is correct after a `cd'. Without options, `cd'
> canonicalizes its pathname argument in the way POSIX describes in
>
> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/cd.html#tag_20_14
>
> That converts it
On 6/19/20 7:53 PM, Bryan Henderson wrote:
> I tracked it down to an Ncurses change.
>
> Bash/readline attempts to move the cursor left by calling Ncurses (libtinfo)
> function 'tputs' with ASCII BS (ctl-H) as the argument. The function of
> 'tputs' is to write stuff to the terminal with delays
On 6/20/20 1:28 PM, Lawrence Velázquez wrote:
> Here's something fun though:
>
> $ PROMPT_COMMAND='cd .'
> $ readlink /tmp
> private/tmp
> $ mkdir /tmp/old
> $ cd /tmp/old
> $ echo "$PWD"
> /tmp/old
> $ mv /tmp/old /tmp/new
> $ echo "$PWD"
> /private/tmp/new
>
> Not wrong, but maybe unexpected
On 6/19/20 8:51 PM, corr...@goncalo.pt wrote:
>
> When we rename the current working directory, $PWD doesn't get updated
> as it would as it would if we just did a simple "cd directory".
Of course not. There is no mechanism to inform the shell that the file
system has changed from underneath it.
> On Jun 20, 2020, at 11:26 AM, Ilkka Virta wrote:
>
>> On 20.6. 3.51, corr...@goncalo.pt wrote:
>>
>> When we rename the current working directory, $PWD doesn't get updated
>> as it would as it would if we just did a simple "cd directory". Fix:
>> Probably: Trigger the current working
On 20.6. 3.51, corr...@goncalo.pt wrote:
When we rename the current working directory, $PWD doesn't get updated
as it would as it would if we just did a simple "cd directory".
Fix:
Probably: Trigger the current working directory refresh event, like it
is already done with the cd command.
