Search Results

Don't fix that last one. "suppressing further errors from this subtree" sounds like a Gotcha :D

Cool, otherwise :)

Exactly which operating system did you download the file to?

A file having a .exe extension implies (but only implies) that it's a Windows file, not a Linux one. You won't be able to natively run...

My "security" suggestion was just a guess.. probably not a very good one, or the right one for the wrong reasons! Encapsulation is good!

When the Vue instance is instantiated the execution context...

Added vbuserId to the component:

data() {
return {
...
vbuserId: vbuserId
};
},
computed:{
...
id: function() {
return this.vbuserId;
}

I...

The problem in the end was in the vB Template, where $jsGlobalsfromvB was given after the Vue components were loaded, meaning that vbuserId and vbtheURL were not set at the time the components were...

I see from the source in the test page link you sent that vbuserId and vbtheURL are both already in scope as Javascript variables, which means you can add them to your data function:


data() {...

A simple way (probably a simpler one) to swap two lines in sed would be:

sed "40h;41G;40d" file

Well, if you modify PATH from the command line it will be lost when you end your current session. To make it stick, you need to modify the path in one of your login scripts (e.g. .bashrc or...

Perhaps I misread your first post. Did you actually edit your .bashrc to add the path to gatk-4.0.10.1, or just change it on the command line?

(second, probably silly question - are you using...

I don't see where you added /usr/bin/gatk-4.0.10.1 to your PATH in the .bashrc. I won't ask why it's in /usr/ and not /usr/local/, though :)

kill requires at least one argument (one or more PIDs).

kill [-s signal|-p] [-q sigval] [-a] [--] pid...


echo doesn't require any arguments (and wouldn't appear to serve any purpose in your...

There are a number of ways to accomplish that. Assuming there is a direct one-to-one mapping between the two input files, then you could do something like:

paste file[12] | while read user pass x;...

Using strings $(which sed) | grep "followed by text" on GNU sed returns nothing, whereas it does on macOS's standard sed.

So, even though you installed GNU sed, is that the one you are actually...

-v declares a variable to use inside awk. You could also put that at the end, without -v. e.g.

awk -vd=`date +%Y%m%d` -F"," '{print $1, d}' OFS="," file

What is wrong with the result ("didn't get the result as expected)?

$ sed "s/$/,$(date '+%Y%m%d')/" file
22055,20180930
21088,20180930
93840,20180930
30990,20180930
50990,20180930...

Yes. It works this way because you are reading a file (sequentially) and processing it as it comes.

if you find red, process that
if you find blue, process that

Yields the same results as
...

I don't think that's what I said at all. If you are reading the file sequentially, you'll always get whatever color comes first, regardless of the order in which you process it.

Or maybe I'm not...

You're reading the file in sequential order. The order of your if statements is unimportant for the requirement you specified.

The redirection is a shell thing, not an awk or sed thing. Put it after the awk command, regardless of which solution you use.

e.g.

awk ...... file2 file1 > file3

or

sed .. && awk ......

Having added code tags to the data as well, I see that file1 has a lot of whitespace (spaces and/or tabs) in the fields. If you're using -F to specify a very specific field separator (,), then the...

In awk:

awk '/^root: nmp/ { getline; V[$0]++ } END { for( v in V ) print v " " V[v] }'
Segmentation fault 1
10 2
3.1 1

This method doesn't guarantee the order. You'd need to modify it...

There is (as is always the case) a number of ways of doing this. Here's one with awk:

awk -F'"' '/EqName/ { sub(" ", "_", $2) }1' file
{
EqName Tan_1
....
....
}

{

EqName ...

You never really mentioned what error you get when you try to install the package...

OK, well apologies for the slight tangent I sent us off on, but again it comes back to this "DEVNAME" thing.

Before, or after, when you call fdisk..


DEVNAME=$(fdisk -l |grep FAT16 |awk...

Ah, bajeezus.. I somehow forgot this was about udev! Are there any errors in the system logs (dmesg, etc.)?