Update README.md: Note to mac users regarding startup file. #261
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
regarding the Platform.userConfigDir and startup file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Regarding sclangs
Platform.userConfigDirand startup file.contents should be self-explanatory...
This wasn't terribly obvious to me, because once you figure out that you can set a config file via argument to sclang, you can then use that to make sclang find all the extensions you use... That leaves only one component of the
Platform.userConfigDirwhose path can't be manually set: the startup file... and it seems it can't be set, or only after startup, which sort of defeats the purpose.I had to do some sleuthing in sc's source (common/SC_Filesystem_macos.cpp) to figure this out, so I thought I might add a note here. It's technically not a scnvim issue but a sc one, but it might help some folks make the switch. And a doc change is quicker than messing with actual code.
(otoh, if there is actually some reasonably elegant way to set the config directory path for sclang, I'd certainly like to know about it... but again, that's a sc issue.)