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

Episode 3: No mention of letter case for file names and directories #736

Open
jfessic opened this Issue Mar 9, 2018 · 2 comments

Comments

Projects
None yet
5 participants
@jfessic

jfessic commented Mar 9, 2018

Hello,
In "Working with Files and Directories" under "Good names for files and directories" I think it would be good advice to suggest that file names contain only lower case letters. If nothing else, it would be worthwhile to emphasize the importance of being consistent with letter case when choosing file names.
My understanding is that Unix is always case sensitive, while Windows is not, and macs depend on how the OS was configured when installed. It can be very puzzling for someone who is not aware of this behavior and doesn't realize the different effects it can have on their files. It is also good advice to develop a habit for how you will name files and stick with it.

@shwina

This comment has been minimized.

Member

shwina commented Mar 10, 2018

I am +1 for this addition. Just a comment: some "built-in" directories like Desktop and Documents do not follow these conventions. Perhaps any explanation should also account for this.

@loz-hurst

This comment has been minimized.

Contributor

loz-hurst commented Jun 12, 2018

My understanding is that Unix is always case sensitive

This depends on the filesystem being used. By default Mac OSX is NOT case sensitive, despite being an actual Unix (bearing in mind Linux is not a Unix but a clone).

My opinion is that it should be phrased along the lines of "Most filenames are lowercase by convention, although some desktop environments may create a default set of directories with capitols at the start, such as Desktop and Documents".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment