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

Fixup and update cmd.exe shelling out docs #1605

Closed
wants to merge 1 commit into from

Conversation

Kissaki
Copy link
Contributor

@Kissaki Kissaki commented Nov 1, 2024

The documentation about shelling out cmd.exe commands was outdated, incomplete, and confusing.

  • It mixed past tense "used to" and the forwarded commands without being clear about their relationship and differences
  • There have been multiple undocumented changes across versions
  • Neither Nu release notes nor this or the book escaping [the shell] mention these version differences

The docs receive a significant update to structure and information:

  • Introduce a headlined section for the forwarded commands
  • Introduce version-blocks to describe differences between versions
  • Describe forwarded command list changes across versions within a same-behavior block
  • Differentiates between CMD.EXE and cmd.exe (the shell and the executable/forward call)

These version docs may not be useful in the long run, given the version release ages. Nevertheless, these docs will serve as a good, thorough reference even if the information about older versions will be removed at some point or even soon.

The docs themselves provide enough context and source links to verify their correctness. I will not repeat those here in the commit description.

@@ -1,6 +1,6 @@
# Coming from CMD.EXE

This table was last updated for Nu 0.67.0.
This table was last updated for Nu 0.99.1.
Copy link
Contributor Author

@Kissaki Kissaki Nov 1, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not go over the command table. I was unsure whether it should remain the previous, be updated to the new, or split across concerns.

I chose to update it for simplicity, thinking issues can still be resolved either way when they come up/get reported.

But given that this refers to the table specifically, maybe it should remain the previous version?

@Kissaki
Copy link
Contributor Author

Kissaki commented Nov 1, 2024

CI failure on a file I did not change

error: `punctutation` should be `punctuation`
  --> ./book/modules/creating_modules.md:468:7

=> #1606

The documentation about shelling out cmd.exe commands was outdated, incomplete, and confusing.

* It mixed past tense "used to" and the forwarded commands without being clear about their relationship and differences
* There have been multiple undocumented changes across versions
* Neither Nu release notes nor this or the book escaping [the shell] mention these version differences

The docs receive a significant update to structure and information:

* Introduce a headlined section for the forwarded commands
* Introduce version-blocks to describe differences between versions
* Describe forwarded command list changes across versions within a same-behavior block
* Differentiates between CMD.EXE and `cmd.exe` (the shell and the executable/forward call)

These version docs may not be useful in the long run, given the version release ages.
Nevertheless, these docs will serve as a good, thorough reference even if the information about older versions will be removed at some point or even soon.

The docs themselves provide enough context and source links to verify their correctness. I will not repeat those here in the commit description.
@fdncred
Copy link
Collaborator

fdncred commented Nov 1, 2024

I don't really see the value of mentioning old versions of nushell here.

@Kissaki
Copy link
Contributor Author

Kissaki commented Nov 1, 2024

Shall I update it only with the most recent info then?

Or is merging this, and then doing a follow-up to reduce it to the recent version viable, which would produce a conclusive doc of the behavior changes in the git log?

@fdncred
Copy link
Collaborator

fdncred commented Nov 1, 2024

ya, i think it would be better to fix it here and only have info on the latest version.

Kissaki added a commit to Kissaki/nushell.github.io that referenced this pull request Nov 2, 2024
Replaces nushell#1605 (which documented behavior across versions).

The "if no executable by that name exists" has been wrong since 0.94.0 (not disclosed in release notes, but consequence of 6c649809d38a687cd63b59ab028b7f30207e5663).

The "used to" (prior version 0.67 2022-08-16) is very old, and no longer worth it to keep.

Add information about forwarded commands overshadowing external files.
@Kissaki Kissaki closed this Nov 2, 2024
fdncred added a commit that referenced this pull request Nov 2, 2024
* Update forwarded cmd.exe commands docs

Replaces #1605 (which documented behavior across versions).

The "if no executable by that name exists" has been wrong since 0.94.0 (not disclosed in release notes, but consequence of 6c649809d38a687cd63b59ab028b7f30207e5663).

The "used to" (prior version 0.67 2022-08-16) is very old, and no longer worth it to keep.

Add information about forwarded commands overshadowing external files.

* Improve wording

* 'forwarded' -> 'internal'

Co-authored-by: Darren Schroeder <[email protected]>

---------

Co-authored-by: Darren Schroeder <[email protected]>
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