You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Either way, I find it odd that an assignment we have includes a short snippet that makes people use Nano, which we'll never touch again afterwards. And that's before people are probably clued fully clued in one what to do and not do. Example of recent confusion from a learner about which text editors.
The previous lesson is on text editors where we make the VSCode recommendation.
I'm in a mind that an 80:20 resolution for this would be to add a note underneath
that provides the code draft.txt command instructions instead, and instructions for saving that file in VSCode, as opposed to using Nano.
I was not asked but knowing how to use nano is a good thing - if learners don't configure git correctly, their default text editor will be nano. Many answers on SO or AskUbuntu suggest using nano and people don't realise they could use a different text editor. Same would apply for sudoedit if no editor is provided.
My recollection isn't that great but I do believe using nano never was a pain point ever for learners while going through this content. The note is quite clear that many programmers are fans of particular editors and that VSCode belongs to a different group (graphical) than vim and emacs.
Furthermore, this resource has historically caused problems for WSL2 users (#27338) so stacking even more exceptions would put inclusion of this great resource in jeopardy. I call it a great resource because ever since the lesson has been revamped to use it, the volume of questions relating to using CLI has dropped significantly.
Not an issue exclusive to maintainer feedback - your insight and opinion is also absolutely kore than valid, thank you! Just thought since I'm personally less familiar with this part and potential community pain points, I'd open the discussion in case there are things that are deemed appropriate to do!
Checks
Describe your suggestion
Command Line Basics includes an assignment to swcarpentry's UNIX Shell course. In particular, the Working with Files and Directories section includes some instruction on creating text files in Nano. It also includes a note box within it talking about "Which Editor?", with some language that some people in Discord have thought might make the thought of using editors other than VSCode appealing.
Either way, I find it odd that an assignment we have includes a short snippet that makes people use Nano, which we'll never touch again afterwards. And that's before people are probably clued fully clued in one what to do and not do. Example of recent confusion from a learner about which text editors.
The previous lesson is on text editors where we make the VSCode recommendation.
I'm in a mind that an 80:20 resolution for this would be to add a note underneath
that provides the
code draft.txt
command instructions instead, and instructions for saving that file in VSCode, as opposed to using Nano.Path
Foundations
Lesson Url
https://www.theodinproject.com/lessons/foundations-command-line-basics#assignment
(Optional) Discord Name
No response
(Optional) Additional Comments
No response
The text was updated successfully, but these errors were encountered: