Why does ⎕cmd not work when my current directory is a UNC ?
Forum rules
The FAQ is a read-only forum which is in general updated only by employees of Dyalog Ltd. It replaces the FAQ page which existed under http://www.dyalog.com. Rather than rejecting other posts to this forum, such posts will be put in a moderation queue, and moved to a more appropriate forum.
The FAQ is a read-only forum which is in general updated only by employees of Dyalog Ltd. It replaces the FAQ page which existed under http://www.dyalog.com. Rather than rejecting other posts to this forum, such posts will be put in a moderation queue, and moved to a more appropriate forum.
1 post
• Page 1 of 1
Why does ⎕cmd not work when my current directory is a UNC ?
You may find that expressions such as ⎕cmd'dir' return empty results. This will happen if the current working directory is a UNC, rather than based on drive letter and directory.
So supposing \\mymachine\mydir is mapped to Z:\mydir, then if the shortcut to Dyalog APL has the "Start In" directory defined as "Z:\mydir", ⎕cmd'dir' will return the contents of mydir. If however "Start In" is defined to be \\mymachine\mydir then ⎕cmd'dir' will return an empty result.
This is a limitation in Windows, rather than a limitation of Dyalog APL. More information can be found at http://support.microsoft.com/?kbid=156276.
So supposing \\mymachine\mydir is mapped to Z:\mydir, then if the shortcut to Dyalog APL has the "Start In" directory defined as "Z:\mydir", ⎕cmd'dir' will return the contents of mydir. If however "Start In" is defined to be \\mymachine\mydir then ⎕cmd'dir' will return an empty result.
This is a limitation in Windows, rather than a limitation of Dyalog APL. More information can be found at http://support.microsoft.com/?kbid=156276.
-
AndyS|Dyalog - Posts: 263
- Joined: Tue May 12, 2009 6:06 pm
1 post
• Page 1 of 1
Return to Frequently Asked Questions (FAQ)
Who is online
Users browsing this forum: No registered users and 1 guest
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group