Open relative files from executing program path#123
Open relative files from executing program path#123TheThirdOne merged 2 commits intoTheThirdOne:masterfrom
Conversation
|
As currently implemented this should break programs that execute using the API or launch from the CLI. I don't believe either sets
There are situations where this could be very confusing. If you have multiple files open, are using the setting to assemble all open, and some of the files are in different directories, the selected file when you assemble could change the CWD (current working directory). Additionally, I think most IDEs use a single CWD per workspace/project and do not change the CWD based on which file in the "main" file. For example IntelliJ's default behavior is to set the CWD to the base directory of the current project. So while I agree that students may find this more intuitive, it would be counter what most existing software does and has the opportunity to be very confusing so I will not merge it as is. If this were behind a setting named something like "Derive current working directory from main file" I would merge it though. |
|
I believe I've addressed your feedback with the latest commit. There is now a setting option to enable this if the user wants it when using the GUI. When using the CLI, it uses the RARS directory as before. |
When giving a relative file path, RARS will look from the path of the RISC-V program, not the from the RARS path. This is more intuitive. Absolute file paths remain unaffected.