Try:

    grep --text

or

    grep -a 

for short. This is equivalent to `--binary-files=text` and it should show the matches in binary files.

I have a read large csv file into a data frame. Data in the csv file are from multiple web sites representing user information. For example here is the structure of the data frame.

    user_id, number_of_logins, number_of_images, web
    001, 34, 3, aa.com
    002, 4, 4, aa.com
    034, 3, 3, aa.com
    001, 12, 4, bb.com
    002, 1, 3, bb.com
    034, 2, 2, cc.com

as you can see once I bring the data into the data frame user_id is no longer a unique id and this causes all the analysis. I am trying to add another columns prior to `user_id` which is something like `&quot;generated_uid&quot;` and pretty much use the index of the `data.frame` to be filled by that column. What&#39;s the best way to accomplish this. 

Add an index (numeric ID) column to large data frame

&lt;kbd&gt;Ctrl&lt;/kbd&gt;+&lt;kbd&gt;D&lt;/kbd&gt; performs the `find_under_expand` command in sublime. This basically searched for the next occurrence of the already selected text and selected it, so when I edit, it&#39;s edited on both places at the same time. I&#39;m currently trying to move to IDEA editors (such as WebStorm, PHPStorm, PyCharm, etc) but didn&#39;t find something like this command in this IDE yet.

How can I select next occurrence in IDEA editors

I&#39;ve got a grep script that searches through a directory recursively.

    grep -n -R -e &#39;search term&#39; -e &#39;second search term&#39; ./ 


However the results I get are the following. Notice there are found matches in JPGs but no actual result. 

    Binary file ./jpg/00015928.jpg matches
    Binary file ./jpg/00015296.jpg matches
    Binary file ./jpg/00020072.jpg matches

Is there any way to see the result in the output like a normal grep search? 



Grep &#39;binary file matches&#39;. How to get normal grep output?

I've got a grep script that searches through a directory recursively.
<pre><code class="hljs language-perl">grep -n -R -e 'search term' -e 'second search term' ./ 
</code></pre>
However the results I get are the following. Notice there are found matches in JPGs but no actual result.
<pre><code class="hljs language-sql">Binary file ./jpg/00015928.jpg matches
Binary file ./jpg/00015296.jpg matches
Binary file ./jpg/00020072.jpg matches
</code></pre>
Is there any way to see the result in the output like a normal grep search?

I&#39;m working with this:

    GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)


I have a script like below:

    #!/bin/bash

    e=2
    
    function test1() {
      e=4
      echo &quot;hello&quot;
    }
    
    test1 
    echo &quot;$e&quot;

Which returns:

    hello
    4

But if I assign the result of the function to a variable, the global variable `e` is not modified:

    #!/bin/bash
    
    e=2
    
    function test1() {
      e=4
      echo &quot;hello&quot;
    }
    
    ret=$(test1)
    
    echo &quot;$ret&quot;
    echo &quot;$e&quot;

Returns:

    hello
    2

I&#39;ve heard of [the use of eval][1] in this case, so I did this in `test1`:

    eval &#39;e=4&#39;

But the same result.

Could you explain me why it is not modified? How could I save the echo of the `test1` function in `ret` and modify the global variable too?


  [1]: https://superuser.com/a/628865/235245

How to modify a global variable within a function in bash?

When I try to run a script that contains the envsubst command, I get this error. Looking online, this seems to be a standard bash command, so I am not sure what to install in order to get it to work.

envsubst: command not found on Mac OS X 10.8

Excited that Firebase&#39;s hosting is now out of beta. Trying to get going with with the firebase-tools package and I&#39;ve successfully installed it:

    npm install -g firebase-tools

Trying to run any tool fails with

    -bash: firebase: command not found

I&#39;ve tried putting the following command in my .bash_profile without any luck

    export PATH=/usr/local/share/npm/bin:$PATH

Any ideas? Pretty new to the command line in general.

Thanks!

firebase-tools &quot;-bash: firebase: command not found&quot;

I&#39;m trying to write a Bash script that will overwrite an existing directory. I have a directory `foo/` and I am trying to overwrite `bar/` with it. But when I do this:

    cp -Rf foo/ bar/

a new `bar/foo/` directory is created. I don&#39;t want that. There are two files in `foo/`; `a` and `b`. There are files with same names in `bar/` as well. I want the `foo/a` and `foo/b` to replace `bar/a` and `bar/b`.


How to force &#39;cp&#39; to overwrite directory instead of creating another one inside?

I am writing a bash script that needs to parse filenames.

It will need to remove all special characters (including space): **&quot;!?.-_** and change all uppercase letters to lowercase.  Something like this:

    Some_randoM data1-A
    More Data0

to:

    somerandomdata1a
    moredata0

