Browsing this Thread:
1 Anonymous Users
|
Re: "c:version" always check files in $PATH instead of current path or specified one
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
@LukeJerry
It has nothing to do with the command path. What happens is that version by default always checks first if a library, device or command by that name is already loaded in memory and uses that if that is the case. If you want to force C:version to check a file on disk you should use the "FILE" switch. version file t:update/devs/fat.handler
Posted on: 2013/1/31 13:21
|
|||
|
||||
|
"c:version" always check files in $PATH instead of current path or specified one
|
||||
|---|---|---|---|---|
|
Home away from home
|
Hi,
updating the new fat.handler I grabbed a screenshot showing an odd behaviour of c:version command. Seems that if the argument of 'version' is found in the PATH variable, the current path or any specified paths are ignored. See attached screenshot. Is this a bug? limitation? feature? I'm used to check version of files with 'strings $filename | grep VER', but maybe our version could be improved/fixed? Thx - Cheers - LuKe Attach file:  (0.00 KB)
Posted on: 2013/1/31 11:44
|
|||
|
"I'm told they let DiskDoctor decide its own fate. They put the sources on a floppy, then ran DiskDoctor on it. The floppy was trashed, so was DiskDoctor." --Dave Haynie
|
||||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
