Trash and linkage?

Debian 3.1
Here is an interesting curiosity that I ran across. It isn't a bug, just
something that I didn't know existed. I will see if I can explain it.

I am building a Perl script and work on it at home and at work. When I am
through with it for the day (or night), I tar up the whole subdirectory
and email it to myself so I can get it at the other location.

I use Kate for the source and open a separate console to test with.

Tonight, differently than usual, I opened the console FIRST and moved to
the project directory. Then I moved that whole (old) subdirectory to the
trash (using the GUI in a different virtual console, not the console I
opened earlier) and then untarred the current project to the same place.
So what happened is that I sent to trash a subdirectory that my console
was still looking at.

Then I run the program to make sure that it is still working from this
afternoon at work. It doesn't. The source looks fine, but when executed
it looks like last night's work. Changes to the source don't produce any
changes when run, although exiting Kate and reloading the source always
gives the new changes.

Then I did a cd.. out of the console window and moved back in and
everything worked fine.

So, obviously, Linux kept some kind of link to the old perl script that
was in the trash even though there was a new script by the same name now
in the same place that the console window is looking at. And nothing was
touching the old deleted script. And even though you can't usually run a
program in the trash bin without retrieving it first.

Don't quite understand the linkage yet, but it definitely explains a few
weird quirks from the past when I couldn't seem to get changes to take in
my source.

No big deal, and it was my fault for deleting something that I was in. But
it is good to know not to do it anymore.

RMK
.

Quantcast