I have seen lots of questions to do this in many different programming languages, but not in bash.  Is there a good way to do this?

Remove all special characters and case from string in bash

I have bunch of files sitting in folders like

    data\A\A\A\json1.json
    data\A\A\A\json2.json
    data\A\A\B\json1.json
    ...
    data\Z\Z\Z\json_x.json

I want to cat all the jsons into one single file?


Recursively cat all the files into single file

When using `grep` in linux, the result often contains a lot of &quot;binary file XXX matches&quot;, which I do not care about. How to suppress this part of the results, or how to exclude binary files in grep?

How to suppress binary file matching results in grep

I need to check if the recipient username is in file */etc/passwd* which contains all the users in my class, but I have tried a few different combinations of *if* statements and *[grep][1]* without success. The best I could come up with is below, but I don&#39;t think it&#39;s working properly.

My logic behind it is that if the *grep* is null, the user is invalid.

    send_email()
    {
      message=
      address=
      attachment=
      validuser=1
      until [ &quot;$validuser&quot; = &quot;0&quot; ]
        do
        echo &quot;Enter the email address: &quot;
        read address
        if [ -z grep $address /etc/passwd ]
          then
        validuser=0
        else
            validuser=1
        fi
        echo -n &quot;Enter the subject of the message: &quot;
        read message
        echo &quot;&quot;
        echo &quot;Enter the file you want to attach: &quot;
        read attachment
        mail -s &quot;$message&quot; &quot;$address&quot;&lt;&quot;$attachment&quot;
        done
        press_enter
    }

  [1]: https://en.wikipedia.org/wiki/Grep




How can I check if &#39;grep&#39; doesn&#39;t have any output?

Given the following shell script, would someone be so kind as to explain the `grep -Po` regex please?

    #!/bin/bash
    # Issue the request for a bearer token, json is returned
    raw_json=`curl -s -X POST -d &quot;username=name&amp;password=secret&amp;client_id=security-admin-console&quot; http://localhost:8081/auth/realms/master/tokens/grants/access`
    # Strip away all but the &quot;access_token&quot; field&#39;s value using a Python regular expression
    bearerToken=`echo $raw_json | grep -Po &#39;&quot;&#39;&quot;access_token&quot;&#39;&quot;\s*:\s*&quot;\K([^&quot;]*)&#39;`
    echo &quot;The bearer token is:&quot;
    echo $bearerToken

So specifically, I&#39;m interested in understanding the parts of the regex

    grep -Po &#39;&quot;&#39;&quot;access_token&quot;&#39;&quot;\s*:\s*&quot;\K([^&quot;]*)&#39;`

and how it works. Why so many quotes? What is the &quot;K&quot; for? I&#39;ve some experience with grep regex but this confuses me.

This is the actual output of the curl command and the shell script (grep) works as desired returning just the contents of the &quot;access_token&quot; value.

