I would like to search \G string including the backslash with grep.
$ echo "\G\\G" > /tmp/test
$ grep '\G' /tmp/test
\G\G
$ grep '\\G' /tmp/test
\G\G
$ grep "\\G" /tmp/test
\G\G
$ grep "\G" /tmp/test
\G\G
Also see the screenshot below for the matches in red:
I was wondering why only '\\...
@FaheemMitha With "\\Sig" you also have the shell poking into the string, so you will additionally have to escape both backslashes. What you end up with is "\\\\Sig".
With "\\Sig", the shell will give \Sig to grep. \S is a literal S.
With '\\Sig', the shell will give \\Sig to grep. \\ is a literal backslash.
the usage for /history says "The history of Unix systems and their main components. Please DO NOT USE this tag for shell-related questions; use "command-history" instead."
"shell-related questions" is too broad I think, although it does further clarify by saying: "This tag is about the history of Unix systems and their main components. For the recall of previous commands in shells and other applications, use command-history"
It seems like essentially the same thing except it calculates the sleep time using more "human readable" input, although sleep itself on some systems can take human readable numbers like sleep 1h (I think)
it also contains a useless use of date which I didn't think was a thing
`date -d $(date -d "1 hours" '+%H:00:00') '+%s'` is equal to: `date -d '1 hours' +%s`
So, in essence, the backslash in \S preserves the literal value of the S in contexts that may otherwise interpret it as something else. I'm not away of any such context. More useful is \␣ (backslash-space), which causes the shell not to do word splitting on that space.
Long story short, I am trying to do operation system virtualization. To do so I unshared the mount namespace and PID namespace of a parent process and then forked. Yet when the child process tries to execute some command I can see there are many other PID's although I did unshare(CLONE_NEWPID)
T...
I'm trying to apply the answer from https://unix.stackexchange.com/a/6438/32774 in my bash script (a script for transmission that runs after a file is completed)
But I just get this in my syslog: /home/xorinzor/transmission_torrent_finished.sh: line 14: [/home/xorinzor/Downloads/transmission/completed/KNOPPIX_V7.2.0CD-2013-06-16-DE: No such file or directory
The line looks like this: if ["${FINISHED_DOWNLOAD##COMPLETED_PATH}" != "${FINISHED_DOWNLOAD}" ]; then
Where I want to make sure that the path from FINISHED_DOWNLOAD is a subdirectory of COMPLETED_PATH.
@Kusalananda no worries, my experience with the SO chatroom is that people aren't really in the chatroom that much anyway, so I figured I'd just give it a go, wait a bit, and if nothing happened to create a question instead ;)
I would like to search \G string including the backslash with grep.
$ echo "\G\\G" > /tmp/test
$ grep '\G' /tmp/test
\G\G
$ grep '\\G' /tmp/test
\G\G
$ grep "\\G" /tmp/test
\G\G
$ grep "\G" /tmp/test
\G\G
Also see the screenshot below for the matches in red:
I was wondering why only '\\...
