Tom Granot's questions

Consider the following directory structure, printed to the screen using ls -l "$dir" ($dir is a bash variable standing for some folder on the same server, a few levels up), on a remote Ubuntu server (more precisely, Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64)):

-rw-r--r-- 1 user group     12 Apr  2 12:34 FILE1
-rwxr--r-- 1 user group    287 Apr 23  2017 File_
-rw-r--r-- 1 user group      0 Apr 21  2017 file_1
-rw-r--r-- 1 user group    272 Apr  3 22:16 myFile
-rw-r--r-- 1 user group  47633 Apr 11 14:01 myFile.txt
-rw-r--r-- 1 user group  37030 Apr 11 14:16 myfile1
-rw-r--r-- 1 user group      0 Apr 11 21:23 nothing_here
-rw-r--r-- 1 user group      2 Apr 22  2017 small_file
-rwxr-x--- 1 user group 262529 Apr  8 15:31 story

This is coming from a MacBook, and using the built-in terminal and the out-of-the-box installation of ssh (OS X Version 10.13.3, as the terminal tells me).

Consider, in comparison, the same server accessed from a Windows machine running PuTTy release 0.70:

-rwxr--r-- 1 user group    287 Apr 23  2017 File_
-rw-r--r-- 1 user group      0 Apr 21  2017 file_1
-rw-r--r-- 1 user group     12 Apr  2 12:34 FILE1
-rw-r--r-- 1 user group    272 Apr  3 22:16 myFile
-rw-r--r-- 1 user group  37030 Apr 11 14:16 myfile1
-rw-r--r-- 1 user group  47633 Apr 11 14:01 myFile.txt
-rw-r--r-- 1 user group      0 Apr 11 21:23 nothing_here
-rw-r--r-- 1 user group      2 Apr 22  2017 small_file
-rwxr-x--- 1 user group 262529 Apr  8 15:31 story

Notice the different sorting of the first 6 files in each code block.

Considering that the commands are running on the server, and not on the client computers, one would expect no difference between the two outputs. What's the reason they're not identical, then?

Edit 1: As mentioned in the comments, I've checked and the Mac's terminal is set to xterm-256color while the Windows one is set to xterm. A quick change of the Mac's setting to xterm had no effect.

Edit 2: As mentioned in the comments, I've tried running whereis ls, which gives the reasonable location you'd expect to find ls - i.e. bin/ls.

Edit 3: Got rid of the terminal images, traded them for properly-formatted code as per this meta post.

Edit 4: Added quotes around "$dir" to prevent problems with spaces.

I accidentally used the wrong-sided slash when trying to write the Newline (Line Feed) escape character, in C.

When trying to replace it in gedit:

I get this outcome:

Clearly gedit (version 3.18.3, running on my Ubuntu 16.04) is treating the New Line escape character as an excuse to actually spit out a new line.

Is this a known bug? It's an edge case, and I probably would have never even thought about it if I could write an escape character properly, but still - it made me curious as to what can be done to solve it.

I've tried parentheses, commas, one quotemark, two quotemarks.... no cigar.

The code itself is just an overly-tedious switch exercise from a book, LCTHW by Zed A. Shaw.

Title says it all.

Instead of popping out in front of all the open windows, the task switcher is stuck in the back. At first, I thought it just didn't work - and then I closed some of the windows, I saw it was just kinda stuck in the back.

EDIT 07.12.2017: Tried the fixes in the comments and answer below, no cigar.