New answers tagged history
People had been writing scripts (and possibly C programs) to run file on a file, capturing the output with $(file foobar) or popen(), and doing a string match check to see whether the output from file contained (or ended with) the word “text”. Then the developers of the Berkeley Software Distribution (at the University of California, Berkeley) did as ...
vi is inspired by ex, ex is inspired by ed, ed is inspired by qed ed was hacked together by Ken Thompson way back in the 1971 — basically he put regex in qed (he did a lot more than that, but it's outside the scope of this answer.) One command in ed was the "g" or "global" command. It allowed you to operate on all lines in the file at once. Grep ...
Per the Wikipedia page on the subject: shell account - A shell account is a user account on a remote server, traditionally running under the Unix operating system, which gives access to a shell via a command-line interface protocol such as telnet or SSH. ... So the fact that it utilizes a "shell" such as Bash, Bourne, etc. is why.
The term 'remote account' doesn't tell me anything about the nature of the account. I know it is on a remote machine, but that is about it. Could it be for email? for printing? for mysql management? is it an RDP login? a samba share? You see, remote is not descriptive or intuitive at all. The term shell refers to the command interpreter you use when ...
I believe they both came at the same time as part of ed, or possibly QED. They're pretty fundamental to the usage of ed. If there were ever a version that didn't have both, I can't imagine how it would function. g// and //g are two completely different things. And there are actually several things going on here. // is for searching for the next line in ...
You might find this collection of examples interesting: Pattern Matching and Permuted Term Indexing with Command Line Tools in Linux
Top 50 recent answers are included