Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 20910
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

when is .cdsinit.local loaded?

SteveRFIC

I have a questions on .cdsinit.local file

I did some customization (bindkeys etc.) in .cdsinit.local file and I put the file in my cadence working directory.

When I start cadence, when is .cdsinit.local loaded?

What I found is that some of the customization gets overwritten by scripts loaded later from the project/company environment. As a results, I have to load again my bindkeys after cadence fully starts.

Is there a way to put .cdsinit.local at the end of the list of files loaded when cadence starts, so that it won't get overwritten?

Or is there a way to use the pop up window (like the what's new window)  to trigger the loading of some skill code?

Thanks! 

Parents

  • Thanks Andew!

    Indeed this is customized settings from the CAD team, where loading .cdsinit.local file is defined in .cdsinit

    It seems that .cdsinit is the only place to define any customized settings, is this correct? Does cadence also try to load some other files? 

    I remember that Cadence searches a few paths for .cdsinit file before starts, does it load the first one it finds? what if I have two .cdsinit file located at different locations, and they differ in content, will both .cdsinit file be loaded?

Reply

  • Thanks Andew!

    Indeed this is customized settings from the CAD team, where loading .cdsinit.local file is defined in .cdsinit

    It seems that .cdsinit is the only place to define any customized settings, is this correct? Does cadence also try to load some other files? 

    I remember that Cadence searches a few paths for .cdsinit file before starts, does it load the first one it finds? what if I have two .cdsinit file located at different locations, and they differ in content, will both .cdsinit file be loaded?

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.