Reputation
21,695
Next tag badge:
845/400 score
77/80 answers
Badges
3 48 79
Newest
 Enlightened
Impact
~840k people reached

Jul
23
comment missing argument to find -exec
Yup, no harm in over-quoting. It's definitely better to err that way than the other way, but leaving out redundant quotes does save some keystrokes :). Normally I don't point out redundant quotes but in this case I just wanted to make sure the questioner understood where the real issue was, i.e. the misquoted ; character.
Jul
23
comment What does .??* mean in a shell command?
@SabreWolfy If you read the POSIX spec carefully, that's actually an important difference between globs and regex: in bracket expressions, [^abc] in regex syntax means the same as [!abc] in glob syntax (i.e. ^ is replaced with ! for globs). Using [^abc] style syntax in a glob is not very portable because POSIX does not specify what it means, so some shells interpret it using regex-like semantics while others treat ^ as just a literal character.
Jul
23
comment Reload ~/.profile for desktop
It would probably help to post which desktop environment you are using. I think the easiest way is to log out and back in - any other way will be difficult and not fool-proof.
Jul
23
revised What does .??* mean in a shell command?
added 321 characters in body
Jul
23
comment missing argument to find -exec
Wherever you found those examples that used the wrong slash must not be a very good resource. I would recommend not going there for examples anymore.
Jul
23
comment How to check the operating system of a server remotely?
I don't think any such tool to determine OS type solely from IP address exists. nmap could give you its best guess.
Jul
23
comment missing argument to find -exec
Found it: modern shells don't require quoting {}.
Jul
23
comment missing argument to find -exec
Backslash and slash are not the same thing at all. Backslashes lean backwards: \\ , Forward slashes, or just slashes, lean forwards: /. In Unix, slashes are generally path separators, while backslashes are generally used for quoting / escaping.
Jul
23
comment missing argument to find -exec
It's almost never necessary to quote {}. There was actually an entire question about that, but I can't find it because the site can't search for {}. The issue is the /; typo in the original question.
Jul
23
comment Ansi escape code in VIM
You are talking about syntax highlighting, which is different from raw ANSI escape codes embedded in the text.
Jul
23
comment How to install Java Runtime Environment 7 update 5 for x64 arquitecture on Debian OS?
First things first - have you tried the openjdk java? It's the recommended distribution on Debian systems. If not, then I'd try the java-package route first, before the wiki-how link. With a packaging system as mature as Debian's, always treat generic instructions that involve manually copying and symlink-ing lots of files with a healthy dose of suspicion. With Debian, there's usually a cleaner or, for lack of a better word, more "Debian-way" method.
Jul
23
comment How to log all my DNS queries?
Given how large bind is and its lackluster security record, I think many people would hesitate to install something like that for the sole purpose of logging.
Jul
22
awarded  Nice Answer
Jul
22
revised What does .??* mean in a shell command?
added 25 characters in body
Jul
22
answered What does .??* mean in a shell command?
Jul
22
comment Where to start creating CLI applications?
@EmanuelBerg You are talking about the developer's perspective, not the user's. What I said applies to the user side. As a developer you can set up your workflow however you (or your team) like, but you should definitely take out the extension when you package and ship. (It's probably fine to ship a file with an extension and provide an extension-less symlink for the user.) Any decent editor like vim and emacs should be able to determine file type from the shebang line, NOT the suffix - after all it's what your system uses to find the interpreter to run the file.
Jul
22
answered Bash: kill background jobs
Jul
19
comment Bash: kill background jobs
for pid in $(jobs -p); do kill $pid; done?
Jul
19
comment Bash: kill background jobs
kill $(jobs -p) seems easier.
Jul
19
revised Where are command line arguments (e.g. 'some.text') actually passed to?
edited tags; edited title