Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

shell.nss already has stuff in it #516

Open
CityguyUSA opened this issue Sep 21, 2024 · 2 comments
Open

shell.nss already has stuff in it #516

CityguyUSA opened this issue Sep 21, 2024 · 2 comments

Comments

@CityguyUSA
Copy link

Configuration file has several lines of existing code. I'm not sure where I'm suppose to put the "item(title='Hello, World!' cmd=msg('Hello @user.name'))" referenced in the Get Started document.

@RubicBG
Copy link
Collaborator

RubicBG commented Sep 21, 2024

there is no limit to which nss file you put your code in, but to be logically consistent, let it NOT be in shell.nss - better create a new nss file for your code (for example MyStuff.nss), make an import statement in shell.nss for the new file. (import 'MyStuff.nss' or import 'imports/MyStuff.nss' based on the location of the file)

@CityguyUSA
Copy link
Author

I get what you're saying but you should probably update the Get Started document. I understand from what you wrote the configuration could incorporate multiple .nss files. And that it makes sense for ease of configuration to maybe have multiple .nss that are essentially sections that can be included or removed on a moments notice.

So I create my own file but I still don't know where it should get imported as there currently appear to be 2 sections doing imports of multiple files. Not knowing what's in any of them could make a random choice of location a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants