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

Run Options should persist per project #484

Open
catskull opened this issue Jun 29, 2015 · 4 comments
Open

Run Options should persist per project #484

catskull opened this issue Jun 29, 2015 · 4 comments

Comments

@catskull
Copy link

Every time I restart Atom, I have to reconfigure my run options. I propose that script save the run options somewhere in the project so they persist between relaunches.

I'm on Windows 7, on Atom 1.0.0 (current) using script 2.26.0 (current).

@korantir
Copy link

korantir commented Jul 2, 2015

have same problem. it is very annoying.
but #169

maybe it could be fixed by init script or by a couple of code lines. I'm not familiar with coffee, but trying to fix it. Sadly, I don't have much time.

@korantir
Copy link

korantir commented Jul 2, 2015

Well, i can offer u temporary solution for cwd. For some reasons, if script can not find correct path in PATHs of your system (it is my case) it uses cwd from run options and doesn't save it after restart . From code it can be seen, that script uses first value of PATH if it can't find any. Setting cwd to first position (first of SYSTEM (not USER) in windows) removes problem with grabbing of correct cwd.

for further work script->lib->script-view.coffee and other adjacent files

@rgbkrk
Copy link
Member

rgbkrk commented Jul 2, 2015

There's a way for packages to serialize state per project, it came out after this package was put together. There's nothing holding it back from saving the options, I think it was suggested in the original #74 too.

@korantir I definitely agree we should persist PATH on restart (and Atom itself probably should keep that on restart).

I'd certainly like to see persistence in the options and PATH.

@KurtLoeffler
Copy link

I don't see how it wasn't implemented this way to begin with. 3 years later its still not addressed. There's a "Script: Save Options" command that does nothing and is not mentioned in the readme.

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

4 participants