ksh Auto-Completion PuTTY Configuration












0














I'm having a bit of a problem configuring my PuTTY client to work with the auto-completion feature in the ksh shell.



I do a listing on the root with the directories /home and /homeroot and it returns the directories in a list just fine. I can't select it, though, by hitting X = (where X is the number).



/home/nitrodist>ls /h        #hits esc + =
1) home/
2) homeroot/
#hits 2 + = for the 'homeroot' dir
1) home/
2) homeroot/
#hits just the '=' key.
1) home/
2) homeroot/


Any ideas? I've su -'d to another user who can actually do it with their PuTTY session and I can't do it there, which makes me think it's a PuTTY configuration issue. This is running on a ksh93 shell on HP-UX, if that makes any difference.



Here's my ksh config:



/home/campbelm>set -o
Current option settings
allexport off
bgnice on
emacs off
errexit off
gmacs off
ignoreeof off
interactive on
keyword off
markdirs off
monitor on
noexec off
noclobber off
noglob off
nolog off
notify off
nounset off
privileged off
restricted off
trackall off
verbose off
vi on
viraw on
xtrace off
/home/campbelm>









share|improve this question





























    0














    I'm having a bit of a problem configuring my PuTTY client to work with the auto-completion feature in the ksh shell.



    I do a listing on the root with the directories /home and /homeroot and it returns the directories in a list just fine. I can't select it, though, by hitting X = (where X is the number).



    /home/nitrodist>ls /h        #hits esc + =
    1) home/
    2) homeroot/
    #hits 2 + = for the 'homeroot' dir
    1) home/
    2) homeroot/
    #hits just the '=' key.
    1) home/
    2) homeroot/


    Any ideas? I've su -'d to another user who can actually do it with their PuTTY session and I can't do it there, which makes me think it's a PuTTY configuration issue. This is running on a ksh93 shell on HP-UX, if that makes any difference.



    Here's my ksh config:



    /home/campbelm>set -o
    Current option settings
    allexport off
    bgnice on
    emacs off
    errexit off
    gmacs off
    ignoreeof off
    interactive on
    keyword off
    markdirs off
    monitor on
    noexec off
    noclobber off
    noglob off
    nolog off
    notify off
    nounset off
    privileged off
    restricted off
    trackall off
    verbose off
    vi on
    viraw on
    xtrace off
    /home/campbelm>









    share|improve this question



























      0












      0








      0







      I'm having a bit of a problem configuring my PuTTY client to work with the auto-completion feature in the ksh shell.



      I do a listing on the root with the directories /home and /homeroot and it returns the directories in a list just fine. I can't select it, though, by hitting X = (where X is the number).



      /home/nitrodist>ls /h        #hits esc + =
      1) home/
      2) homeroot/
      #hits 2 + = for the 'homeroot' dir
      1) home/
      2) homeroot/
      #hits just the '=' key.
      1) home/
      2) homeroot/


      Any ideas? I've su -'d to another user who can actually do it with their PuTTY session and I can't do it there, which makes me think it's a PuTTY configuration issue. This is running on a ksh93 shell on HP-UX, if that makes any difference.



      Here's my ksh config:



      /home/campbelm>set -o
      Current option settings
      allexport off
      bgnice on
      emacs off
      errexit off
      gmacs off
      ignoreeof off
      interactive on
      keyword off
      markdirs off
      monitor on
      noexec off
      noclobber off
      noglob off
      nolog off
      notify off
      nounset off
      privileged off
      restricted off
      trackall off
      verbose off
      vi on
      viraw on
      xtrace off
      /home/campbelm>









      share|improve this question















      I'm having a bit of a problem configuring my PuTTY client to work with the auto-completion feature in the ksh shell.



      I do a listing on the root with the directories /home and /homeroot and it returns the directories in a list just fine. I can't select it, though, by hitting X = (where X is the number).



      /home/nitrodist>ls /h        #hits esc + =
      1) home/
      2) homeroot/
      #hits 2 + = for the 'homeroot' dir
      1) home/
      2) homeroot/
      #hits just the '=' key.
      1) home/
      2) homeroot/


      Any ideas? I've su -'d to another user who can actually do it with their PuTTY session and I can't do it there, which makes me think it's a PuTTY configuration issue. This is running on a ksh93 shell on HP-UX, if that makes any difference.



      Here's my ksh config:



      /home/campbelm>set -o
      Current option settings
      allexport off
      bgnice on
      emacs off
      errexit off
      gmacs off
      ignoreeof off
      interactive on
      keyword off
      markdirs off
      monitor on
      noexec off
      noclobber off
      noglob off
      nolog off
      notify off
      nounset off
      privileged off
      restricted off
      trackall off
      verbose off
      vi on
      viraw on
      xtrace off
      /home/campbelm>






      unix shell putty ksh hp-ux






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 8 '11 at 14:18

























      asked Mar 7 '11 at 21:47









      Nitrodist

      1,27621124




      1,27621124






















          1 Answer
          1






          active

          oldest

          votes


















          0














          It doesn't have anything to do with PuTTY.



          Try:



          Esc = then 2 Esc =



          or



          Tab Tab then 2 Tab






          share|improve this answer





















          • Already tried the above line before and the second line was my gut instinct when I first started using ksh. Sorry, not at work until tomorrow to definitely test.
            – Nitrodist
            Mar 7 '11 at 23:14










          • OK, just tried those commands and it definitely doesn't work.
            – Nitrodist
            Mar 8 '11 at 14:00










          • @Nitrodist: The keystrokes I showed are for emacs mode. I should have asked whether you are using vi mode. What specific version of ksh (echo $KSH_VERSION)? Can you check to make sure the other user is using the same version? Your keystrokes work fine for me through PuTTY to a Linux system running 93t+. Are you using the regular number keys or the numeric keypad (try both)?
            – Dennis Williamson
            Mar 8 '11 at 15:57










          • >echo ${.sh.version}; Version M-12/28/93e It's really bizarre. His version is the same. He had ignoreeof set to on in one case and it worked, and then ignoreeof set to off in another case which gave behavior similar to mine. So I set it to on but it didn't work. My numpad doesn't feature an equals key that works.
            – Nitrodist
            Mar 8 '11 at 20:08








          • 1




            Well, it looks like there is a version difference between the AIX and HP-UX servers that we were testing it on. Version E doesn't work at all but version T does. Also, my shell had been set to ksh instead of ksh93, leading to much more confusion.
            – Nitrodist
            Mar 8 '11 at 20:49













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f254534%2fksh-auto-completion-putty-configuration%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          It doesn't have anything to do with PuTTY.



          Try:



          Esc = then 2 Esc =



          or



          Tab Tab then 2 Tab






          share|improve this answer





















          • Already tried the above line before and the second line was my gut instinct when I first started using ksh. Sorry, not at work until tomorrow to definitely test.
            – Nitrodist
            Mar 7 '11 at 23:14










          • OK, just tried those commands and it definitely doesn't work.
            – Nitrodist
            Mar 8 '11 at 14:00










          • @Nitrodist: The keystrokes I showed are for emacs mode. I should have asked whether you are using vi mode. What specific version of ksh (echo $KSH_VERSION)? Can you check to make sure the other user is using the same version? Your keystrokes work fine for me through PuTTY to a Linux system running 93t+. Are you using the regular number keys or the numeric keypad (try both)?
            – Dennis Williamson
            Mar 8 '11 at 15:57










          • >echo ${.sh.version}; Version M-12/28/93e It's really bizarre. His version is the same. He had ignoreeof set to on in one case and it worked, and then ignoreeof set to off in another case which gave behavior similar to mine. So I set it to on but it didn't work. My numpad doesn't feature an equals key that works.
            – Nitrodist
            Mar 8 '11 at 20:08








          • 1




            Well, it looks like there is a version difference between the AIX and HP-UX servers that we were testing it on. Version E doesn't work at all but version T does. Also, my shell had been set to ksh instead of ksh93, leading to much more confusion.
            – Nitrodist
            Mar 8 '11 at 20:49


















          0














          It doesn't have anything to do with PuTTY.



          Try:



          Esc = then 2 Esc =



          or



          Tab Tab then 2 Tab






          share|improve this answer





















          • Already tried the above line before and the second line was my gut instinct when I first started using ksh. Sorry, not at work until tomorrow to definitely test.
            – Nitrodist
            Mar 7 '11 at 23:14










          • OK, just tried those commands and it definitely doesn't work.
            – Nitrodist
            Mar 8 '11 at 14:00










          • @Nitrodist: The keystrokes I showed are for emacs mode. I should have asked whether you are using vi mode. What specific version of ksh (echo $KSH_VERSION)? Can you check to make sure the other user is using the same version? Your keystrokes work fine for me through PuTTY to a Linux system running 93t+. Are you using the regular number keys or the numeric keypad (try both)?
            – Dennis Williamson
            Mar 8 '11 at 15:57










          • >echo ${.sh.version}; Version M-12/28/93e It's really bizarre. His version is the same. He had ignoreeof set to on in one case and it worked, and then ignoreeof set to off in another case which gave behavior similar to mine. So I set it to on but it didn't work. My numpad doesn't feature an equals key that works.
            – Nitrodist
            Mar 8 '11 at 20:08








          • 1




            Well, it looks like there is a version difference between the AIX and HP-UX servers that we were testing it on. Version E doesn't work at all but version T does. Also, my shell had been set to ksh instead of ksh93, leading to much more confusion.
            – Nitrodist
            Mar 8 '11 at 20:49
















          0












          0








          0






          It doesn't have anything to do with PuTTY.



          Try:



          Esc = then 2 Esc =



          or



          Tab Tab then 2 Tab






          share|improve this answer












          It doesn't have anything to do with PuTTY.



          Try:



          Esc = then 2 Esc =



          or



          Tab Tab then 2 Tab







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 7 '11 at 22:48









          Dennis Williamson

          76k14129167




          76k14129167












          • Already tried the above line before and the second line was my gut instinct when I first started using ksh. Sorry, not at work until tomorrow to definitely test.
            – Nitrodist
            Mar 7 '11 at 23:14










          • OK, just tried those commands and it definitely doesn't work.
            – Nitrodist
            Mar 8 '11 at 14:00










          • @Nitrodist: The keystrokes I showed are for emacs mode. I should have asked whether you are using vi mode. What specific version of ksh (echo $KSH_VERSION)? Can you check to make sure the other user is using the same version? Your keystrokes work fine for me through PuTTY to a Linux system running 93t+. Are you using the regular number keys or the numeric keypad (try both)?
            – Dennis Williamson
            Mar 8 '11 at 15:57










          • >echo ${.sh.version}; Version M-12/28/93e It's really bizarre. His version is the same. He had ignoreeof set to on in one case and it worked, and then ignoreeof set to off in another case which gave behavior similar to mine. So I set it to on but it didn't work. My numpad doesn't feature an equals key that works.
            – Nitrodist
            Mar 8 '11 at 20:08








          • 1




            Well, it looks like there is a version difference between the AIX and HP-UX servers that we were testing it on. Version E doesn't work at all but version T does. Also, my shell had been set to ksh instead of ksh93, leading to much more confusion.
            – Nitrodist
            Mar 8 '11 at 20:49




















          • Already tried the above line before and the second line was my gut instinct when I first started using ksh. Sorry, not at work until tomorrow to definitely test.
            – Nitrodist
            Mar 7 '11 at 23:14










          • OK, just tried those commands and it definitely doesn't work.
            – Nitrodist
            Mar 8 '11 at 14:00










          • @Nitrodist: The keystrokes I showed are for emacs mode. I should have asked whether you are using vi mode. What specific version of ksh (echo $KSH_VERSION)? Can you check to make sure the other user is using the same version? Your keystrokes work fine for me through PuTTY to a Linux system running 93t+. Are you using the regular number keys or the numeric keypad (try both)?
            – Dennis Williamson
            Mar 8 '11 at 15:57










          • >echo ${.sh.version}; Version M-12/28/93e It's really bizarre. His version is the same. He had ignoreeof set to on in one case and it worked, and then ignoreeof set to off in another case which gave behavior similar to mine. So I set it to on but it didn't work. My numpad doesn't feature an equals key that works.
            – Nitrodist
            Mar 8 '11 at 20:08








          • 1




            Well, it looks like there is a version difference between the AIX and HP-UX servers that we were testing it on. Version E doesn't work at all but version T does. Also, my shell had been set to ksh instead of ksh93, leading to much more confusion.
            – Nitrodist
            Mar 8 '11 at 20:49


















          Already tried the above line before and the second line was my gut instinct when I first started using ksh. Sorry, not at work until tomorrow to definitely test.
          – Nitrodist
          Mar 7 '11 at 23:14




          Already tried the above line before and the second line was my gut instinct when I first started using ksh. Sorry, not at work until tomorrow to definitely test.
          – Nitrodist
          Mar 7 '11 at 23:14












          OK, just tried those commands and it definitely doesn't work.
          – Nitrodist
          Mar 8 '11 at 14:00




          OK, just tried those commands and it definitely doesn't work.
          – Nitrodist
          Mar 8 '11 at 14:00












          @Nitrodist: The keystrokes I showed are for emacs mode. I should have asked whether you are using vi mode. What specific version of ksh (echo $KSH_VERSION)? Can you check to make sure the other user is using the same version? Your keystrokes work fine for me through PuTTY to a Linux system running 93t+. Are you using the regular number keys or the numeric keypad (try both)?
          – Dennis Williamson
          Mar 8 '11 at 15:57




          @Nitrodist: The keystrokes I showed are for emacs mode. I should have asked whether you are using vi mode. What specific version of ksh (echo $KSH_VERSION)? Can you check to make sure the other user is using the same version? Your keystrokes work fine for me through PuTTY to a Linux system running 93t+. Are you using the regular number keys or the numeric keypad (try both)?
          – Dennis Williamson
          Mar 8 '11 at 15:57












          >echo ${.sh.version}; Version M-12/28/93e It's really bizarre. His version is the same. He had ignoreeof set to on in one case and it worked, and then ignoreeof set to off in another case which gave behavior similar to mine. So I set it to on but it didn't work. My numpad doesn't feature an equals key that works.
          – Nitrodist
          Mar 8 '11 at 20:08






          >echo ${.sh.version}; Version M-12/28/93e It's really bizarre. His version is the same. He had ignoreeof set to on in one case and it worked, and then ignoreeof set to off in another case which gave behavior similar to mine. So I set it to on but it didn't work. My numpad doesn't feature an equals key that works.
          – Nitrodist
          Mar 8 '11 at 20:08






          1




          1




          Well, it looks like there is a version difference between the AIX and HP-UX servers that we were testing it on. Version E doesn't work at all but version T does. Also, my shell had been set to ksh instead of ksh93, leading to much more confusion.
          – Nitrodist
          Mar 8 '11 at 20:49






          Well, it looks like there is a version difference between the AIX and HP-UX servers that we were testing it on. Version E doesn't work at all but version T does. Also, my shell had been set to ksh instead of ksh93, leading to much more confusion.
          – Nitrodist
          Mar 8 '11 at 20:49




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f254534%2fksh-auto-completion-putty-configuration%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

          Alcedinidae

          Origin of the phrase “under your belt”?