&gt; {&quot;access_token&quot;:&quot;eyJhbGciOiJSandNoThisIsntRealndmbS1yZWFsbSI6eyJyb2xlcyI6WyJtYW5hZ2UtY2xpZW50cyIsInZpZXctcmVhbG0iLCJtYW5hZ2UtZXZlbnRzIiwidmlldy1ldmVudHMiLCJ2aWV3LWFwcGxpY2F0aW9ucyIsInZpZXctdXNlcnMiLCJ2aWV3LWNsaWVudHMiLCJtYW5hZ2UtdXNlcnMiLCJtYW5hZ2UtYXBwbGljYXRpb25zIiwibWFuYWdlLXJlYWxtIl19LCJtYXN0ZXItcmVhbG0iOnsicm9sZXMiOlsibWFuYWdlLWV2ZW50cyIsIm1hbmFnZS1jbGllbnRzIiwidmlldy1yZWFsbSIsInZpZXctZXZlbnRzIiwidmlldy1hcHBsaWNhdGlvbnMiLCJ2aWV3LXVzZXJzIiwidmlldy1jbGllbnRzIiwibWFuYWdlLXJlYWxtIiwibWFuYWdlLXVzZXJzIiwibWFuYWdlLWFwcGxpY2F0aW9ucyJdfX19.fQmQKn-xatvflHPAaxCfrrVow3ynpw0sREho7__jZo2d0g1SwZV7Lf4C26CcweNLlb3wmKHHo63HRz35qRxJ7BXyiZwHgXokvDJj13yuOb6Sirg9z02n6fwGy8Iog30pUvffnDaVnUWHfVL-h_R4-OZNf-_YUK5RcL2DHt0zUXI&quot;,&quot;expires_in&quot;:60,&quot;refresh_expires_in&quot;:1800,&quot;refresh_token&quot;:&quot;eyJhbGciOiJSUzI1NiJ9.eyJqdGkiOiJlNWFmYTZiOC04ZjM5LTQ5MjUtOWZiMC00MmY3MTM4YzUzMGIiLCJleHAiOjE0NDY4Mjk3OTksIm5iZiI6MCwAreYouKiddingIwouldnotputSOmethigRealHereNpb25fc3RhdGUiOiI2MmVmYzA1Yy0xYmY1LTRmNTUtYjc0OS01ZTBlZmY5NDE1NWIiLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiYWRtaW4iLCJjcmVhdGUtcmVhbG0iXX0sInJlc291cmNlX2FjY2VzcyI6eyJ3Zm0tcmVhbG0iOnsicm9sZXMiOlsibWFuYWdlLWV2ZW50cyIsInZpZXctcmVhbG0iLCJtYW5hZ2UtY2xpZW50cyIsInZpZXctYXBwbGljYXRpb25zIiwidmlldy1ldmVudHMiLCJ2aWV3LXVzZXJzIiwidmlldy1jbGllbnRzIiwibWFuYWdlLXJlYWxtIiwibWFuYWdlLWFwcGxpY2F0aW9ucyIsIm1hbmFnZS11c2VycyJdfSwibWFzdGVyLXJlYWxtIjp7InJvbGVzIjpbInZpZXctcmVhbG0iLCJtYW5hZ2UtY2xpZW50cyIsIm1hbmFnZS1ldmVudHMiLCJ2aWV3LWFwcGxpY2F0aW9ucyIsInZpZXctZXZlbnRzIiwidmlldy11c2VycyIsInZpZXctY2xpZW50cyIsIm1hbmFnZS1hcHBsaWNhdGlvbnMiLCJtYW5hZ2UtdXNlcnMiLCJtYW5hZ2UtcmVhbG0iXX19fQ.WeiJOC1jQ52aKgnW8UN2Lv9rJ_yKZiOhijOYKLN2EEOkYF8rvRZsSKbTPFKTIUvjnwy2A7V_N-GhhJH4C-T7F5__QPNofSXbCNyvATj52jGLxk9V0Afvk-Z5QAWi55PJRTC0qteeMRcO2Frw-0KtKYe9o3UcGICJubxhZHsXBLA&quot;,&quot;token_type&quot;:&quot;bearer&quot;,&quot;id_token&quot;:&quot;eyJhbGciOiJSUzI1NiJ9.eyJuYW1lIjoiIiwianRpIjoiMGIyMGI0ODctOTI4OS00YTFhLTgyNmMtM2NiOTg0MDJkMzVkIiwiZXhwIjoxNDQ2ODI4MDU5LCJuYmYiOjAsImlhdCI6MTQ0NjgyNzk5OIwouldhaveToBeNutsUiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJhZG1pbiIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZX0.DmG8Lm4niL1djzNrLsZ2CrsB1ZzUPnR2Nm7IZnrwrmkXsrPxjl6pyXKCWSj6pbk2sgVI8NNFqrGIJmEJ7gkTZWm328VGGpJsmMuJBki0KbqBRKORGQSgkas_34rwzhcTE3Iki8h_YVs2vvNIx_eZSOvIzyEcP3IGHuBoxcR6W3E&quot;,&quot;not-before-policy&quot;:0,&quot;session-state&quot;:&quot;62efc05c-1bf5-4f55-b749-5e0eff94155b&quot;}

----- 

In case anyone finds this post, this is what I ended up using:

    if hash jq 2&gt;/dev/null; then
      # Use the jq command to safely parse json
      bearerToken=$(echo $raw_json | jq -r &#39;.access_token&#39;)
    else
      # Strip away all but the &quot;access_token&quot; field&#39;s value using a perl regular expression
      bearerToken=$(echo $raw_json | grep -Po &#39;&quot;&#39;&quot;access_token&quot;&#39;&quot;\s*:\s*&quot;\K([^&quot;]*)&#39;)
    fi



What does &#39;\K&#39; mean in this regex?

What is the best way to find a specific string in the logs of a docker container? Let&#39;s say I want to see all requests, that are made in the &quot;nginx&quot; docker image that came from a ip starting with &quot;127.&quot;

grep wont work as expected on docker logs command:

    docker logs nginx |&#160;grep &quot;127.&quot;

It prints all logs, but does not filter the result!

Content Type	Original Author	Original Content on Stackoverflow
Question	davidbain	View Question on Stackoverflow
Solution 1 - Bash	perreal	View Answer on Stackoverflow

Grep 'binary file matches'. How to get normal grep output?

Bash Problem Overview

Bash Solutions

Solution 1 - Bash

How can I select next occurrence in IDEA editors

Add an index (numeric ID) column to large data frame

Attributions