Translation: shell-novice Episode 2

[joelnitta]

Translation: shell-novice Episode 2 "Navigating Files and Directories" (02-filedir.md)

• Please see the README for more information about editing PO files
• Please assign yourself (or add a comment) to the issue before you start translating, so other people know that you are translating.
• Once you have finished translating, send a pull request and reference this issue.

---

• PO fileの編集についてはREADMEをご参照ください。
• あなたが翻訳し始めたと分かるように、翻訳を始める前にこのイシューを自分に割り振って(assign)、あるいはコメントを書いて下さい。
• 翻訳が終わったら、プルリクエストを開いて、このイシューを参照・リンクして下さい。

i18n/po/shell-novice.ja.po

Lines 1462 to 3419 in f4aed5e

	# Front Matter
	#: shell-novice/_episodes/02-filedir.md:1
	msgid ""
	"---\n"
	"title: \"Navigating Files and Directories\"\n"
	"teaching: 30\n"
	"exercises: 10\n"
	"questions:\n"
	"- \"How can I move around on my computer?\"\n"
	"- \"How can I see what files and directories I have?\"\n"
	"- \"How can I specify the location of a file or directory on my computer?\"\n"
	"objectives:\n"
	"- \"Explain the similarities and differences between a file and a directory.\"\n"
	"- \"Translate an absolute path into a relative path and vice versa.\"\n"
	"- \"Construct absolute and relative paths that identify specific files and directories.\"\n"
	"- \"Demonstrate the use of tab completion, and explain its advantages.\"\n"
	"keypoints:\n"
	"- \"The file system is responsible for managing information on the disk.\"\n"
	"- \"Information is stored in files, which are stored in directories (folders).\"\n"
	"- \"Directories can also store other directories, which forms a directory tree.\"\n"
	"- \"`cd path` changes the current working directory.\"\n"
	"- \"`ls path` prints a listing of a specific file or directory; `ls` on its own lists the current working directory.\"\n"
	"- \"`pwd` prints the user's current working directory.\"\n"
	"- \"`whoami` shows the user's current identity.\"\n"
	"- \"`/` on its own is the root directory of the whole file system.\"\n"
	"- \"A relative path specifies a location starting from the current location.\"\n"
	"- \"An absolute path specifies a location from the root of the file system.\"\n"
	"- \"Directory names in a path are separated with `/` on Unix, but `\\\\\\\\` on Windows.\"\n"
	"- \"`..` means 'the directory above the current one'; `.` on its own means 'the current directory'.\"\n"
	"- \"Most files' names are `something.extension`. The extension isn't required, and doesn't guarantee anything, but is normally used to indicate the type of data in the file.\"\n"
	"---"
	msgstr ""
	"---\n"
	"title: \"Navigating Files and Directories\"\n"
	"teaching: 30\n"
	"exercises: 10\n"
	"questions:\n"
	"- \"How can I move around on my computer?\"\n"
	"- \"How can I see what files and directories I have?\"\n"
	"- \"How can I specify the location of a file or directory on my computer?\"\n"
	"objectives:\n"
	"- \"Explain the similarities and differences between a file and a directory.\"\n"
	"- \"Translate an absolute path into a relative path and vice versa.\"\n"
	"- \"Construct absolute and relative paths that identify specific files and directories.\"\n"
	"- \"Demonstrate the use of tab completion, and explain its advantages.\"\n"
	"keypoints:\n"
	"- \"The file system is responsible for managing information on the disk.\"\n"
	"- \"Information is stored in files, which are stored in directories (folders).\"\n"
	"- \"Directories can also store other directories, which forms a directory tree.\"\n"
	"- \"`cd path` changes the current working directory.\"\n"
	"- \"`ls path` prints a listing of a specific file or directory; `ls` on its own lists the current working directory.\"\n"
	"- \"`pwd` prints the user's current working directory.\"\n"
	"- \"`whoami` shows the user's current identity.\"\n"
	"- \"`/` on its own is the root directory of the whole file system.\"\n"
	"- \"A relative path specifies a location starting from the current location.\"\n"
	"- \"An absolute path specifies a location from the root of the file system.\"\n"
	"- \"Directory names in a path are separated with `/` on Unix, but `\\\\\\\\` on Windows.\"\n"
	"- \"`..` means 'the directory above the current one'; `.` on its own means 'the current directory'.\"\n"
	"- \"Most files' names are `something.extension`. The extension isn't required, and doesn't guarantee anything, but is normally used to indicate the type of data in the file.\"\n"
	"---"
	#: shell-novice/_episodes/02-filedir.md:30
	msgid ""
	"The part of the operating system responsible for managing files and directories \n"
	"is called the **file system**.\n"
	"It organizes our data into files,\n"
	"which hold information,\n"
	"and directories (also called \"folders\"),\n"
	"which hold files or other directories."
	msgstr ""
	"The part of the operating system responsible for managing files and directories \n"
	"is called the **file system**.\n"
	"It organizes our data into files,\n"
	"which hold information,\n"
	"and directories (also called \"folders\"),\n"
	"which hold files or other directories."
	#: shell-novice/_episodes/02-filedir.md:37
	msgid ""
	"Several commands are frequently used to create, inspect, rename, and delete files and directories.\n"
	"To start exploring them, we'll go to our open shell window:"
	msgstr ""
	"Several commands are frequently used to create, inspect, rename, and delete files and directories.\n"
	"To start exploring them, we'll go to our open shell window:"
	#: shell-novice/_episodes/02-filedir.md:40
	msgid ""
	"First let's find out where we are by running a command called `pwd`\n"
	"(which stands for \"print working directory\"). Directories are like *places* - at any time\n"
	"while we are using the shell we are in exactly one place, called\n"
	"our **current working directory**. Commands mostly read and write files in the \n"
	"current working directory, i.e. \"here\", so knowing where you are before running\n"
	"a command is important. `pwd` shows you where you are:"
	msgstr ""
	"First let's find out where we are by running a command called `pwd`\n"
	"(which stands for \"print working directory\"). Directories are like *places* - at any time\n"
	"while we are using the shell we are in exactly one place, called\n"
	"our **current working directory**. Commands mostly read and write files in the \n"
	"current working directory, i.e. \"here\", so knowing where you are before running\n"
	"a command is important. `pwd` shows you where you are:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:47
	#: shell-novice/_episodes/02-filedir.md:474
	#: shell-novice/_episodes/02-filedir.md:530
	#: shell-novice/_episodes/02-filedir.md:603
	#: shell-novice/_episodes/02-filedir.md:647
	#: shell-novice/_episodes/03-create.md:27
	#: shell-novice/_episodes/03-create.md:262
	#: shell-novice/_episodes/03-create.md:350
	msgid ""
	"~~~\n"
	"$ pwd\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ pwd\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:52
	#: shell-novice/_episodes/02-filedir.md:608
	msgid ""
	"~~~\n"
	"/Users/nelle\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"/Users/nelle\n"
	"~~~"
	# SC/DC Template label
	#: shell-novice/_episodes/02-filedir.md:55
	#: shell-novice/_episodes/02-filedir.md:135
	#: shell-novice/_episodes/02-filedir.md:158
	#: shell-novice/_episodes/02-filedir.md:321
	#: shell-novice/_episodes/02-filedir.md:414
	#: shell-novice/_episodes/02-filedir.md:443
	#: shell-novice/_episodes/02-filedir.md:482
	#: shell-novice/_episodes/02-filedir.md:493
	#: shell-novice/_episodes/02-filedir.md:538
	#: shell-novice/_episodes/02-filedir.md:552
	#: shell-novice/_episodes/02-filedir.md:611
	#: shell-novice/_episodes/02-filedir.md:655
	#: shell-novice/_episodes/03-create.md:35
	#: shell-novice/_episodes/03-create.md:45
	#: shell-novice/_episodes/03-create.md:69
	#: shell-novice/_episodes/03-create.md:188
	#: shell-novice/_episodes/03-create.md:270
	#: shell-novice/_episodes/03-create.md:281
	#: shell-novice/_episodes/03-create.md:358
	#: shell-novice/_episodes/03-create.md:370
	#: shell-novice/_episodes/03-create.md:397
	#: shell-novice/_episodes/03-create.md:441
	#: shell-novice/_episodes/03-create.md:489
	#: shell-novice/_episodes/04-pipefilter.md:43
	#: shell-novice/_episodes/04-pipefilter.md:66
	#: shell-novice/_episodes/04-pipefilter.md:188
	#: shell-novice/_episodes/04-pipefilter.md:220
	#: shell-novice/_episodes/04-pipefilter.md:286
	#: shell-novice/_episodes/04-pipefilter.md:362
	#: shell-novice/_episodes/04-pipefilter.md:379
	#: shell-novice/_episodes/04-pipefilter.md:418
	#: shell-novice/_episodes/04-pipefilter.md:448
	#: shell-novice/_episodes/04-pipefilter.md:460
	#: shell-novice/_episodes/04-pipefilter.md:759
	#: shell-novice/_episodes/04-pipefilter.md:775
	#: shell-novice/_episodes/04-pipefilter.md:797
	#: shell-novice/_episodes/04-pipefilter.md:813
	#: shell-novice/_episodes/05-loop.md:80 shell-novice/_episodes/05-loop.md:313
	#: shell-novice/_episodes/05-loop.md:449 shell-novice/_episodes/05-loop.md:472
	#: shell-novice/_episodes/05-loop.md:528 shell-novice/_episodes/06-script.md:73
	#: shell-novice/_episodes/06-script.md:106
	#: shell-novice/_episodes/06-script.md:124
	#: shell-novice/_episodes/06-script.md:140
	#: shell-novice/_episodes/06-script.md:162
	#: shell-novice/_episodes/06-script.md:178
	#: shell-novice/_episodes/06-script.md:195
	#: shell-novice/_episodes/06-script.md:211
	#: shell-novice/_episodes/06-script.md:255
	#: shell-novice/_episodes/06-script.md:272 shell-novice/_episodes/07-find.md:54
	#: shell-novice/_episodes/07-find.md:76 shell-novice/_episodes/07-find.md:93
	#: shell-novice/_episodes/07-find.md:112 shell-novice/_episodes/07-find.md:128
	#: shell-novice/_episodes/07-find.md:148 shell-novice/_episodes/07-find.md:165
	#: shell-novice/_episodes/07-find.md:179 shell-novice/_episodes/07-find.md:200
	#: shell-novice/_episodes/07-find.md:230 shell-novice/_episodes/07-find.md:422
	#: shell-novice/_episodes/07-find.md:451 shell-novice/_episodes/07-find.md:472
	#: shell-novice/_episodes/07-find.md:484 shell-novice/_episodes/07-find.md:516
	#: shell-novice/_episodes/07-find.md:548 shell-novice/_episodes/07-find.md:579
	msgid "{: .output}"
	msgstr "{: .output}"
	#: shell-novice/_episodes/02-filedir.md:57
	msgid ""
	"Here,\n"
	"the computer's response is `/Users/nelle`,\n"
	"which is Nelle's **home directory**:"
	msgstr ""
	"Here,\n"
	"the computer's response is `/Users/nelle`,\n"
	"which is Nelle's **home directory**:"
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:61
	msgid "> ## Home Directory Variation"
	msgstr "> ## Home Directory Variation"
	#: shell-novice/_episodes/02-filedir.md:62
	msgid ""
	">\n"
	"> The home directory path will look different on different operating systems.\n"
	"> On Linux it may look like `/home/nelle`,\n"
	"> and on Windows it will be similar to `C:\\Documents and Settings\\nelle` or\n"
	"> `C:\\Users\\nelle`. \n"
	"> (Note that it may look slightly different for different versions of Windows.)\n"
	"> In future examples, we've used Mac output as the default - Linux and Windows\n"
	"> output may differ slightly, but should be generally similar. "
	msgstr ""
	">\n"
	"> The home directory path will look different on different operating systems.\n"
	"> On Linux it may look like `/home/nelle`,\n"
	"> and on Windows it will be similar to `C:\\Documents and Settings\\nelle` or\n"
	"> `C:\\Users\\nelle`. \n"
	"> (Note that it may look slightly different for different versions of Windows.)\n"
	"> In future examples, we've used Mac output as the default - Linux and Windows\n"
	"> output may differ slightly, but should be generally similar. "
	#: shell-novice/_episodes/02-filedir.md:72
	msgid ""
	"To understand what a \"home directory\" is,\n"
	"let's have a look at how the file system as a whole is organized. For the\n"
	"sake of this example, we'll be\n"
	"illustrating the filesystem on our scientist Nelle's computer. After this\n"
	"illustration, you'll be learning commands to explore your own filesystem,\n"
	"which will be constructed in a similar way, but not be exactly identical. "
	msgstr ""
	"To understand what a \"home directory\" is,\n"
	"let's have a look at how the file system as a whole is organized. For the\n"
	"sake of this example, we'll be\n"
	"illustrating the filesystem on our scientist Nelle's computer. After this\n"
	"illustration, you'll be learning commands to explore your own filesystem,\n"
	"which will be constructed in a similar way, but not be exactly identical. "
	#: shell-novice/_episodes/02-filedir.md:79
	msgid "On Nelle's computer, the filesystem looks like this:"
	msgstr "On Nelle's computer, the filesystem looks like this:"
	#: shell-novice/_episodes/02-filedir.md:81
	msgid ""
	msgstr ""
	#: shell-novice/_episodes/02-filedir.md:83
	msgid ""
	"At the top is the **root directory**\n"
	"that holds everything else.\n"
	"We refer to it using a slash character `/` on its own;\n"
	"this is the leading slash in `/Users/nelle`."
	msgstr ""
	"At the top is the **root directory**\n"
	"that holds everything else.\n"
	"We refer to it using a slash character `/` on its own;\n"
	"this is the leading slash in `/Users/nelle`."
	#: shell-novice/_episodes/02-filedir.md:88
	msgid ""
	"Inside that directory are several other directories:\n"
	"`bin` (which is where some built-in programs are stored),\n"
	"`data` (for miscellaneous data files),\n"
	"`Users` (where users' personal directories are located),\n"
	"`tmp` (for temporary files that don't need to be stored long-term),\n"
	"and so on. "
	msgstr ""
	"Inside that directory are several other directories:\n"
	"`bin` (which is where some built-in programs are stored),\n"
	"`data` (for miscellaneous data files),\n"
	"`Users` (where users' personal directories are located),\n"
	"`tmp` (for temporary files that don't need to be stored long-term),\n"
	"and so on. "
	#: shell-novice/_episodes/02-filedir.md:95
	msgid ""
	"We know that our current working directory `/Users/nelle` is stored inside `/Users`\n"
	"because `/Users` is the first part of its name.\n"
	"Similarly,\n"
	"we know that `/Users` is stored inside the root directory `/`\n"
	"because its name begins with `/`."
	msgstr ""
	"We know that our current working directory `/Users/nelle` is stored inside `/Users`\n"
	"because `/Users` is the first part of its name.\n"
	"Similarly,\n"
	"we know that `/Users` is stored inside the root directory `/`\n"
	"because its name begins with `/`."
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:101
	msgid "> ## Slashes"
	msgstr "> ## Slashes"
	#: shell-novice/_episodes/02-filedir.md:102
	msgid ""
	">\n"
	"> Notice that there are two meanings for the `/` character.\n"
	"> When it appears at the front of a file or directory name,\n"
	"> it refers to the root directory. When it appears *inside* a name,\n"
	"> it's just a separator."
	msgstr ""
	">\n"
	"> Notice that there are two meanings for the `/` character.\n"
	"> When it appears at the front of a file or directory name,\n"
	"> it refers to the root directory. When it appears *inside* a name,\n"
	"> it's just a separator."
	#: shell-novice/_episodes/02-filedir.md:109
	msgid ""
	"Underneath `/Users`,\n"
	"we find one directory for each user with an account on Nelle's machine,\n"
	"her colleagues the Mummy and Wolfman. "
	msgstr ""
	"Underneath `/Users`,\n"
	"we find one directory for each user with an account on Nelle's machine,\n"
	"her colleagues the Mummy and Wolfman. "
	#: shell-novice/_episodes/02-filedir.md:113
	msgid ""
	msgstr ""
	#: shell-novice/_episodes/02-filedir.md:115
	msgid ""
	"The Mummy's files are stored in `/Users/imhotep`,\n"
	"Wolfman's in `/Users/larry`,\n"
	"and Nelle's in `/Users/nelle`. Because Nelle is the user in our\n"
	"examples here, this is why we get `/Users/nelle` as our home directory. \n"
	"Typically, when you open a new command prompt you will be in\n"
	"your home directory to start. "
	msgstr ""
	"The Mummy's files are stored in `/Users/imhotep`,\n"
	"Wolfman's in `/Users/larry`,\n"
	"and Nelle's in `/Users/nelle`. Because Nelle is the user in our\n"
	"examples here, this is why we get `/Users/nelle` as our home directory. \n"
	"Typically, when you open a new command prompt you will be in\n"
	"your home directory to start. "
	#: shell-novice/_episodes/02-filedir.md:122
	msgid ""
	"Now let's learn the command that will let us see the contents of our\n"
	"own filesystem. We can see what's in our home directory by running `ls`,\n"
	"which stands for \"listing\":"
	msgstr ""
	"Now let's learn the command that will let us see the contents of our\n"
	"own filesystem. We can see what's in our home directory by running `ls`,\n"
	"which stands for \"listing\":"
	# code block
	#: shell-novice/_episodes/02-filedir.md:126
	#: shell-novice/_episodes/03-create.md:180
	#: shell-novice/_episodes/03-create.md:243
	msgid ""
	"~~~\n"
	"$ ls\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:131
	msgid ""
	"~~~\n"
	"Applications Documents Library Music Public\n"
	"Desktop Downloads Movies Pictures\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"Applications Documents Library Music Public\n"
	"Desktop Downloads Movies Pictures\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:137
	msgid ""
	"(Again, your results may be slightly different depending on your operating\n"
	"system and how you have customized your filesystem.)"
	msgstr ""
	"(Again, your results may be slightly different depending on your operating\n"
	"system and how you have customized your filesystem.)"
	#: shell-novice/_episodes/02-filedir.md:140
	msgid ""
	"`ls` prints the names of the files and directories in the current directory. \n"
	"We can make its output more comprehensible by using the **flag** `-F`\n"
	"(also known as a **switch** or an **option**) ,\n"
	"which tells `ls` to add a marker to file and directory names to indicate what\n"
	"they are. A trailing `/` indicates that this is a directory. Depending on your\n"
	"settings, it might also use colors to indicate whether each entry is a file or \n"
	"directory.\n"
	"You might recall that we used `ls -F` in an earlier example."
	msgstr ""
	"`ls` prints the names of the files and directories in the current directory. \n"
	"We can make its output more comprehensible by using the **flag** `-F`\n"
	"(also known as a **switch** or an **option**) ,\n"
	"which tells `ls` to add a marker to file and directory names to indicate what\n"
	"they are. A trailing `/` indicates that this is a directory. Depending on your\n"
	"settings, it might also use colors to indicate whether each entry is a file or \n"
	"directory.\n"
	"You might recall that we used `ls -F` in an earlier example."
	# code block
	#: shell-novice/_episodes/02-filedir.md:149
	#: shell-novice/_episodes/02-filedir.md:484
	#: shell-novice/_episodes/03-create.md:37
	#: shell-novice/_episodes/03-create.md:61
	msgid ""
	"~~~\n"
	"$ ls -F\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls -F\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:154
	msgid ""
	"~~~\n"
	"Applications/ Documents/ Library/ Music/ Public/\n"
	"Desktop/ Downloads/ Movies/ Pictures/\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"Applications/ Documents/ Library/ Music/ Public/\n"
	"Desktop/ Downloads/ Movies/ Pictures/\n"
	"~~~"
	# header
	#: shell-novice/_episodes/02-filedir.md:160
	msgid "### Getting help"
	msgstr "### Getting help"
	#: shell-novice/_episodes/02-filedir.md:162
	msgid ""
	"`ls` has lots of other **flags**. There are two common ways to find out how \n"
	"to use a command and what flags it accepts:"
	msgstr ""
	"`ls` has lots of other **flags**. There are two common ways to find out how \n"
	"to use a command and what flags it accepts:"
	# ordered list
	#: shell-novice/_episodes/02-filedir.md:165
	msgid "1. We can pass a `--help` flag to the command, such as:"
	msgstr "1. We can pass a `--help` flag to the command, such as:"
	#: shell-novice/_episodes/02-filedir.md:166
	msgid ""
	" ~~~\n"
	" $ ls --help\n"
	" ~~~"
	msgstr ""
	" ~~~\n"
	" $ ls --help\n"
	" ~~~"
	# SC/DC Template label
	#: shell-novice/_episodes/02-filedir.md:169
	#: shell-novice/_episodes/02-filedir.md:175 shell-novice/_extras/guide.md:210
	msgid " {: .bash}"
	msgstr " {: .bash}"
	# ordered list
	#: shell-novice/_episodes/02-filedir.md:171
	msgid "2. We can read its manual with `man`, such as:"
	msgstr "2. We can read its manual with `man`, such as:"
	#: shell-novice/_episodes/02-filedir.md:172
	msgid ""
	" ~~~\n"
	" $ man ls \n"
	" ~~~"
	msgstr ""
	" ~~~\n"
	" $ man ls \n"
	" ~~~"
	#: shell-novice/_episodes/02-filedir.md:177
	msgid ""
	"If you use a Mac, or Git for Windows, you might find that only one of these works \n"
	"(probably `man` on Mac and `--help` in Windows). We'll describe both ways."
	msgstr ""
	"If you use a Mac, or Git for Windows, you might find that only one of these works \n"
	"(probably `man` on Mac and `--help` in Windows). We'll describe both ways."
	#: shell-novice/_episodes/02-filedir.md:180
	msgid ""
	"Of course there is a third way: searching the internet via your web browser. \n"
	"When using internet search, including the phrase `unix man page` in your search\n"
	"query will help to find relevant results."
	msgstr ""
	"Of course there is a third way: searching the internet via your web browser. \n"
	"When using internet search, including the phrase `unix man page` in your search\n"
	"query will help to find relevant results."
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:184
	msgid "> ## Manual pages on the web"
	msgstr "> ## Manual pages on the web"
	#: shell-novice/_episodes/02-filedir.md:185
	msgid ""
	">\n"
	"> GNU provides links to its\n"
	"> [manuals](http://www.gnu.org/manual/manual.html) including the\n"
	"> [core GNU utilities](http://www.gnu.org/software/coreutils/manual/coreutils.html),\n"
	"> which covers many commands introduced within this lesson."
	msgstr ""
	">\n"
	"> GNU provides links to its\n"
	"> [manuals](http://www.gnu.org/manual/manual.html) including the\n"
	"> [core GNU utilities](http://www.gnu.org/software/coreutils/manual/coreutils.html),\n"
	"> which covers many commands introduced within this lesson."
	# header
	#: shell-novice/_episodes/02-filedir.md:192
	msgid "#### The `--help` flag"
	msgstr "#### The `--help` flag"
	#: shell-novice/_episodes/02-filedir.md:194
	msgid ""
	"Many bash commands, and programs that people have written that can be\n"
	"run from within bash, support a `--help` flag to display more\n"
	"information on how to use the command or program."
	msgstr ""
	"Many bash commands, and programs that people have written that can be\n"
	"run from within bash, support a `--help` flag to display more\n"
	"information on how to use the command or program."
	# code block
	#: shell-novice/_episodes/02-filedir.md:198
	msgid ""
	"~~~\n"
	"$ ls --help\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls --help\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:203
	msgid ""
	"~~~\n"
	"Usage: ls [OPTION]... [FILE]...\n"
	"List information about the FILEs (the current directory by default).\n"
	"Sort entries alphabetically if none of -cftuvSUX nor --sort is specified.\n"
	"\n"
	"Mandatory arguments to long options are mandatory for short options too.\n"
	" -a, --all do not ignore entries starting with .\n"
	" -A, --almost-all do not list implied . and ..\n"
	" --author with -l, print the author of each file\n"
	" -b, --escape print C-style escapes for nongraphic characters\n"
	" --block-size=SIZE scale sizes by SIZE before printing them; e.g.,\n"
	" '--block-size=M' prints sizes in units of\n"
	" 1,048,576 bytes; see SIZE format below\n"
	" -B, --ignore-backups do not list implied entries ending with ~\n"
	" -c with -lt: sort by, and show, ctime (time of last\n"
	" modification of file status information);\n"
	" with -l: show ctime and sort by name;\n"
	" otherwise: sort by ctime, newest first\n"
	" -C list entries by columns\n"
	" --color[=WHEN] colorize the output; WHEN can be 'always' (default\n"
	" if omitted), 'auto', or 'never'; more info below\n"
	" -d, --directory list directories themselves, not their contents\n"
	" -D, --dired generate output designed for Emacs' dired mode\n"
	" -f do not sort, enable -aU, disable -ls --color\n"
	" -F, --classify append indicator (one of */=>@|) to entries\n"
	" --file-type likewise, except do not append '*'\n"
	" --format=WORD across -x, commas -m, horizontal -x, long -l,\n"
	" single-column -1, verbose -l, vertical -C\n"
	" --full-time like -l --time-style=full-iso\n"
	" -g like -l, but do not list owner\n"
	" --group-directories-first\n"
	" group directories before files;\n"
	" can be augmented with a --sort option, but any\n"
	" use of --sort=none (-U) disables grouping\n"
	" -G, --no-group in a long listing, don't print group names\n"
	" -h, --human-readable with -l and/or -s, print human readable sizes\n"
	" (e.g., 1K 234M 2G)\n"
	" --si likewise, but use powers of 1000 not 1024\n"
	" -H, --dereference-command-line\n"
	" follow symbolic links listed on the command line\n"
	" --dereference-command-line-symlink-to-dir\n"
	" follow each command line symbolic link\n"
	" that points to a directory\n"
	" --hide=PATTERN do not list implied entries matching shell PATTERN\n"
	" (overridden by -a or -A)\n"
	" --indicator-style=WORD append indicator with style WORD to entry names:\n"
	" none (default), slash (-p),\n"
	" file-type (--file-type), classify (-F)\n"
	" -i, --inode print the index number of each file\n"
	" -I, --ignore=PATTERN do not list implied entries matching shell PATTERN\n"
	" -k, --kibibytes default to 1024-byte blocks for disk usage\n"
	" -l use a long listing format\n"
	" -L, --dereference when showing file information for a symbolic\n"
	" link, show information for the file the link\n"
	" references rather than for the link itself\n"
	" -m fill width with a comma separated list of entries\n"
	" -n, --numeric-uid-gid like -l, but list numeric user and group IDs\n"
	" -N, --literal print raw entry names (don't treat e.g. control\n"
	" characters specially)\n"
	" -o like -l, but do not list group information\n"
	" -p, --indicator-style=slash\n"
	" append / indicator to directories\n"
	" -q, --hide-control-chars print ? instead of nongraphic characters\n"
	" --show-control-chars show nongraphic characters as-is (the default,\n"
	" unless program is 'ls' and output is a terminal)\n"
	" -Q, --quote-name enclose entry names in double quotes\n"
	" --quoting-style=WORD use quoting style WORD for entry names:\n"
	" literal, locale, shell, shell-always,\n"
	" shell-escape, shell-escape-always, c, escape\n"
	" -r, --reverse reverse order while sorting\n"
	" -R, --recursive list subdirectories recursively\n"
	" -s, --size print the allocated size of each file, in blocks\n"
	" -S sort by file size, largest first\n"
	" --sort=WORD sort by WORD instead of name: none (-U), size (-S),\n"
	" time (-t), version (-v), extension (-X)\n"
	" --time=WORD with -l, show time as WORD instead of default\n"
	" modification time: atime or access or use (-u);\n"
	" ctime or status (-c); also use specified time\n"
	" as sort key if --sort=time (newest first)\n"
	" --time-style=STYLE with -l, show times using style STYLE:\n"
	" full-iso, long-iso, iso, locale, or +FORMAT;\n"
	" FORMAT is interpreted like in 'date'; if FORMAT\n"
	" is FORMAT1<newline>FORMAT2, then FORMAT1 applies\n"
	" to non-recent files and FORMAT2 to recent files;\n"
	" if STYLE is prefixed with 'posix-', STYLE\n"
	" takes effect only outside the POSIX locale\n"
	" -t sort by modification time, newest first\n"
	" -T, --tabsize=COLS assume tab stops at each COLS instead of 8\n"
	" -u with -lt: sort by, and show, access time;\n"
	" with -l: show access time and sort by name;\n"
	" otherwise: sort by access time, newest first\n"
	" -U do not sort; list entries in directory order\n"
	" -v natural sort of (version) numbers within text\n"
	" -w, --width=COLS set output width to COLS. 0 means no limit\n"
	" -x list entries by lines instead of by columns\n"
	" -X sort alphabetically by entry extension\n"
	" -Z, --context print any security context of each file\n"
	" -1 list one file per line. Avoid '\\n' with -q or -b\n"
	" --help display this help and exit\n"
	" --version output version information and exit\n"
	"\n"
	"The SIZE argument is an integer and optional unit (example: 10K is 10*1024).\n"
	"Units are K,M,G,T,P,E,Z,Y (powers of 1024) or KB,MB,... (powers of 1000).\n"
	"\n"
	"Using color to distinguish file types is disabled both by default and\n"
	"with --color=never. With --color=auto, ls emits color codes only when\n"
	"standard output is connected to a terminal. The LS_COLORS environment\n"
	"variable can change the settings. Use the dircolors command to set it.\n"
	"\n"
	"Exit status:\n"
	" 0 if OK,\n"
	" 1 if minor problems (e.g., cannot access subdirectory),\n"
	" 2 if serious trouble (e.g., cannot access command-line argument).\n"
	"\n"
	"GNU coreutils online help: <http://www.gnu.org/software/coreutils/>\n"
	"Full documentation at: <http://www.gnu.org/software/coreutils/ls>\n"
	"or available locally via: info '(coreutils) ls invocation'\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"Usage: ls [OPTION]... [FILE]...\n"
	"List information about the FILEs (the current directory by default).\n"
	"Sort entries alphabetically if none of -cftuvSUX nor --sort is specified.\n"
	"\n"
	"Mandatory arguments to long options are mandatory for short options too.\n"
	" -a, --all do not ignore entries starting with .\n"
	" -A, --almost-all do not list implied . and ..\n"
	" --author with -l, print the author of each file\n"
	" -b, --escape print C-style escapes for nongraphic characters\n"
	" --block-size=SIZE scale sizes by SIZE before printing them; e.g.,\n"
	" '--block-size=M' prints sizes in units of\n"
	" 1,048,576 bytes; see SIZE format below\n"
	" -B, --ignore-backups do not list implied entries ending with ~\n"
	" -c with -lt: sort by, and show, ctime (time of last\n"
	" modification of file status information);\n"
	" with -l: show ctime and sort by name;\n"
	" otherwise: sort by ctime, newest first\n"
	" -C list entries by columns\n"
	" --color[=WHEN] colorize the output; WHEN can be 'always' (default\n"
	" if omitted), 'auto', or 'never'; more info below\n"
	" -d, --directory list directories themselves, not their contents\n"
	" -D, --dired generate output designed for Emacs' dired mode\n"
	" -f do not sort, enable -aU, disable -ls --color\n"
	" -F, --classify append indicator (one of */=>@|) to entries\n"
	" --file-type likewise, except do not append '*'\n"
	" --format=WORD across -x, commas -m, horizontal -x, long -l,\n"
	" single-column -1, verbose -l, vertical -C\n"
	" --full-time like -l --time-style=full-iso\n"
	" -g like -l, but do not list owner\n"
	" --group-directories-first\n"
	" group directories before files;\n"
	" can be augmented with a --sort option, but any\n"
	" use of --sort=none (-U) disables grouping\n"
	" -G, --no-group in a long listing, don't print group names\n"
	" -h, --human-readable with -l and/or -s, print human readable sizes\n"
	" (e.g., 1K 234M 2G)\n"
	" --si likewise, but use powers of 1000 not 1024\n"
	" -H, --dereference-command-line\n"
	" follow symbolic links listed on the command line\n"
	" --dereference-command-line-symlink-to-dir\n"
	" follow each command line symbolic link\n"
	" that points to a directory\n"
	" --hide=PATTERN do not list implied entries matching shell PATTERN\n"
	" (overridden by -a or -A)\n"
	" --indicator-style=WORD append indicator with style WORD to entry names:\n"
	" none (default), slash (-p),\n"
	" file-type (--file-type), classify (-F)\n"
	" -i, --inode print the index number of each file\n"
	" -I, --ignore=PATTERN do not list implied entries matching shell PATTERN\n"
	" -k, --kibibytes default to 1024-byte blocks for disk usage\n"
	" -l use a long listing format\n"
	" -L, --dereference when showing file information for a symbolic\n"
	" link, show information for the file the link\n"
	" references rather than for the link itself\n"
	" -m fill width with a comma separated list of entries\n"
	" -n, --numeric-uid-gid like -l, but list numeric user and group IDs\n"
	" -N, --literal print raw entry names (don't treat e.g. control\n"
	" characters specially)\n"
	" -o like -l, but do not list group information\n"
	" -p, --indicator-style=slash\n"
	" append / indicator to directories\n"
	" -q, --hide-control-chars print ? instead of nongraphic characters\n"
	" --show-control-chars show nongraphic characters as-is (the default,\n"
	" unless program is 'ls' and output is a terminal)\n"
	" -Q, --quote-name enclose entry names in double quotes\n"
	" --quoting-style=WORD use quoting style WORD for entry names:\n"
	" literal, locale, shell, shell-always,\n"
	" shell-escape, shell-escape-always, c, escape\n"
	" -r, --reverse reverse order while sorting\n"
	" -R, --recursive list subdirectories recursively\n"
	" -s, --size print the allocated size of each file, in blocks\n"
	" -S sort by file size, largest first\n"
	" --sort=WORD sort by WORD instead of name: none (-U), size (-S),\n"
	" time (-t), version (-v), extension (-X)\n"
	" --time=WORD with -l, show time as WORD instead of default\n"
	" modification time: atime or access or use (-u);\n"
	" ctime or status (-c); also use specified time\n"
	" as sort key if --sort=time (newest first)\n"
	" --time-style=STYLE with -l, show times using style STYLE:\n"
	" full-iso, long-iso, iso, locale, or +FORMAT;\n"
	" FORMAT is interpreted like in 'date'; if FORMAT\n"
	" is FORMAT1<newline>FORMAT2, then FORMAT1 applies\n"
	" to non-recent files and FORMAT2 to recent files;\n"
	" if STYLE is prefixed with 'posix-', STYLE\n"
	" takes effect only outside the POSIX locale\n"
	" -t sort by modification time, newest first\n"
	" -T, --tabsize=COLS assume tab stops at each COLS instead of 8\n"
	" -u with -lt: sort by, and show, access time;\n"
	" with -l: show access time and sort by name;\n"
	" otherwise: sort by access time, newest first\n"
	" -U do not sort; list entries in directory order\n"
	" -v natural sort of (version) numbers within text\n"
	" -w, --width=COLS set output width to COLS. 0 means no limit\n"
	" -x list entries by lines instead of by columns\n"
	" -X sort alphabetically by entry extension\n"
	" -Z, --context print any security context of each file\n"
	" -1 list one file per line. Avoid '\\n' with -q or -b\n"
	" --help display this help and exit\n"
	" --version output version information and exit\n"
	"\n"
	"The SIZE argument is an integer and optional unit (example: 10K is 10*1024).\n"
	"Units are K,M,G,T,P,E,Z,Y (powers of 1024) or KB,MB,... (powers of 1000).\n"
	"\n"
	"Using color to distinguish file types is disabled both by default and\n"
	"with --color=never. With --color=auto, ls emits color codes only when\n"
	"standard output is connected to a terminal. The LS_COLORS environment\n"
	"variable can change the settings. Use the dircolors command to set it.\n"
	"\n"
	"Exit status:\n"
	" 0 if OK,\n"
	" 1 if minor problems (e.g., cannot access subdirectory),\n"
	" 2 if serious trouble (e.g., cannot access command-line argument).\n"
	"\n"
	"GNU coreutils online help: <http://www.gnu.org/software/coreutils/>\n"
	"Full documentation at: <http://www.gnu.org/software/coreutils/ls>\n"
	"or available locally via: info '(coreutils) ls invocation'\n"
	"~~~"
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:323
	msgid "> ## Unsupported command-line options"
	msgstr "> ## Unsupported command-line options"
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:324
	msgid "> If you try to use an option (flag) that is not supported, `ls` and other programs"
	msgstr "> If you try to use an option (flag) that is not supported, `ls` and other programs"
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:325
	msgid "> will usually print an error message similar to this:"
	msgstr "> will usually print an error message similar to this:"
	#: shell-novice/_episodes/02-filedir.md:326
	msgid ""
	">\n"
	"> ~~~\n"
	"> $ ls -j\n"
	"> ~~~\n"
	"> {: .language-bash}\n"
	"> \n"
	"> ~~~\n"
	"> ls: invalid option -- 'j'\n"
	"> Try 'ls --help' for more information.\n"
	"> ~~~"
	msgstr ""
	">\n"
	"> ~~~\n"
	"> $ ls -j\n"
	"> ~~~\n"
	"> {: .language-bash}\n"
	"> \n"
	"> ~~~\n"
	"> ls: invalid option -- 'j'\n"
	"> Try 'ls --help' for more information.\n"
	"> ~~~"
	# SC/DC Template label
	#: shell-novice/_episodes/02-filedir.md:336
	msgid "> {: .error}"
	msgstr "> {: .error}"
	# header
	#: shell-novice/_episodes/02-filedir.md:339
	msgid "#### The `man` command"
	msgstr "#### The `man` command"
	#: shell-novice/_episodes/02-filedir.md:341
	msgid ""
	"The other way to learn about `ls` is to type \n"
	"~~~\n"
	"$ man ls\n"
	"~~~"
	msgstr ""
	"The other way to learn about `ls` is to type \n"
	"~~~\n"
	"$ man ls\n"
	"~~~"
	# SC/DC Template label
	#: shell-novice/_episodes/02-filedir.md:345
	msgid "{: .bash}"
	msgstr "{: .bash}"
	#: shell-novice/_episodes/02-filedir.md:347
	msgid ""
	"This will turn your terminal into a page with a description \n"
	"of the `ls` command and its options and, if you're lucky, some examples\n"
	"of how to use it."
	msgstr ""
	"This will turn your terminal into a page with a description \n"
	"of the `ls` command and its options and, if you're lucky, some examples\n"
	"of how to use it."
	#: shell-novice/_episodes/02-filedir.md:351
	msgid ""
	"To navigate through the `man` pages,\n"
	"you may use the up and down arrow keys to move line-by-line,\n"
	"or try the \"b\" and spacebar keys to skip up and down by a full page.\n"
	"To search for a character or word in the `man` pages, \n"
	"use \"/\" followed by the character or word you are searching for. "
	msgstr ""
	"To navigate through the `man` pages,\n"
	"you may use the up and down arrow keys to move line-by-line,\n"
	"or try the \"b\" and spacebar keys to skip up and down by a full page.\n"
	"To search for a character or word in the `man` pages, \n"
	"use \"/\" followed by the character or word you are searching for. "
	#: shell-novice/_episodes/02-filedir.md:357
	msgid "To **quit** the `man` pages, press `q`. "
	msgstr "To **quit** the `man` pages, press `q`. "
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:360
	msgid "> ## Exploring More `ls` Flags"
	msgstr "> ## Exploring More `ls` Flags"
	#: shell-novice/_episodes/02-filedir.md:361
	msgid ""
	">\n"
	"> What does the command `ls` do when used with the `-l` and `-h` flags?\n"
	">\n"
	"> Some of its output is about properties that we do not cover in this lesson (such\n"
	"> as file permissions and ownership), but the rest should be useful\n"
	"> nevertheless.\n"
	">\n"
	"> > ## Solution\n"
	"> > The `-l` flag makes `ls` use a **l**ong listing format, showing not only\n"
	"> > the file/directory names but also additional information such as the file size\n"
	"> > and the time of its last modification. The `-h` flag makes the file size\n"
	"> > \"**h**uman readable\", i.e. display something like `5.3K` instead of `5369`."
	msgstr ""
	">\n"
	"> What does the command `ls` do when used with the `-l` and `-h` flags?\n"
	">\n"
	"> Some of its output is about properties that we do not cover in this lesson (such\n"
	"> as file permissions and ownership), but the rest should be useful\n"
	"> nevertheless.\n"
	">\n"
	"> > ## Solution\n"
	"> > The `-l` flag makes `ls` use a **l**ong listing format, showing not only\n"
	"> > the file/directory names but also additional information such as the file size\n"
	"> > and the time of its last modification. The `-h` flag makes the file size\n"
	"> > \"**h**uman readable\", i.e. display something like `5.3K` instead of `5369`."
	# SC/DC Template label
	#: shell-novice/_episodes/02-filedir.md:373
	#: shell-novice/_episodes/02-filedir.md:387
	#: shell-novice/_episodes/02-filedir.md:706
	#: shell-novice/_episodes/02-filedir.md:727
	#: shell-novice/_episodes/02-filedir.md:753
	#: shell-novice/_episodes/03-create.md:226
	#: shell-novice/_episodes/03-create.md:324
	#: shell-novice/_episodes/03-create.md:471
	#: shell-novice/_episodes/03-create.md:555
	#: shell-novice/_episodes/03-create.md:604
	#: shell-novice/_episodes/03-create.md:650
	#: shell-novice/_episodes/03-create.md:691
	#: shell-novice/_episodes/03-create.md:740
	#: shell-novice/_episodes/04-pipefilter.md:123
	#: shell-novice/_episodes/04-pipefilter.md:168
	#: shell-novice/_episodes/04-pipefilter.md:263
	#: shell-novice/_episodes/04-pipefilter.md:340
	#: shell-novice/_episodes/04-pipefilter.md:483
	#: shell-novice/_episodes/04-pipefilter.md:604
	#: shell-novice/_episodes/04-pipefilter.md:641
	#: shell-novice/_episodes/04-pipefilter.md:702
	#: shell-novice/_episodes/04-pipefilter.md:733
	#: shell-novice/_episodes/04-pipefilter.md:860
	#: shell-novice/_episodes/04-pipefilter.md:884
	#: shell-novice/_episodes/05-loop.md:186 shell-novice/_episodes/05-loop.md:261
	#: shell-novice/_episodes/05-loop.md:282 shell-novice/_episodes/05-loop.md:606
	#: shell-novice/_episodes/05-loop.md:633 shell-novice/_episodes/05-loop.md:685
	#: shell-novice/_episodes/05-loop.md:712
	#: shell-novice/_episodes/06-script.md:312
	#: shell-novice/_episodes/06-script.md:387
	#: shell-novice/_episodes/06-script.md:496
	#: shell-novice/_episodes/06-script.md:526
	#: shell-novice/_episodes/06-script.md:570
	#: shell-novice/_episodes/06-script.md:612
	#: shell-novice/_episodes/07-find.md:249 shell-novice/_episodes/07-find.md:338
	#: shell-novice/_episodes/07-find.md:382 shell-novice/_episodes/07-find.md:605
	#: shell-novice/_episodes/07-find.md:657 shell-novice/_episodes/07-find.md:679
	msgid "> {: .solution}"
	msgstr "> {: .solution}"
	# SC/DC Template label
	#: shell-novice/_episodes/02-filedir.md:374
	#: shell-novice/_episodes/02-filedir.md:388
	#: shell-novice/_episodes/02-filedir.md:707
	#: shell-novice/_episodes/02-filedir.md:728
	#: shell-novice/_episodes/02-filedir.md:754
	#: shell-novice/_episodes/03-create.md:227
	#: shell-novice/_episodes/03-create.md:325
	#: shell-novice/_episodes/03-create.md:472
	#: shell-novice/_episodes/03-create.md:556
	#: shell-novice/_episodes/03-create.md:605
	#: shell-novice/_episodes/03-create.md:651
	#: shell-novice/_episodes/03-create.md:692
	#: shell-novice/_episodes/03-create.md:741
	#: shell-novice/_episodes/04-pipefilter.md:124
	#: shell-novice/_episodes/04-pipefilter.md:169
	#: shell-novice/_episodes/04-pipefilter.md:239
	#: shell-novice/_episodes/04-pipefilter.md:264
	#: shell-novice/_episodes/04-pipefilter.md:341
	#: shell-novice/_episodes/04-pipefilter.md:484
	#: shell-novice/_episodes/04-pipefilter.md:605
	#: shell-novice/_episodes/04-pipefilter.md:642
	#: shell-novice/_episodes/04-pipefilter.md:667
	#: shell-novice/_episodes/04-pipefilter.md:703
	#: shell-novice/_episodes/04-pipefilter.md:734
	#: shell-novice/_episodes/04-pipefilter.md:861
	#: shell-novice/_episodes/04-pipefilter.md:885
	#: shell-novice/_episodes/05-loop.md:187 shell-novice/_episodes/05-loop.md:283
	#: shell-novice/_episodes/05-loop.md:607 shell-novice/_episodes/05-loop.md:634
	#: shell-novice/_episodes/05-loop.md:686 shell-novice/_episodes/05-loop.md:713
	#: shell-novice/_episodes/06-script.md:313
	#: shell-novice/_episodes/06-script.md:388
	#: shell-novice/_episodes/06-script.md:497
	#: shell-novice/_episodes/06-script.md:527
	#: shell-novice/_episodes/06-script.md:571
	#: shell-novice/_episodes/06-script.md:613
	#: shell-novice/_episodes/07-find.md:250 shell-novice/_episodes/07-find.md:339
	#: shell-novice/_episodes/07-find.md:383 shell-novice/_episodes/07-find.md:606
	#: shell-novice/_episodes/07-find.md:658 shell-novice/_episodes/07-find.md:680
	msgid "{: .challenge}"
	msgstr "{: .challenge}"
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:376
	msgid "> ## Listing Recursively and By Time"
	msgstr "> ## Listing Recursively and By Time"
	#: shell-novice/_episodes/02-filedir.md:377
	msgid ""
	">\n"
	"> The command `ls -R` lists the contents of directories recursively, i.e., lists\n"
	"> their sub-directories, sub-sub-directories, and so on at each level. The command\n"
	"> `ls -t` lists things by time of last change, with most recently changed files or\n"
	"> directories first.\n"
	"> In what order does `ls -R -t` display things? Hint: `ls -l` uses a long listing\n"
	"> format to view timestamps.\n"
	">\n"
	"> > ## Solution\n"
	"> > The files/directories in each directory are sorted by time of last change."
	msgstr ""
	">\n"
	"> The command `ls -R` lists the contents of directories recursively, i.e., lists\n"
	"> their sub-directories, sub-sub-directories, and so on at each level. The command\n"
	"> `ls -t` lists things by time of last change, with most recently changed files or\n"
	"> directories first.\n"
	"> In what order does `ls -R -t` display things? Hint: `ls -l` uses a long listing\n"
	"> format to view timestamps.\n"
	">\n"
	"> > ## Solution\n"
	"> > The files/directories in each directory are sorted by time of last change."
	#: shell-novice/_episodes/02-filedir.md:390
	msgid ""
	"Here,\n"
	"we can see that our home directory contains mostly **sub-directories**.\n"
	"Any names in your output that don't have trailing slashes,\n"
	"are plain old **files**.\n"
	"And note that there is a space between `ls` and `-F`:\n"
	"without it,\n"
	"the shell thinks we're trying to run a command called `ls-F`,\n"
	"which doesn't exist."
	msgstr ""
	"Here,\n"
	"we can see that our home directory contains mostly **sub-directories**.\n"
	"Any names in your output that don't have trailing slashes,\n"
	"are plain old **files**.\n"
	"And note that there is a space between `ls` and `-F`:\n"
	"without it,\n"
	"the shell thinks we're trying to run a command called `ls-F`,\n"
	"which doesn't exist."
	#: shell-novice/_episodes/02-filedir.md:399
	msgid ""
	"We can also use `ls` to see the contents of a different directory. Let's take a\n"
	"look at our `Desktop` directory by running `ls -F Desktop`,\n"
	"i.e.,\n"
	"the command `ls` with the `-F` **flag** and the **argument** `Desktop`.\n"
	"The argument `Desktop` tells `ls` that\n"
	"we want a listing of something other than our current working directory:"
	msgstr ""
	"We can also use `ls` to see the contents of a different directory. Let's take a\n"
	"look at our `Desktop` directory by running `ls -F Desktop`,\n"
	"i.e.,\n"
	"the command `ls` with the `-F` **flag** and the **argument** `Desktop`.\n"
	"The argument `Desktop` tells `ls` that\n"
	"we want a listing of something other than our current working directory:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:406
	msgid ""
	"~~~\n"
	"$ ls -F Desktop\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls -F Desktop\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:411
	msgid ""
	"~~~\n"
	"data-shell/\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"data-shell/\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:416
	msgid ""
	"Your output should be a list of all the files and sub-directories on your\n"
	"Desktop, including the `data-shell` directory you downloaded at\n"
	"the start of the lesson. Take a look at your Desktop to confirm that\n"
	"your output is accurate. "
	msgstr ""
	"Your output should be a list of all the files and sub-directories on your\n"
	"Desktop, including the `data-shell` directory you downloaded at\n"
	"the start of the lesson. Take a look at your Desktop to confirm that\n"
	"your output is accurate. "
	#: shell-novice/_episodes/02-filedir.md:421
	msgid ""
	"As you may now see, using a bash shell is strongly dependent on the idea that\n"
	"your files are organized in a hierarchical file system.\n"
	"Organizing things hierarchically in this way helps us keep track of our work:\n"
	"it's possible to put hundreds of files in our home directory,\n"
	"just as it's possible to pile hundreds of printed papers on our desk,\n"
	"but it's a self-defeating strategy."
	msgstr ""
	"As you may now see, using a bash shell is strongly dependent on the idea that\n"
	"your files are organized in a hierarchical file system.\n"
	"Organizing things hierarchically in this way helps us keep track of our work:\n"
	"it's possible to put hundreds of files in our home directory,\n"
	"just as it's possible to pile hundreds of printed papers on our desk,\n"
	"but it's a self-defeating strategy."
	#: shell-novice/_episodes/02-filedir.md:428
	msgid ""
	"Now that we know the `data-shell` directory is located on our Desktop, we\n"
	"can do two things. "
	msgstr ""
	"Now that we know the `data-shell` directory is located on our Desktop, we\n"
	"can do two things. "
	#: shell-novice/_episodes/02-filedir.md:431
	msgid ""
	"First, we can look at its contents, using the same strategy as before, passing\n"
	"a directory name to `ls`:"
	msgstr ""
	"First, we can look at its contents, using the same strategy as before, passing\n"
	"a directory name to `ls`:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:434
	msgid ""
	"~~~\n"
	"$ ls -F Desktop/data-shell\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls -F Desktop/data-shell\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:439
	msgid ""
	"~~~\n"
	"creatures/ molecules/ notes.txt solar.pdf\n"
	"data/ north-pacific-gyre/ pizza.cfg writing/\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"creatures/ molecules/ notes.txt solar.pdf\n"
	"data/ north-pacific-gyre/ pizza.cfg writing/\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:445
	msgid ""
	"Second, we can actually change our location to a different directory, so\n"
	"we are no longer located in\n"
	"our home directory. "
	msgstr ""
	"Second, we can actually change our location to a different directory, so\n"
	"we are no longer located in\n"
	"our home directory. "
	#: shell-novice/_episodes/02-filedir.md:449
	msgid ""
	"The command to change locations is `cd` followed by a\n"
	"directory name to change our working directory.\n"
	"`cd` stands for \"change directory\",\n"
	"which is a bit misleading:\n"
	"the command doesn't change the directory,\n"
	"it changes the shell's idea of what directory we are in."
	msgstr ""
	"The command to change locations is `cd` followed by a\n"
	"directory name to change our working directory.\n"
	"`cd` stands for \"change directory\",\n"
	"which is a bit misleading:\n"
	"the command doesn't change the directory,\n"
	"it changes the shell's idea of what directory we are in."
	#: shell-novice/_episodes/02-filedir.md:456
	msgid ""
	"Let's say we want to move to the `data` directory we saw above. We can\n"
	"use the following series of commands to get there:"
	msgstr ""
	"Let's say we want to move to the `data` directory we saw above. We can\n"
	"use the following series of commands to get there:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:459
	msgid ""
	"~~~\n"
	"$ cd Desktop\n"
	"$ cd data-shell\n"
	"$ cd data\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ cd Desktop\n"
	"$ cd data-shell\n"
	"$ cd data\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:466
	msgid ""
	"These commands will move us from our home directory onto our Desktop, then into\n"
	"the `data-shell` directory, then into the `data` directory. `cd` doesn't print anything,\n"
	"but if we run `pwd` after it, we can see that we are now\n"
	"in `/Users/nelle/Desktop/data-shell/data`.\n"
	"If we run `ls` without arguments now,\n"
	"it lists the contents of `/Users/nelle/Desktop/data-shell/data`,\n"
	"because that's where we now are:"
	msgstr ""
	"These commands will move us from our home directory onto our Desktop, then into\n"
	"the `data-shell` directory, then into the `data` directory. `cd` doesn't print anything,\n"
	"but if we run `pwd` after it, we can see that we are now\n"
	"in `/Users/nelle/Desktop/data-shell/data`.\n"
	"If we run `ls` without arguments now,\n"
	"it lists the contents of `/Users/nelle/Desktop/data-shell/data`,\n"
	"because that's where we now are:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:479
	#: shell-novice/_episodes/02-filedir.md:652
	msgid ""
	"~~~\n"
	"/Users/nelle/Desktop/data-shell/data\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"/Users/nelle/Desktop/data-shell/data\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:489
	msgid ""
	"~~~\n"
	"amino-acids.txt elements/ pdb/\t salmon.txt\n"
	"animals.txt morse.txt planets.txt sunspot.txt\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"amino-acids.txt elements/ pdb/\t salmon.txt\n"
	"animals.txt morse.txt planets.txt sunspot.txt\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:495
	msgid ""
	"We now know how to go down the directory tree, but\n"
	"how do we go up? We might try the following:"
	msgstr ""
	"We now know how to go down the directory tree, but\n"
	"how do we go up? We might try the following:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:498
	msgid ""
	"~~~\n"
	"$ cd data-shell\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ cd data-shell\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:503
	msgid ""
	"~~~\n"
	"-bash: cd: data-shell: No such file or directory\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"-bash: cd: data-shell: No such file or directory\n"
	"~~~"
	# SC/DC Template label
	#: shell-novice/_episodes/02-filedir.md:506
	#: shell-novice/_episodes/03-create.md:299
	#: shell-novice/_episodes/03-create.md:505 shell-novice/_episodes/05-loop.md:53
	msgid "{: .error}"
	msgstr "{: .error}"
	#: shell-novice/_episodes/02-filedir.md:508
	msgid "But we get an error! Why is this? "
	msgstr "But we get an error! Why is this? "
	#: shell-novice/_episodes/02-filedir.md:510
	msgid ""
	"With our methods so far,\n"
	"`cd` can only see sub-directories inside your current directory. There are\n"
	"different ways to see directories above your current location; we'll start\n"
	"with the simplest. "
	msgstr ""
	"With our methods so far,\n"
	"`cd` can only see sub-directories inside your current directory. There are\n"
	"different ways to see directories above your current location; we'll start\n"
	"with the simplest. "
	#: shell-novice/_episodes/02-filedir.md:515
	msgid ""
	"There is a shortcut in the shell to move up one directory level\n"
	"that looks like this:"
	msgstr ""
	"There is a shortcut in the shell to move up one directory level\n"
	"that looks like this:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:518
	#: shell-novice/_episodes/03-create.md:283
	msgid ""
	"~~~\n"
	"$ cd ..\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ cd ..\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:523
	msgid ""
	"`..` is a special directory name meaning\n"
	"\"the directory containing this one\",\n"
	"or more succinctly,\n"
	"the **parent** of the current directory.\n"
	"Sure enough,\n"
	"if we run `pwd` after running `cd ..`, we're back in `/Users/nelle/Desktop/data-shell`:"
	msgstr ""
	"`..` is a special directory name meaning\n"
	"\"the directory containing this one\",\n"
	"or more succinctly,\n"
	"the **parent** of the current directory.\n"
	"Sure enough,\n"
	"if we run `pwd` after running `cd ..`, we're back in `/Users/nelle/Desktop/data-shell`:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:535
	#: shell-novice/_episodes/03-create.md:32
	#: shell-novice/_episodes/03-create.md:355
	msgid ""
	"~~~\n"
	"/Users/nelle/Desktop/data-shell\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"/Users/nelle/Desktop/data-shell\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:540
	msgid ""
	"The special directory `..` doesn't usually show up when we run `ls`. If we want\n"
	"to display it, we can give `ls` the `-a` flag:"
	msgstr ""
	"The special directory `..` doesn't usually show up when we run `ls`. If we want\n"
	"to display it, we can give `ls` the `-a` flag:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:543
	msgid ""
	"~~~\n"
	"$ ls -F -a\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls -F -a\n"
	"~~~"
	# code block
	#: shell-novice/_episodes/02-filedir.md:548
	msgid ""
	"~~~\n"
	"./ .bash_profile data/ north-pacific-gyre/ pizza.cfg thesis/\n"
	"../ creatures/ molecules/ notes.txt solar.pdf writing/\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"./ .bash_profile data/ north-pacific-gyre/ pizza.cfg thesis/\n"
	"../ creatures/ molecules/ notes.txt solar.pdf writing/\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:554
	msgid ""
	"`-a` stands for \"show all\";\n"
	"it forces `ls` to show us file and directory names that begin with `.`,\n"
	"such as `..` (which, if we're in `/Users/nelle`, refers to the `/Users` directory)\n"
	"As you can see,\n"
	"it also displays another special directory that's just called `.`,\n"
	"which means \"the current working directory\".\n"
	"It may seem redundant to have a name for it,\n"
	"but we'll see some uses for it soon."
	msgstr ""
	"`-a` stands for \"show all\";\n"
	"it forces `ls` to show us file and directory names that begin with `.`,\n"
	"such as `..` (which, if we're in `/Users/nelle`, refers to the `/Users` directory)\n"
	"As you can see,\n"
	"it also displays another special directory that's just called `.`,\n"
	"which means \"the current working directory\".\n"
	"It may seem redundant to have a name for it,\n"
	"but we'll see some uses for it soon."
	#: shell-novice/_episodes/02-filedir.md:563
	msgid ""
	"Note that in most command line tools, multiple flags can be combined \n"
	"with a single `-` and no spaces between the flags: `ls -F -a` is \n"
	"equivalent to `ls -Fa`."
	msgstr ""
	"Note that in most command line tools, multiple flags can be combined \n"
	"with a single `-` and no spaces between the flags: `ls -F -a` is \n"
	"equivalent to `ls -Fa`."
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:567
	msgid "> ## Other Hidden Files"
	msgstr "> ## Other Hidden Files"
	#: shell-novice/_episodes/02-filedir.md:568
	msgid ""
	">\n"
	"> In addition to the hidden directories `..` and `.`, you may also see a file\n"
	"> called `.bash_profile`. This file usually contains shell configuration\n"
	"> settings. You may also see other files and directories beginning\n"
	"> with `.`. These are usually files and directories that are used to configure\n"
	"> different programs on your computer. The prefix `.` is used to prevent these\n"
	"> configuration files from cluttering the terminal when a standard `ls` command\n"
	"> is used."
	msgstr ""
	">\n"
	"> In addition to the hidden directories `..` and `.`, you may also see a file\n"
	"> called `.bash_profile`. This file usually contains shell configuration\n"
	"> settings. You may also see other files and directories beginning\n"
	"> with `.`. These are usually files and directories that are used to configure\n"
	"> different programs on your computer. The prefix `.` is used to prevent these\n"
	"> configuration files from cluttering the terminal when a standard `ls` command\n"
	"> is used."
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:578
	msgid "> ## Orthogonality"
	msgstr "> ## Orthogonality"
	#: shell-novice/_episodes/02-filedir.md:579
	msgid ""
	">\n"
	"> The special names `.` and `..` don't belong to `cd`;\n"
	"> they are interpreted the same way by every program.\n"
	"> For example,\n"
	"> if we are in `/Users/nelle/data`,\n"
	"> the command `ls ..` will give us a listing of `/Users/nelle`.\n"
	"> When the meanings of the parts are the same no matter how they're combined,\n"
	"> programmers say they are **orthogonal**:\n"
	"> Orthogonal systems tend to be easier for people to learn\n"
	"> because there are fewer special cases and exceptions to keep track of."
	msgstr ""
	">\n"
	"> The special names `.` and `..` don't belong to `cd`;\n"
	"> they are interpreted the same way by every program.\n"
	"> For example,\n"
	"> if we are in `/Users/nelle/data`,\n"
	"> the command `ls ..` will give us a listing of `/Users/nelle`.\n"
	"> When the meanings of the parts are the same no matter how they're combined,\n"
	"> programmers say they are **orthogonal**:\n"
	"> Orthogonal systems tend to be easier for people to learn\n"
	"> because there are fewer special cases and exceptions to keep track of."
	#: shell-novice/_episodes/02-filedir.md:591
	msgid ""
	"These then, are the basic commands for navigating the filesystem on your computer:\n"
	"`pwd`, `ls` and `cd`. Let's explore some variations on those commands. What happens\n"
	"if you type `cd` on its own, without giving\n"
	"a directory? "
	msgstr ""
	"These then, are the basic commands for navigating the filesystem on your computer:\n"
	"`pwd`, `ls` and `cd`. Let's explore some variations on those commands. What happens\n"
	"if you type `cd` on its own, without giving\n"
	"a directory? "
	# code block
	#: shell-novice/_episodes/02-filedir.md:596
	msgid ""
	"~~~\n"
	"$ cd\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ cd\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:601
	msgid "How can you check what happened? `pwd` gives us the answer! "
	msgstr "How can you check what happened? `pwd` gives us the answer! "
	#: shell-novice/_episodes/02-filedir.md:613
	msgid ""
	"It turns out that `cd` without an argument will return you to your home directory,\n"
	"which is great if you've gotten lost in your own filesystem. "
	msgstr ""
	"It turns out that `cd` without an argument will return you to your home directory,\n"
	"which is great if you've gotten lost in your own filesystem. "
	#: shell-novice/_episodes/02-filedir.md:616
	msgid ""
	"Let's try returning to the `data` directory from before. Last time, we used\n"
	"three commands, but we can actually string together the list of directories\n"
	"to move to `data` in one step:"
	msgstr ""
	"Let's try returning to the `data` directory from before. Last time, we used\n"
	"three commands, but we can actually string together the list of directories\n"
	"to move to `data` in one step:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:620
	msgid ""
	"~~~\n"
	"$ cd Desktop/data-shell/data\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ cd Desktop/data-shell/data\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:625
	msgid "Check that we've moved to the right place by running `pwd` and `ls -F` "
	msgstr "Check that we've moved to the right place by running `pwd` and `ls -F` "
	#: shell-novice/_episodes/02-filedir.md:627
	msgid ""
	"If we want to move up one level from the data directory, we could use `cd ..`. But\n"
	"there is another way to move to any directory, regardless of your\n"
	"current location. "
	msgstr ""
	"If we want to move up one level from the data directory, we could use `cd ..`. But\n"
	"there is another way to move to any directory, regardless of your\n"
	"current location. "
	#: shell-novice/_episodes/02-filedir.md:631
	msgid ""
	"So far, when specifying directory names, or even a directory path (as above),\n"
	"we have been using **relative paths**. When you use a relative path with a command\n"
	"like `ls` or `cd`, it tries to find that location from where we are,\n"
	"rather than from the root of the file system. "
	msgstr ""
	"So far, when specifying directory names, or even a directory path (as above),\n"
	"we have been using **relative paths**. When you use a relative path with a command\n"
	"like `ls` or `cd`, it tries to find that location from where we are,\n"
	"rather than from the root of the file system. "
	#: shell-novice/_episodes/02-filedir.md:636
	msgid ""
	"However, it is possible to specify the **absolute path** to a directory by\n"
	"including its entire path from the root directory, which is indicated by a\n"
	"leading slash. The leading `/` tells the computer to follow the path from\n"
	"the root of the file system, so it always refers to exactly one directory,\n"
	"no matter where we are when we run the command."
	msgstr ""
	"However, it is possible to specify the **absolute path** to a directory by\n"
	"including its entire path from the root directory, which is indicated by a\n"
	"leading slash. The leading `/` tells the computer to follow the path from\n"
	"the root of the file system, so it always refers to exactly one directory,\n"
	"no matter where we are when we run the command."
	#: shell-novice/_episodes/02-filedir.md:642
	msgid ""
	"This allows us to move to our `data-shell` directory from anywhere on\n"
	"the filesystem (including from inside `data`). To find the absolute path\n"
	"we're looking for, we can use `pwd` and then extract the piece we need\n"
	"to move to `data-shell`. "
	msgstr ""
	"This allows us to move to our `data-shell` directory from anywhere on\n"
	"the filesystem (including from inside `data`). To find the absolute path\n"
	"we're looking for, we can use `pwd` and then extract the piece we need\n"
	"to move to `data-shell`. "
	# code block
	#: shell-novice/_episodes/02-filedir.md:657
	msgid ""
	"~~~\n"
	"$ cd /Users/nelle/Desktop/data-shell\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ cd /Users/nelle/Desktop/data-shell\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:662
	msgid "Run `pwd` and `ls -F` to ensure that we're in the directory we expect. "
	msgstr "Run `pwd` and `ls -F` to ensure that we're in the directory we expect. "
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:664
	msgid "> ## Two More Shortcuts"
	msgstr "> ## Two More Shortcuts"
	#: shell-novice/_episodes/02-filedir.md:665
	msgid ""
	">\n"
	"> The shell interprets the character `~` (tilde) at the start of a path to\n"
	"> mean \"the current user's home directory\". For example, if Nelle's home\n"
	"> directory is `/Users/nelle`, then `~/data` is equivalent to\n"
	"> `/Users/nelle/data`. This only works if it is the first character in the\n"
	"> path: `here/there/~/elsewhere` is *not* `here/there/Users/nelle/elsewhere`.\n"
	">\n"
	"> Another shortcut is the `-` (dash) character. `cd` will translate `-` into\n"
	"> *the previous directory I was in*, which is faster than having to remember,\n"
	"> then type, the full path. This is a *very* efficient way of moving back\n"
	"> and forth between directories. The difference between `cd ..` and `cd -` is\n"
	"> that the former brings you *up*, while the latter brings you *back*. You can\n"
	"> think of it as the *Last Channel* button on a TV remote."
	msgstr ""
	">\n"
	"> The shell interprets the character `~` (tilde) at the start of a path to\n"
	"> mean \"the current user's home directory\". For example, if Nelle's home\n"
	"> directory is `/Users/nelle`, then `~/data` is equivalent to\n"
	"> `/Users/nelle/data`. This only works if it is the first character in the\n"
	"> path: `here/there/~/elsewhere` is *not* `here/there/Users/nelle/elsewhere`.\n"
	">\n"
	"> Another shortcut is the `-` (dash) character. `cd` will translate `-` into\n"
	"> *the previous directory I was in*, which is faster than having to remember,\n"
	"> then type, the full path. This is a *very* efficient way of moving back\n"
	"> and forth between directories. The difference between `cd ..` and `cd -` is\n"
	"> that the former brings you *up*, while the latter brings you *back*. You can\n"
	"> think of it as the *Last Channel* button on a TV remote."
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:680
	msgid "> ## Absolute vs Relative Paths"
	msgstr "> ## Absolute vs Relative Paths"
	#: shell-novice/_episodes/02-filedir.md:681
	msgid ""
	">\n"
	"> Starting from `/Users/amanda/data/`,\n"
	"> which of the following commands could Amanda use to navigate to her home directory,\n"
	"> which is `/Users/amanda`?\n"
	">\n"
	"> 1. `cd .`\n"
	"> 2. `cd /`\n"
	"> 3. `cd /home/amanda`\n"
	"> 4. `cd ../..`\n"
	"> 5. `cd ~`\n"
	"> 6. `cd home`\n"
	"> 7. `cd ~/data/..`\n"
	"> 8. `cd`\n"
	"> 9. `cd ..`\n"
	">\n"
	"> > ## Solution\n"
	"> > 1. No: `.` stands for the current directory.\n"
	"> > 2. No: `/` stands for the root directory.\n"
	"> > 3. No: Amanda's home directory is `/Users/amanda`.\n"
	"> > 4. No: this goes up two levels, i.e. ends in `/Users`.\n"
	"> > 5. Yes: `~` stands for the user's home directory, in this case `/Users/amanda`.\n"
	"> > 6. No: this would navigate into a directory `home` in the current directory if it exists.\n"
	"> > 7. Yes: unnecessarily complicated, but correct.\n"
	"> > 8. Yes: shortcut to go back to the user's home directory.\n"
	"> > 9. Yes: goes up one level."
	msgstr ""
	">\n"
	"> Starting from `/Users/amanda/data/`,\n"
	"> which of the following commands could Amanda use to navigate to her home directory,\n"
	"> which is `/Users/amanda`?\n"
	">\n"
	"> 1. `cd .`\n"
	"> 2. `cd /`\n"
	"> 3. `cd /home/amanda`\n"
	"> 4. `cd ../..`\n"
	"> 5. `cd ~`\n"
	"> 6. `cd home`\n"
	"> 7. `cd ~/data/..`\n"
	"> 8. `cd`\n"
	"> 9. `cd ..`\n"
	">\n"
	"> > ## Solution\n"
	"> > 1. No: `.` stands for the current directory.\n"
	"> > 2. No: `/` stands for the root directory.\n"
	"> > 3. No: Amanda's home directory is `/Users/amanda`.\n"
	"> > 4. No: this goes up two levels, i.e. ends in `/Users`.\n"
	"> > 5. Yes: `~` stands for the user's home directory, in this case `/Users/amanda`.\n"
	"> > 6. No: this would navigate into a directory `home` in the current directory if it exists.\n"
	"> > 7. Yes: unnecessarily complicated, but correct.\n"
	"> > 8. Yes: shortcut to go back to the user's home directory.\n"
	"> > 9. Yes: goes up one level."
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:709
	msgid "> ## Relative Path Resolution"
	msgstr "> ## Relative Path Resolution"
	#: shell-novice/_episodes/02-filedir.md:710
	msgid ""
	">\n"
	"> Using the filesystem diagram below, if `pwd` displays `/Users/thing`,\n"
	"> what will `ls -F ../backup` display?\n"
	">\n"
	"> 1. `../backup: No such file or directory`\n"
	"> 2. `2012-12-01 2013-01-08 2013-01-27`\n"
	"> 3. `2012-12-01/ 2013-01-08/ 2013-01-27/`\n"
	"> 4. `original/ pnas_final/ pnas_sub/`\n"
	">\n"
	"> \n"
	">\n"
	"> > ## Solution\n"
	"> > 1. No: there *is* a directory `backup` in `/Users`.\n"
	"> > 2. No: this is the content of `Users/thing/backup`,\n"
	"> > but with `..` we asked for one level further up.\n"
	"> > 3. No: see previous explanation.\n"
	"> > 4. Yes: `../backup/` refers to `/Users/backup/`."
	msgstr ""
	">\n"
	"> Using the filesystem diagram below, if `pwd` displays `/Users/thing`,\n"
	"> what will `ls -F ../backup` display?\n"
	">\n"
	"> 1. `../backup: No such file or directory`\n"
	"> 2. `2012-12-01 2013-01-08 2013-01-27`\n"
	"> 3. `2012-12-01/ 2013-01-08/ 2013-01-27/`\n"
	"> 4. `original/ pnas_final/ pnas_sub/`\n"
	">\n"
	"> \n"
	">\n"
	"> > ## Solution\n"
	"> > 1. No: there *is* a directory `backup` in `/Users`.\n"
	"> > 2. No: this is the content of `Users/thing/backup`,\n"
	"> > but with `..` we asked for one level further up.\n"
	"> > 3. No: see previous explanation.\n"
	"> > 4. Yes: `../backup/` refers to `/Users/backup/`."
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:730
	msgid "> ## `ls` Reading Comprehension"
	msgstr "> ## `ls` Reading Comprehension"
	#: shell-novice/_episodes/02-filedir.md:731
	msgid ""
	">\n"
	"> Assuming a directory structure as in the above Figure\n"
	"> (File System for Challenge Questions), if `pwd` displays `/Users/backup`,\n"
	"> and `-r` tells `ls` to display things in reverse order,\n"
	"> what command will display:\n"
	">\n"
	"> ~~~\n"
	"> pnas_sub/ pnas_final/ original/\n"
	"> ~~~"
	msgstr ""
	">\n"
	"> Assuming a directory structure as in the above Figure\n"
	"> (File System for Challenge Questions), if `pwd` displays `/Users/backup`,\n"
	"> and `-r` tells `ls` to display things in reverse order,\n"
	"> what command will display:\n"
	">\n"
	"> ~~~\n"
	"> pnas_sub/ pnas_final/ original/\n"
	"> ~~~"
	# SC/DC Template label
	#: shell-novice/_episodes/02-filedir.md:740
	#: shell-novice/_episodes/03-create.md:569
	#: shell-novice/_episodes/03-create.md:577
	#: shell-novice/_episodes/03-create.md:619
	#: shell-novice/_episodes/03-create.md:632
	#: shell-novice/_episodes/03-create.md:640
	#: shell-novice/_episodes/03-create.md:674
	#: shell-novice/_episodes/04-pipefilter.md:323
	#: shell-novice/_episodes/04-pipefilter.md:334
	#: shell-novice/_episodes/04-pipefilter.md:630
	#: shell-novice/_episodes/04-pipefilter.md:691
	#: shell-novice/_episodes/04-pipefilter.md:716
	#: shell-novice/_episodes/05-loop.md:124 shell-novice/_episodes/05-loop.md:369
	#: shell-novice/_episodes/05-loop.md:559 shell-novice/_episodes/07-find.md:239
	#: shell-novice/_episodes/07-find.md:272
	msgid "> {: .output}"
	msgstr "> {: .output}"
	#: shell-novice/_episodes/02-filedir.md:741
	msgid ""
	">\n"
	"> 1. `ls pwd`\n"
	"> 2. `ls -r -F`\n"
	"> 3. `ls -r -F /Users/backup`\n"
	"> 4. Either #2 or #3 above, but not #1.\n"
	">\n"
	"> > ## Solution\n"
	"> > 1. No: `pwd` is not the name of a directory.\n"
	"> > 2. Yes: `ls` without directory argument lists files and directories\n"
	"> > in the current directory.\n"
	"> > 3. Yes: uses the absolute path explicitly.\n"
	"> > 4. Correct: see explanations above."
	msgstr ""
	">\n"
	"> 1. `ls pwd`\n"
	"> 2. `ls -r -F`\n"
	"> 3. `ls -r -F /Users/backup`\n"
	"> 4. Either #2 or #3 above, but not #1.\n"
	">\n"
	"> > ## Solution\n"
	"> > 1. No: `pwd` is not the name of a directory.\n"
	"> > 2. Yes: `ls` without directory argument lists files and directories\n"
	"> > in the current directory.\n"
	"> > 3. Yes: uses the absolute path explicitly.\n"
	"> > 4. Correct: see explanations above."
	# header
	#: shell-novice/_episodes/02-filedir.md:756
	msgid "### Nelle's Pipeline: Organizing Files"
	msgstr "### Nelle's Pipeline: Organizing Files"
	#: shell-novice/_episodes/02-filedir.md:758
	msgid ""
	"Knowing just this much about files and directories,\n"
	"Nelle is ready to organize the files that the protein assay machine will create.\n"
	"First,\n"
	"she creates a directory called `north-pacific-gyre`\n"
	"(to remind herself where the data came from).\n"
	"Inside that,\n"
	"she creates a directory called `2012-07-03`,\n"
	"which is the date she started processing the samples.\n"
	"She used to use names like `conference-paper` and `revised-results`,\n"
	"but she found them hard to understand after a couple of years.\n"
	"(The final straw was when she found herself creating\n"
	"a directory called `revised-revised-results-3`.)"
	msgstr ""
	"Knowing just this much about files and directories,\n"
	"Nelle is ready to organize the files that the protein assay machine will create.\n"
	"First,\n"
	"she creates a directory called `north-pacific-gyre`\n"
	"(to remind herself where the data came from).\n"
	"Inside that,\n"
	"she creates a directory called `2012-07-03`,\n"
	"which is the date she started processing the samples.\n"
	"She used to use names like `conference-paper` and `revised-results`,\n"
	"but she found them hard to understand after a couple of years.\n"
	"(The final straw was when she found herself creating\n"
	"a directory called `revised-revised-results-3`.)"
	# blockquote, which can be cascaded
	#: shell-novice/_episodes/02-filedir.md:771
	msgid "> ## Sorting Output"
	msgstr "> ## Sorting Output"
	#: shell-novice/_episodes/02-filedir.md:772
	msgid ""
	">\n"
	"> Nelle names her directories \"year-month-day\",\n"
	"> with leading zeroes for months and days,\n"
	"> because the shell displays file and directory names in alphabetical order.\n"
	"> If she used month names,\n"
	"> December would come before July;\n"
	"> if she didn't use leading zeroes,\n"
	"> November ('11') would come before July ('7'). Similarly, putting the year first\n"
	"> means that June 2012 will come before June 2013."
	msgstr ""
	">\n"
	"> Nelle names her directories \"year-month-day\",\n"
	"> with leading zeroes for months and days,\n"
	"> because the shell displays file and directory names in alphabetical order.\n"
	"> If she used month names,\n"
	"> December would come before July;\n"
	"> if she didn't use leading zeroes,\n"
	"> November ('11') would come before July ('7'). Similarly, putting the year first\n"
	"> means that June 2012 will come before June 2013."
	#: shell-novice/_episodes/02-filedir.md:783
	msgid ""
	"Each of her physical samples is labelled according to her lab's convention\n"
	"with a unique ten-character ID,\n"
	"such as \"NENE01729A\".\n"
	"This is what she used in her collection log\n"
	"to record the location, time, depth, and other characteristics of the sample,\n"
	"so she decides to use it as part of each data file's name.\n"
	"Since the assay machine's output is plain text,\n"
	"she will call her files `NENE01729A.txt`, `NENE01812A.txt`, and so on.\n"
	"All 1520 files will go into the same directory."
	msgstr ""
	"Each of her physical samples is labelled according to her lab's convention\n"
	"with a unique ten-character ID,\n"
	"such as \"NENE01729A\".\n"
	"This is what she used in her collection log\n"
	"to record the location, time, depth, and other characteristics of the sample,\n"
	"so she decides to use it as part of each data file's name.\n"
	"Since the assay machine's output is plain text,\n"
	"she will call her files `NENE01729A.txt`, `NENE01812A.txt`, and so on.\n"
	"All 1520 files will go into the same directory."
	#: shell-novice/_episodes/02-filedir.md:793
	msgid ""
	"Now in her current directory `data-shell`,\n"
	"Nelle can see what files she has using the command:"
	msgstr ""
	"Now in her current directory `data-shell`,\n"
	"Nelle can see what files she has using the command:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:796
	msgid ""
	"~~~\n"
	"$ ls north-pacific-gyre/2012-07-03/\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls north-pacific-gyre/2012-07-03/\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:801
	msgid ""
	"This is a lot to type,\n"
	"but she can let the shell do most of the work through what is called **tab completion**.\n"
	"If she types:"
	msgstr ""
	"This is a lot to type,\n"
	"but she can let the shell do most of the work through what is called **tab completion**.\n"
	"If she types:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:805
	msgid ""
	"~~~\n"
	"$ ls nor\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls nor\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:810
	msgid ""
	"and then presses tab (the tab key on her keyboard),\n"
	"the shell automatically completes the directory name for her:"
	msgstr ""
	"and then presses tab (the tab key on her keyboard),\n"
	"the shell automatically completes the directory name for her:"
	# code block
	#: shell-novice/_episodes/02-filedir.md:813
	msgid ""
	"~~~\n"
	"$ ls north-pacific-gyre/\n"
	"~~~"
	msgstr ""
	"~~~\n"
	"$ ls north-pacific-gyre/\n"
	"~~~"
	#: shell-novice/_episodes/02-filedir.md:818
	msgid ""
	"If she presses tab again,\n"
	"Bash will add `2012-07-03/` to the command,\n"
	"since it's the only possible completion.\n"
	"Pressing tab again does nothing,\n"
	"since there are 19 possibilities;\n"
	"pressing tab twice brings up a list of all the files,\n"
	"and so on.\n"
	"This is called **tab completion**,\n"
	"and we will see it in many other tools as we go on."
	msgstr ""
	"If she presses tab again,\n"
	"Bash will add `2012-07-03/` to the command,\n"
	"since it's the only possible completion.\n"
	"Pressing tab again does nothing,\n"
	"since there are 19 possibilities;\n"
	"pressing tab twice brings up a list of all the files,\n"
	"and so on.\n"
	"This is called **tab completion**,\n"
	"and we will see it in many other tools as we go on."