Skip to content

Default Prompt on MacOS is now %, not $#1877

Merged
das-g merged 4 commits into
DjangoGirls:masterfrom
hjwp:prompt-on-mac-is-dollar
Jul 18, 2026
Merged

Default Prompt on MacOS is now %, not $#1877
das-g merged 4 commits into
DjangoGirls:masterfrom
hjwp:prompt-on-mac-is-dollar

Conversation

@hjwp

@hjwp hjwp commented Sep 20, 2025

Copy link
Copy Markdown
Contributor

Update prompt section to reflect that zsh on mac now defaults to %

NB:

@das-g das-g left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

AFAIR, that change in the prompt sign is due to MacOS having changed from Bash as the default shell to zsh. I wonder whether any other parts of the tutorial need updating due to that.

Comment thread en/intro_to_command_line/prompt.md Outdated
@hjwp
hjwp force-pushed the prompt-on-mac-is-dollar branch from c2216d3 to 1ab15e2 Compare July 18, 2026 08:15
@hjwp

hjwp commented Jul 18, 2026

Copy link
Copy Markdown
Contributor Author

AFAIR, that change in the prompt sign is due to MacOS having changed from Bash as the default shell to zsh. I wonder whether any other parts of the tutorial need updating due to that.

hey @das-g, so somewhat dauntingly the answer is probably yes. at the moment, most listings are split into two: "on windows, do this. on mac or linux, do that". and the prompt in the "mac or linux" section is a $. so to fully feed through this change, theoretically we'd have to change every single set of command blocks from having two sections (windows+mac/linux) to having 3 sections -- windows, mac, and linux separately.

that feels like a big and painful change. do we really want to go ahead and do it? bearing in mind the only difference between mac and linux will be the prompt, not the commands? can we think of some more lightweight way to incorporate this change?

@hjwp
hjwp force-pushed the prompt-on-mac-is-dollar branch from 9a0f03a to e4ef334 Compare July 18, 2026 08:44
@hjwp

hjwp commented Jul 18, 2026

Copy link
Copy Markdown
Contributor Author

i want to say, people have been following the tutorial just fine on macos for the several years now despite there being a $ in their command listings, so maybe it's worth merging now and thinking about how to fix all the listings in a separate PR?

@hjwp
hjwp marked this pull request as ready for review July 18, 2026 08:49
@hjwp

hjwp commented Jul 18, 2026

Copy link
Copy Markdown
Contributor Author

options for (later? separate pr?) fixes to all listings

  1. turn all commands from 2 blocks to 3 blocks. cumbersome but accurate!
  2. switch all macos/linux commands from $ to % - maybe there are more mac users than linux ones, and the linux ones are less likely to be confused?
  3. leave them as-is with the $ -- dollar is a fairly common convention in online tutorials/documentation
  4. get rid of all the prompts -- they confuse people anyway and make copy-pasting hard.

no perfect solution! wdyt?

@das-g das-g left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good to me!

@das-g

das-g commented Jul 18, 2026

Copy link
Copy Markdown
Member

I was more worried that our current Linux/Mac commands might use bashisms (Bash-specific syntax or idioms) somewhere. If indeed people have followed the tutorial fine on Mac (and thus presumably zsh) that's probably not the case.

Additional sections just for the different prompt are IMO not worth it, even if they were (or maybe are, as that should be amendable to (classically, i.e. non-LLM) automated editing, with —say— Vim, (s)ed, awk or a simple Python script) easy to add. Also, separate sections for Linux and Mac might give the wrong impression that CLI skills taught by the tutorial are less transferable between UNIX-like operating systems (such as Linux, Mac OS and BSD) than they actually are.

@das-g
das-g merged commit 0c8021f into DjangoGirls:master Jul 18, 2026
1 check passed
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