"Next up" in http://guide.bash.academy/commands/# incorrectly links to "Tests And Conditionals" instead of "Variables and Expansions".

Observed Issue: I have just completed reading chapter 3 (Variables and Expansions) (http://guide.bash.academy/03.variables.html#) and clicked the Next Up link to start chapter 4 (Tests and Conditionals) (http://guide.bash.academy/04.conditionals.html) but the page only loaded the the header section with a pound sign and what looks like a number 1 (#1)displaying where the normal content would be. I clicked on other chapters from the menu, only the home page and Chapter 1 through 3 loaded correctly.
In order to rule out a browser issue (Using Chrome Version 49.0.2623.75 beta-m (64-bit)), I also tried loading the pages with Firefox, IE and Edge. All failed.
In order to eliminate network issues, I remote connected to an off network computer and tested with Chrome, IE and Edge. All failed.

Desired Results: Having completed reading chapter 3 and clicking on the Next Up link, the content from chapter 4 should properly load. Other chapters should also load correctly in all popular internet browsers.

Steps to recreate:
1: load the Bash Guide: http://guide.bash.academy/
2: Complete chapters 1, 2 and 3 (optional I guess)
3: Try to load chapter 4 (or 5, 6, 7, 8, 9, 10 or 11)

Browsers used:
Chrome v49.0.2636.75 beta-m (64-bit)
Firefox 44.0.2
IE 11.0.9600.17801
Remote System
Chrome v48.0.2564.116 m
IE 11.103.10586.0
Edge 25.10586.0.0

Hey awesome people,
i really love the way that site teaches you Bash, and i would love to recommend it to my fellow students, but it seems that the project wont be finished. I just wanted to know if you are abandoning this project or if there are plans to complete the guide? I would love to help, but i dont know much about bash (thats how i found it, i searched for a good guide and i was struck because of how good the first chapters are). Nevertheless, I'm part of the students council at my University so i would definitely make it more public & recommend it once its finished

Cheers

I want to get the original jekyll repo and translate it into chinese fully . I hope to get your authorization

I was reading this paragraph and have a question:

Notice how in this session, we started out by giving bash the command to start the ex file editor. After issuing this command, our prompt changed: any text we enter now is sent to ex, not to bash. While ex is running, bash is aslumber waiting for your ex session to end.

While bash is in the background, does it take the typed text (the standard input stream from the terminal?) and then "forward" the text to the text editor? Or does bash somehow take itself out of the equation entirely, leaving the text editor to receive standard input directly from the terminal?

I'm a little fuzzy on the mechanics. How does <C-z> (i.e. suspend) work?

PS: This website is great!

In the 'Commands and Arguments' section, I would recommend replacing the two instances of the phrase 'gross part' with 'majority'. At least in North American English, 'gross part' isn't common usage. 'Gross' is far more commonly used as a synonym for 'disgusting' rather than as a term of measure.

https://guide.bash.academy/inception/#toc4
"FreeBSD users can use ports, Windows users can use cygwin, while Windows 10 integrates the Linux Bash Shell natively, but there are alternative distributions."

Tried to edit within website, but received error message. Hence, placing here.

I find the code style much harder to read then the surrounding text with my glasses off. It seems that the current style is:

1. Too thin. I doubt what the point of 'Source Code Pro Light' for all the code while using regular weight for the text is.
2. Low-contrast. The syntax block in 02 gives a 999-ddd fg-bg color combination, which is some 2.1:1 contrast value. Although moving the mouse over the lines help, I would like to be able to correctly skim. With the Light font it looks worse. You can use http://webaim.org/resources/contrastchecker/ and http://contrastchecker.com/ to check for the rest.

syntax for pipelines: [time [-p]] [ ! ] command [ [|||&] command2 ... ] is a bit confusing. | or |& in the second part, seems like optional. Shall we update it with [time [-p]] [ ! ] command [ | or |& command2 ... ]?

I may have posted some other corrections in the wrong place for lhunath. Sorry about that. So, maybe repetitious;
On Managing a command's input and output using redirection, past participle of emit should be emitted (in 5 places): change 'emit' to 'emitted'.
Groeten vanuit Vlaanderen.

Chapter 4-11 have no content and there hasn't been work on the project for a while. Think it would be a useful resource if completed, here showing my interest.

Dear awesome people,

I would like to point that despite much important work done on this generous effort, it would be highly useful if it is released at some point.

Now i agree that it doesn't follows release schedule of some sort say bash etc, but still it will be useful for followers to know when an important section has been updated etc.

So IMHO please use releases even if they are not periodic atleast people would be able to know when its updated.

Many thanks.

The images for the bash processes contain curly quotes instead of "dumb" quotes used in code:

(Moved from lhunath/bash.academy#8 after being tricked by the fork-me link.)

The fact is that I don't know English well, but I really want to be helped with this bash language. I don't understand how I can rewrite it. Help me.
p.s. Russian

There hasn't been a commit in over 6 months. I hope that this project has not been abandoned..

I'm not sure why but when I ran the solution to exercise EXPAN 5 I got

$ echo "${greeting^}!"
-bash: !": event not found

However running

$ echo "${greeting^*}! "
Hello world!

is clearly fine. I'm running on scientific linux if that helps, I am happy to provide any other details that would be useful.

please remove the double quotes here

example:

X=$(ls) # no quotes needed here
echo $X # word splitting happens here
echo "$X" # see: embedded newlines...

I had to read this paragraph (source) multiple times before I understood what was actually going on.

It explains how the glob !(my)*.txt can match a file named myscript.txt. Because I am familiar with how regex works, I was able to figure out why that happens, but the explanation in that page actually threw me off at first.

Perhaps it can be reworded so that what happens is more instantly clear.

In the quoting literal section there is a warning box which has two examples, broken! and correct. But the broken! example looks broken because there is no space between /home/ and $username. So it is probably doing the same thing as the correct example .(i am new to bash so i might be wrong .)

How do you know I actually donated?
Also - I have few remarks about the Inception part - especially when we are learning about the file descriptors.

Hello,

Pages do not having any content save for the headers, starting with this chapter :
http://guide.bash.academy/04.conditionals.html#

Only this works
http://guide.bash.academy/

• https://raw.github.com/lhunath/guide.bash.academy/gh-pages/img/inception.jpg
• https://github.com/lhunath/guide.bash.academy/blob/gh-pages/img/variables.jpg

Two main issues:

1. The hover function is too responsive and irritating. I often use the cursor to track where I'm reading, so every new line it flashes up.
   In my opinion, it should be made click to open, or the hover time threshold increased.

2. The scrolling on the menu feels a bit off. When I'm scrolled at the bottom of the menu, it then scrolls the main window, which is fine. However, if I then want to scroll up again on the menu, it'll prioritise the main window before the menu window. The same happens in the other direction. I think it sometimes persists even if I open and close the menu again.