ADEXL switch default ocean script editor

There is a SKILL variable called editor which is seeded from the UNIX environment variable $EDITOR which sets the editor used.

Check in the CIW what the value of editor is. Then you can do

editor="nedit"

for example. This could go in your .cdsinit.

Something must be setting either $EDITOR or editor, because emacs is not the default... (vi is - because it is guaranteed to be there, whether you like it or not - I don't want to start an editor war!)

Regards,

Andrew.

Is $EDITOR set up in your UNIX environment - i.e. is that what is causing it to be set? If so, maybe you can set that environment variable in your personal .cshrc/.login or .bashrc - whichever shell you're using.

Most companies have something set up in their central .cdsinit file to look for local customization files too, typically in your working directory or home directory. The default behaviour is that virtuoso looks first in the installation in <ICinstDir>/tools/dfII/local, then in working dir, then in home dir. The first that is found is loaded. Alternatively it can use the Cadence Search File mechanism (sometimes known as setup.loc - search in the documentation for more details). However, in all cases, it loads just the first found - and you have to add code into the .cdsinit to look for local files if you want additional places to look.

So your central file could have:

when(isFile("~/.cdsinit")
  loadi("~/.cdsinit")
)

or similar to look for a personal .cdsinit file.

Andrew.

Ok. Added it in .cshrc, and now the editor variable is changed. However, my preferred edit is vim and this editor is runned "inside" a terminal. ADEXL(or vim) gives me a warning when trying to edit a file:

*WARNING* editFile: Vim: Warning: Output is not to a terminal

There is some default handling of EDITOR being "vi" - it transforms that automatically to do "xterm -e vi". That doesn't happen if EDITOR is set to "vim" though. So you either need to set EDITOR to "xterm -e vim" or "gvim" (if you have that available) - that is vim in a standalone window.

Virtuoso doesn't really have any way of knowing whether your editor works in a standalone window (such as emacs, nedit, gvim, gedit), or runs in a terminal (vi, vim, ex, nano etc). So you have to tell it - we just have a default mapping built in to handle EDITOR/editor being "vi".

Regards,

Andrew.