• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1122
  • Last Modified:

! nn and !! with ksh

Hi all,

Now I can use ksh from csh but I face another issues :
- when I enter !! it raises ksh: !!: not found
- when I want to reexecute a command under ksh e.g. : ! nn, it have : ksh: 114: not found.

Thanks in advance.
0
Richard Coffre
Asked:
Richard Coffre
1 Solution
 
yuzhCommented:
Hi  pyxos,

     Now you can put :
     EDITOR=vi
     export EDITOR
     in your .profile
     
and
     put
     set -o vi
     in your .kshrc file

after that when you usr ksh, and type in
     . $HOME/.profile
     . $HOME/.kshrc

      you can use <Esc> k to serach you command line history

or  type in:
     <Esc> k /<serch-patten>  to search you commands from the
history.
     this command line editor behave like the vi editor, you can edit you
command use the same keys as vi.

     I hope this information help.

     Regards
          yuzh
     

0
 
griesshCommented:
Another way (I like this one even more)

In your .env file, add:

set -o emacs

# Arrows
#
alias __A=^P                    # uparrow
alias __B=^N                    # down arrow
alias __C=^F                    # left arrow
alias __D=^B                    # right arrow

to use the arrow keys on your keyboard to go back and forth in your history.

(The ^P is a Ctrl+P key, same for the others ...)

======
Werner
0
 
mnashadkaCommented:
If you're using the vi editor as yuzh suggested, r nn is the same as !nn:
>history
1 ls
2 cd /
3 grep "hello" file

>r 2
cd /
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Richard Coffree-commerce Product ManagerAuthor Commented:
Hi Werner,

When is the file .env loaded ?
Do I have to source it manually ?

Thanks ina advance
0
 
griesshCommented:
No, as soon as you type your "ksh" the shell will source your .env file (locate it in your home directory). To test (I use that to debug these scripts) just put a "echo Now in .env" in the first line of .env. You should see that text as soon as you start ksh.

======
Werner  
0
 
griesshCommented:
And if it is not working, ksh is looking for an environment variable 'ENV' that points to the .env file.
So you should set in your cshell login:

setenv ENV=$HOME/.env

======
Werner
0
 
griesshCommented:
And if you need a good book, try "Bolsky/Korn : The New Kornshell, command and programming Language" (Prentice Hall PTR)

======
Werner
0
 
yuzhCommented:
Hi pyxos,

   Not all favour of UNIX system come with .env now. eg. Solaris, SCO and Debian (Linux) etc. that's why I tell you
to put:
   export ENV=$HOME/.kshrc in your .profile
   by the way, the env command tell you all your enviroment
variables settings.

   "source" is a csh/tcsh term!
   If you default shell is ksh, when you login, it first look at .profile and .kshrc file in your home dir, otherwise, it look for a systems wide profile file.

  I hope that this infor help.

Regards
  yuzh

   
0
 
yuzhCommented:
Hi pyxos,

   As Werner said, if yor prefer to use emacs, you just need to replace my vi with emacs and put it in your .profile or .kshrc file, it should work.
   I think vi is more powerfull.

Regards
   yuzh



0
 
griesshCommented:
yuzh

>>  Not all favour of UNIX system come with .env now. eg. Solaris, SCO and Debian (Linux) etc. that's why I tell you
to put: export ENV=$HOME/.kshrc in your .profile

What do you mean with that?

It doesn't matter what name the file has. It is important that the ENV variable is set to point to that file! What would be more obvious to use .env for ENV?
Anyway, the .profile is the file used when your login shell is ksh, csh uses .login and .cshrc. So setting the ENV in .profile will only help when your login shell is ksh.

======
Werner
0
 
yuzhCommented:
Hi griessh ,

   When people use something like:

    export ENV=File-name
    it will do the job as long as the file has all the ENV settings, by convention, the ksh people trend to use .kshrc as the file name.  

    Cheers

    yuzh


0
 
griesshCommented:
yuzh

I doubt that. I know many people using the .env convention and if you look into the kornshell book I mentioned (oneof the authors is David Korn!) they use the .profile for login and the ENV variable without mentioning a name.

======
Werner
0
 
yuzhCommented:
Hi Werner,

    I think the purpose for this website is for helpping people or getting help from other people, not for arguing.

    It happen I have a few books on my book case, please check them
out:
    The Korn Shell user & programming Manual
                     -by Anatole Olczak
     UNIX Clearly Explained
                     -by Richard L Petersen
     A Practical Guide to the UNIX System
                     -by M. G. Sobell
      SCO UNIX  user's manual

     And
     "Best UNIX Tips EVER"

     they all talking about .kshrc.


============== END======================================

yuzh
0
 
griesshCommented:
yuzh

That's great! And David Korn uses .... ENV

======
Werner
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now