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

New file dialog does not respect custom configuration's scripting directory #122

Open
SirBlockles opened this issue Dec 16, 2019 · 0 comments

Comments

@SirBlockles
Copy link

SirBlockles commented Dec 16, 2019

The new file dialog ignores SM configurations with a custom scripting directory - even though I only have one SM profile configured, the new file dialog still insists on creating the SP file in /sourcepawn/scripts, instead of the directory where my compiler is according to my active profile.
sm
Is it possible to at least have the option to have new SP files default to being created in the same directory as your profile's scripting directory?

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

1 participant