View on GitHub

reading-notes

Choosing a text editor

While picking a text editor may seem like a daunting task, it ultimately boils down to personal preference, as many text editors intended for coding share many features with each other.

A few of the things that a code-focused text editor will tend to provide you with include:

Computers also come with a text editor, but it’s generally not recommended to use those for the sake of programming. You will be missing out on all of the features listed above, and the editor itself will not make any attempts to assist you or recognize and autofill commands.

A Text Editor is different from an Integrated Development Environment. (IDE) An IDE has features for file management, debugging, and compiling, so IDEs are recommended only if you know precisely what you will be working, and deploying, in terms of language and final product.

The Git editor for assembling markdown pages on-site is in itself a text editor as well, albiet a rather rudimentary one.

On Terminal Navigation

This is a brief cheat sheet for navigating via the terminal

additional cd tricks

On Linux and Files.

Everything in Linux is a file.

Everything in Linux is Case Sensitive.

a file called text and a file called Text are regarded as different, and if you do a command that includes improper capitalization, then the command will fail.

also:

File Extensions Do Not Exist

You can have file extensions in the names, but the data for what linux treats the file as is embedded in the file itself. Changing a written extension on the file will not actually change the file in any capacity apart from it being named differently now.

Handling Spaces

If a directory has a space in it, then doing cd cool essays will return the error that the directory “cool” does not exist. this can be worked around by adding " around the name of the directory, like so: cd "cool essays"

Back To Main Page.