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

Update some stale information in README.md #1190

Merged
merged 1 commit into from
Feb 24, 2023
Merged

Update some stale information in README.md #1190

merged 1 commit into from
Feb 24, 2023

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Feb 24, 2023

  • Remove reference to ~/.emscripten. We no longer use the home directory to store config information by default, either in emscripten or in emsdk.
  • Remove some references to The Emscripten Command Prompt. While I suppose this is referring to the windows-only emcmdprompt.bat, and I suppose it means "any shell where activate has been run", I think its more clear to simply avoid using the term.

- Remove reference to `~/.emscripten`.  We no longer use the home
  directory to store config information by default, either in
  emscripten or in emsdk.
- Remove some references to `The Emscripten Command Prompt`.  While I
  suppose this is referring to the windows-only `emcmdprompt.bat`, and I
  suppose it means "any shell where `activate` has been run", I think
  its more clear to simply avoid using the term.
@sbc100 sbc100 requested review from kripken and juj February 24, 2023 15:37
@sbc100 sbc100 merged commit ea2059f into main Feb 24, 2023
@sbc100 sbc100 deleted the update_docs branch February 24, 2023 18:34
shlomif pushed a commit to shlomif/emsdk that referenced this pull request Sep 29, 2023
- Remove reference to `~/.emscripten`.  We no longer use the home
  directory to store config information by default, either in
  emscripten or in emsdk.
- Remove some references to `The Emscripten Command Prompt`.  While I
  suppose this is referring to the windows-only `emcmdprompt.bat`, and I
  suppose it means "any shell where `activate` has been run", I think
  its more clear to simply avoid using the term.
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

Successfully merging this pull request may close these issues.

2 participants