Advertisement
Help Keep Boards Alive. Support us by going ad free today. See here: https://subscriptions.boards.ie/.
If we do not hit our goal we will be forced to close the site.

Current status: https://keepboardsalive.com/

Annual subs are best for most impact. If you are still undecided on going Ad Free - you can also donate using the Paypal Donate option. All contribution helps. Thank you.
https://www.boards.ie/group/1878-subscribers-forum

Private Group for paid up members of Boards.ie. Join the club.

Windows Command Line Issue.

  • 02-07-2013 02:37PM
    #1
    ZENER
    Registered Users, Registered Users 2 Posts: 6,167 ✭✭✭


    Hi all, bit of an odd one here - at least to me it is.

    System is Windows Vista Business 32 bit on a Dell GX520 with 2GB RAM.

    When I open a command line window I can see directory names in full: e.g.

    c:\users\ken\documents

    All fine, but I noticed today after editing a test file with the edit command, saving the file and exiting the editor, my prompt went back to :-

    c:\users\ken\DOCUME~1

    Doing a DIR command displays files as normal, i.e. long file names appear correctly.

    I know that with a FAT drive filenames are limited to 8.3 format and recall well the confusion in Windows 98 etc. when working in the command line because of this. However this is an NTFS system which is supposed not to have this limitation right ?

    Can anyone shed any light on this ?

    Thanks

    Ken


Comments

  • #2
    GreenWolfe
    Registered Users, Registered Users 2 Posts: 1,731 ✭✭✭GreenWolfe


    It's probably reverting to 8.3 format because edit is a DOS program to begin with. If you have local admin rights, you're probably better off setting up nano for Windows. Just put the path to the executable directory into your PATH system environment variable.


  • #3
    Capt'n Midnight
    Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 96,056 Mod ✭✭✭✭Capt'n Midnight


    EarthlyPangaea wrote: »
    If you have local admin rights, you're probably better off setting up nano for Windows.
    No that'll just confuse the poor chap.

    and then it'll be the religious wars of nano vs. vi vs vim vs emacs all over again


    then again edlin was only for heroes and masochists


    re the user name , I've posted this elsewhere
    http://www.livescience.com/1398-early-earth-purple-study-suggests.html


  • #4
    ZENER
    Registered Users, Registered Users 2 Posts: 6,167 ✭✭✭ZENER


    EarthlyPangaea wrote: »
    It's probably reverting to 8.3 format because edit is a DOS program to begin with. If you have local admin rights, you're probably better off setting up nano for Windows. Just put the path to the executable directory into your PATH system environment variable.

    IT was more just a curiosity thing really. I've used vi in the past along with other editors. I just wondered why this was happening and why it only effected the prompt and not the directory listings.

    Thanks.

    Ken


  • #5
    gouche
    Registered Users, Registered Users 2 Posts: 420 ✭✭gouche


    You know I've always used nano on any Linux systems but never even knew it existed for Windows.
    I don't do much command line editing in Windows but that'll come in handy - cheers!


Advertisement