19,987 reputation
34475
bio website
location United States
age
visits member for 3 years, 2 months
seen 7 hours ago

Debian user, GNU/Linux enthusiast, FLOSS supporter, hobby developer.


Jun
20
comment How to combine Bash's read with HERE-document when shopt -os errexit is in place?
@mikeserv Did you confuse me with OP? I am not the one that asked the question. Ask OP, not me. Note that your question is something I already pointed out to the OP in my first comment: "I assume your actual code is a bit more complex than your toy example, because in this case assigning to the variable directly would be much simpler.", i.e. desc='bla bla'.
Jun
19
comment Make vim stop splitting my Git commit messages
(continued)... So, this is not technically an answer, but you are supposed to make the highlighting not ugly by writing a properly formatted git commit message. Try to keep line one below 50 characters. Line 2 is supposed to be blank, which is why it is being colored a BOLD RED for "Warning: this text isn't supposed to be here!" Type the extended message beginning on line 3. Vim will automatically break your lines at 72 characters. Let it do so. If you need Vim to redo the line breaks because you did some editing, highlight the paragraph and do gq to fix the line breaks.
Jun
19
comment Make vim stop splitting my Git commit messages
This is Vim's built-in file type syntax highlighting for git commit messages trying to enforce a certain format for git messages. Your highlighting looks ugly because your git commit message is "ugly", in the sense that it does match the format Vim is expecting you to follow. Both the gitcommit.vim syntax highlighting module and the guidelines were written by Tim Pope. You can read them here: tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html. For a quick summary, make the first line a 50 character summary, leave a blank line, and then write your paragraphs below.
Jun
19
comment How to combine Bash's read with HERE-document when shopt -os errexit is in place?
See unix.stackexchange.com/q/13272/9537. What you want is read ... <<EOF || true not read ... || true <<EOF. The <<EOF is for the read not the true. I assume your actual code is a bit more complex than your toy example, because in this case assigning to the variable directly would be much simpler.
Jun
18
awarded  Great Answer
Jun
18
awarded  Nice Answer
Jun
17
awarded  Enlightened
Jun
17
awarded  Nice Answer
Jun
16
comment sudoers conditional/combo command is possible?
@AquariusPower "only-writeable by root" is not the same thing as "owned by root" and it is the former that matters.
Jun
16
revised Escape on Control key, Control on Capslock key, Capslock on Escape key
added 70 characters in body
Jun
14
answered Escape on Control key, Control on Capslock key, Capslock on Escape key
Jun
14
comment Multiple XkbOptions in xorg.conf
It should be the first, commas with no spaces. Can you post the exact line you are having trouble with?
Jun
14
comment Use find to find certain directory and delete all files in it except one directory
What happens if you have a directory like ./Library/Caches/not_Snapshots/Caches/Snapshots/? Do you want to delete that directory because it is inside ./Library/Caches/not_Snapshots/ or save it because it is a Snapshots directory?
Jun
13
reviewed Approve suggested edit on Looping the listing files in UNIX
Jun
13
comment Looping the listing files in UNIX
The problem is you haven't explained what you want to do. "Check" is not an executable that you run. "Check" is something you can do with your eyes by looking to see if there is a d. Also, I presume your choice of -rt means the sort order is significant?
Jun
13
comment Looping the listing files in UNIX
You can already see which are directories - those are the ones that start with d.
Jun
13
comment Looping the listing files in UNIX
What are you trying to accomplish?
Jun
13
comment Why does vim color this .bashrc line incorrectly? Fixable?
What Vim version do you have? I tried pasting that sqlplus line into my bashrc and Vim 7.3 highlights it correctly. What is your filetype set to? (:set ft? or :echo &ft). Since the highlighting in your image is wrong but the bash syntax is correct, either you have the wrong filetype or the syntax file you have in your Vim is bugged.
Jun
11
answered AWK: Nested Conditional Subset of Rows without Headers
Jun
10
comment Guard against killing an already killed process
@JosephR. The right solution to that (completely different problem) is something along the lines of kill pid || true. When all you have is a PID, it is impossible to avoid race conditions if the state of the PID changes between when you check it and when you try to do something with it.