Filenames on the command-line are not resolved
Filenames on the command line are sometimes not
resolved correctly if they contain symbolic links that
refer to .. (the up-one-level directory).
It looks like .. is being evaluated prior to resolving
the symbolic link, rather than resolving the symbolic
For example, take the following directory tree:
> tree -F /dirA
| `-- dirC -> ../dirX/dirY/
With the command
> nc /dirA/dirB/dirC/../fileZ
nEdit tries to open the file '/dirA/dirB/fileZ'.
Other Unix commands (for example: ls, cat, vi) resolve
the filename to '/dirA/dirX/fileZ', which is (in my
opinion) the file that nEdit should open.
This appears to be a Linux issue, since nEdit on
Solaris opens the correct file.
Here is the information about my nEdit configuration:
Sep 30, 2004
Built on: Linux, 386, GNU C
Built at: Oct 1 2004, 15:55:40
With Motif: 2.1.30 [@(#)Motif Version 2.1.30]
Running Motif: 2.1 [unknown]
Server: Hummingbird Communications Ltd. 7110
Visual: 24-bit TrueColor (ID 0x23, Default)
PS -- Sorry about the duplicate ticket. I thought I
was logged in.
Log in to post a comment.