console showing old content after folder renamed in other console

[florin oltean]

I will start by saying that I am using Ubuntu9.10.
The bug is related to the console and renaming the directory that one of the console is in.

For example:
I have 2 consoles open.
In console number 1 I do:

cd /home/florin
mkdir dir1
cd dir1
joe file000

In console number 2 I do:

cd /home/florin
mv dir1 dir2

Now in console 1 "pwd" will show the old path:
pwd # => /home/florin/dir1 and not the correct one: /home/florin/dir2

Also "ls" will show the content
ls # => file000

Even worst:
In console 2 I create a new directory dir1 with a new file named "file000", but a new content,
console 1 will still show the content of the old "file000"

[florin oltean (oltean-florin-ioan)]

I would like to specify that by "console" I understand a "terminal" started from "Applications->Accessories->Terminal". So there are no confusions.

[Will Bickerstaff (willbickerstaff)]

Even more confusing is that if you then create a file in in terminal 1 while still apparently working in the old non-existent dir, it then appears in terminal 2 in the newly re-located dir, So bash clearly knows where we really are it's just not updating the prompt. This also happens in VTs so I'm guessing it's a bash issue rather than one with gnome-terminal.

[Will Bickerstaff (willbickerstaff)]

So this looks like it's intended behaviour, to improve performance. The bug is already reported at http://groups.google.com/group/gnu.bash.bug/browse_thread/thread/5621c726c6050292/2c4156d96acbc2c5?lnk=gst&q=pwd#2c4156d96acbc2c5, and if it really is an issue, then there a couple of workarounds in the response.

[Will Bickerstaff (willbickerstaff)]

Once I run pwd -P, /bin/pwd or env pwd wouldn't it be reasonable for environment variable $PWD to be refreshed?

[Will Bickerstaff (willbickerstaff)]

No it wouldn't just been pointed here, http://thread.gmane.org/gmane.comp.shells.bash.bugs/15335 which explains why it's the way it is