WIP: chapter on terminals #26
Open
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
NelleV
reviewed
Oct 25, 2021
| write down, and then replicate with copying and pasting, is essential. | ||
|
|
||
| In addition to being more *convenient* when you want to do more than one | ||
| thing at a time, it is also more *reproducible* and less *error-prone*, |
There was a problem hiding this comment.
I would maybe add somewhere that it is more reproducible because it can be automated.
| When faced with their first terminal, most users are dismayed: given how | ||
| slick modern operating systems have become, why are they being forced to | ||
| relive 1980s-style text interfaces? Are programmers really such a backward | ||
| bunch? |
There was a problem hiding this comment.
Well… people have to admit that it looks really really look as well :p
| download other terminal applications with more features such as iTerm2. | ||
| Additionally, IDEs such as VSCode and PyCharm come with a built-in terminal | ||
| (see {doc}`editors-and-ides`). All of these terminals can access different | ||
| *shells*, such as bash, zsh, and fish. Although recent macOS versions default |
There was a problem hiding this comment.
I disagree with this statement. I've switched everything to zsh.
Most commands should be compatible between bash and zsh. The main difference comes from the configuration files.
NelleV
reviewed
Oct 25, 2021
| installing Python somewhere in your home directory, and then adding that | ||
| directory to your path. | ||
|
|
||
| ## Further reading |
There was a problem hiding this comment.
I feel there should be a note on the Python REPL somewhere here.
NelleV
reviewed
Oct 25, 2021
| probably couldn't ever remember the syntax off the top of your head, *but*, | ||
| when you find the instructions, doing things is as easy as copy-paste. For | ||
| flicking a switch in settings, this is not always a huge deal, though even | ||
| then navigating settings menus gets old very quickly. When you try to piece |
NelleV
reviewed
Oct 25, 2021
| Commands in the command prompt are evaluated in the context of the *present | ||
| working directory*, which roughly defines where to look for any files that the | ||
| command might need. For example, after five rounds of reviews and finally | ||
| acceptance and publication, you might never want to look at that paper again! |
There was a problem hiding this comment.
I feel it should be "you will definitely never want to look at that paper again…"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm not happy with the way this is turning out, but I'm pushing it up for discussion.
The biggest issue is Windows, where the situation is a mess and so my advice is all over the place. My current thinking is that I'll leave them with the default approach (CMD.EXE), and add an appendix at the end "Advanced Windows recommendations" for Windows Terminal.