Results 1 to 6 of 6
  1. #1

    Sandwichman's Avatar
    Member Since
    Jul 18, 2006
    Posts
    238
    Specs:
    iMac 17" Intel Core Duo, 2 GB RAM + 20" ACD
    In Terminal, can't type l/
    So I use Terminal on occasionally, enough that this is a bit of a problem: whenever I'm in Terminal (even if I'm in one of the text editors like nano), and I type l/ (for example, when typing a path such as /usr/local/bin), the l/ becomes a space.

    For example:

    "cd /usr/local/bin"

    becomes:

    "cd /usr/loca bin " (with that trailing space that I can't get rid of).

    It happens in real-time, not just when you send the command, and goes away if you remove the / after the l in question.

    This makes it a little difficult to move anywhere in Terminal that has those two characters together. I don't have any idea what caused it; I don't think I changed anything (knowingly) to make it happen. I've rebooted several times since it first showed up, have restarted Terminal, logged out and back in, and all the basic tricks.

    I'd greatly appreciate it if someone knows what's happening here- thanks in advance.
    Sitting, waiting, wishing...

  2. #2


    Member Since
    Mar 27, 2008
    Posts
    18
    This may seem like a silly question, but are you sure you're doing l/ and not \l. That would turn into a space.

    Also, you can always hit the TAB key to finish a path. So if you type:

    cd /usr/loc

    And then TAB

    It should finish that bit and let you keep typing.

  3. #3

    mac57's Avatar
    Member Since
    Apr 29, 2006
    Location
    St. Somewhere
    Posts
    4,560
    Specs:
    iMac 27" 3.4 GHz, 256 GB SSD, 2 TB HDD, 8 GB RAM
    Of course you can always use the good 'ol bash unix/Linux escape mechanism to "escape" the key in question. You do this by preceding the key of interest with a "\".

    In your example above, you could type:

    Code:
    cd /usr/local\/bin
    I just tried this in my Terminal.app and it works like a charm (of course I can type "cd /usr/local/bin" with no problem as well).
    My Macs: iMac 27" 3.4 GHz, Mac Pro 3.2 GHz, PowerMac G5 Quad 2.5 GHz, G4 Cube with 1.2 GHz Upgrade
    My iStuff: 64GB iPhone 5, 64GB iPad4, 30GB iPod Video, 16GB iPod Touch
    My OS': Mac OS X Lion, Mac OS X Snow Leopard, Mac OS X Tiger, Mac OS 9.2.2, openSUSE 10.3
    I was on the Mac-Forums honor roll for September 2007

  4. #4


    Member Since
    Mar 27, 2008
    Posts
    18
    Quote Originally Posted by mac57 View Post
    I just tried this in my Terminal.app and it works like a charm (of course I can type "cd /usr/local/bin" with no problem as well).
    I can too, so this is a strange problem!

  5. #5

    Sandwichman's Avatar
    Member Since
    Jul 18, 2006
    Posts
    238
    Specs:
    iMac 17" Intel Core Duo, 2 GB RAM + 20" ACD
    Hi everyone, thanks for the replies.

    raydot:This may seem like a silly question, but are you sure you're doing l/ and not \l. That would turn into a space.
    Not a silly question at all- one of the first things I checked myself. Regarding TAB-completion, it doesn't really work that way for me. It completes just fine, but the l/ becomes a space again. The problem here is that it's not just being interpreted as a space, it *becomes* a space when I type it.

    The way I worked around it was splitting each directory move into separate commands:

    cd /usr
    cd local
    cd (etc...)

    This works because I never have to type "l/" consecutively. By moving one directory at a time it works fine.

    mac57:Of course you can always use the good 'ol bash unix/Linux escape mechanism to "escape" the key in question. You do this by preceding the key of interest with a "\".
    Hm. I guess that works for me too. Not sure why I didn't try that, guess I assumed it would try to do "cd /usr/local bin/" that way. Thanks for the suggestion!

    I still have no idea what's causing it, but it looks like it's relatively easy to work around. Thanks everyone!
    Sitting, waiting, wishing...

  6. #6


    Member Since
    Jun 22, 2009
    Posts
    3
    I'm having pretty much the same problem, except the "/l" gets turned into a non-US-ASCII character (kind of looks like an "L" with a slash through it) instead of a space. It only happens on one of my machines, and on that box it happens for all users, not just me. Typing a lower-case "L" followed by a slash into the Terminal immediately converts the two characters to this weird one. Tab-completion does the same thing, as does the results of "which". Escaping the slash works.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Terminal not allowing me to type
    By chiss in forum OS X - Operating System
    Replies: 2
    Last Post: 11-06-2014, 09:15 PM
  2. Can't type in Terminal
    By hymik in forum Switcher Hangout
    Replies: 1
    Last Post: 05-19-2013, 11:34 AM
  3. Cant type in Terminal
    By -mateusz in forum OS X - Operating System
    Replies: 2
    Last Post: 06-06-2009, 02:12 PM
  4. Can't Type Password in Terminal
    By WriterStitch in forum OS X - Operating System
    Replies: 2
    Last Post: 04-18-2009, 02:31 AM
  5. Terminal service type thing to display mac on PC
    By edokid in forum Switcher Hangout
    Replies: 3
    Last Post: 11-02-2005, 02:48 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •