aboutsummaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorRon Yorston <rmy@pobox.com>2019-03-30 11:30:20 +0000
committerRon Yorston <rmy@pobox.com>2019-03-30 11:56:56 +0000
commitbe2949717934c19890879cf2a8fc74c5da55d1c7 (patch)
tree3207e0b18137525309787e0fa9e7a732f04983b7 /init
parent077d4c21c0e48e495bc86ea0dec28e5a7143efa8 (diff)
downloadbusybox-w32-be2949717934c19890879cf2a8fc74c5da55d1c7.tar.gz
busybox-w32-be2949717934c19890879cf2a8fc74c5da55d1c7.tar.bz2
busybox-w32-be2949717934c19890879cf2a8fc74c5da55d1c7.zip
win32: improved support for c:path path names
Microsoft Windows permits path names of the form 'c:path', without a path separator after the colon. The system records a current directory for each drive and the path is interpreted relative to that. Since Windows API calls understand 'c:path' path names many commands in busybox-w32 already work with them. This commit adds the following: - The 'cd' shell built-in interprets 'c:path' path names correctly. Previously it treated them as relative to the shell's concept of the current working directory, not the current directory of the specified drive. - The 'pwd' shell built-in takes the '-a' option to list the current directory for all drives. - 'c:path' path names are subject to tab-completion. Paths of the form 'c:path' don't work for mapped network drives or paths that have been associated with a drive using SUBST. See GitHub issue #147.
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions