On 4/23/12 3:57 AM, Artur Rataj wrote:
> To be exact, symlink is in the directory ~/a, and it points to ~/test and
> there is also a directory ~/.java. So, after cd ~/a/symlink, there are two
> ../.java files -- one in the physical parent, and one in the logical
> parent. The former is a directory,
To be exact, symlink is in the directory ~/a, and it points to ~/test and
there is also a directory ~/.java. So, after cd ~/a/symlink, there are two
../.java files -- one in the physical parent, and one in the logical
parent. The former is a directory, the latter is a plain file.
~/a/symlink$ cd .
On 4/20/12 4:41 AM, Artur Rataj wrote:
> ~/a$ mkdir .java
> ~/a$ cd symlink
> ~/a/symlink$ cd ../.java/
> ~/a/.java$
> ~/a/.java$ cd ../
> ~/a$ rm -r .java && touch .java
> ~/a$ cd symlink
> ~/a/symlink$ cd ../.java/
> ~/.java$
>
> Should it really be like that?
I can't reproduce it. Is the foll
On 4/19/12 9:03 AM, Artur Rataj wrote:
> I want the logical view, and I think there is one by now. But there is a
> file missing in the logical directory, when cd ../ is completed from a
> symlink.
>
> ~/projects/art/dev$ ls -la
> drwxr-xr-x 6 art art 4096 2012-02-24 16:21 .bzr
> lrwxrwxrwx 1 a
...continuation:
~/.java$ cd ../a
~/a$ rm -r .java
~/a$ cd symlink
~/a/symlink$ cd ../ [now completion does not work]
~/a/symlink$ cd ../.java/
~/.java$
So, cd looks into the logical directory, and if the lookup fails, then it
looks into the physical directory. The cd completion from a symlink,
t
~/a$ mkdir .java
~/a$ cd symlink
~/a/symlink$ cd ../.java/
~/a/.java$
~/a/.java$ cd ../
~/a$ rm -r .java && touch .java
~/a$ cd symlink
~/a/symlink$ cd ../.java/
~/.java$
Should it really be like that?
I want the logical view, and I think there is one by now. But there is a
file missing in the logical directory, when cd ../ is completed from a
symlink.
~/projects/art/dev$ ls -la
drwxr-xr-x 6 art art 4096 2012-02-24 16:21 .bzr
lrwxrwxrwx 1 art art 18 2012-04-16 14:48 lib -> ../../hth/dev/lib/
On 4/19/12 7:38 AM, Artur Rataj wrote:
> Yes, it appears that "lib" is indeed a symlink. Is it possible to treat it
> as if it were "just here" with the tab completion?
By default, bash uses a logical view of the file system, in which $PWD
and pwd report the current directory using the path used t
Yes, it appears that "lib" is indeed a symlink. Is it possible to treat it
as if it were "just here" with the tab completion?
On 04/19/2012 12:28 PM, Artur Rataj wrote:
~/projects/art/dev/lib$ cd ../
.bzr/ lib/
~/projects/art/dev/lib$ cd ../src
~/projects/art/dev/src$ cd ../
.bzr/ lib/ src/
~/projects/art/dev/src$ cd ../lib
~/projects/art/dev/lib$ cd ../
.bzr/ lib/
Are there any symlinks?
RR
~/projects/art/dev/lib$ cd ../
.bzr/ lib/
~/projects/art/dev/lib$ cd ../src
~/projects/art/dev/src$ cd ../
.bzr/ lib/ src/
~/projects/art/dev/src$ cd ../lib
~/projects/art/dev/lib$ cd ../
.bzr/ lib/
hello, could you explain the following?
~/projects/art/dev/lib$ cd ../
.bzr/ lib/
~/projects/art/dev/lib$ cd ../src
~/projects/art/dev/src$
Artur
12 matches
Mail list logo