Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7848711
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T18:17:56+00:00 2026-06-02T18:17:56+00:00

If I do: if grep someexpression somefile >/dev/null; then … fi Things work fine.

  • 0

If I do:

if grep someexpression somefile >/dev/null; then
   ...
fi

Things work fine.

To do a “not”, I know I can do this (using [] which is the test command):

if [ '!' somecondition ] ; then
   ...
fi

A simple workaround:

grep someexpression somefile >/dev/null
if [ '!' $? ]; then
   ...
fi

But the above workaround won’t work with a while loop, so then I need to write a function instead, which is annoying. How do I do a not with the grep thing above, the proper way?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T18:17:59+00:00Added an answer on June 2, 2026 at 6:17 pm

    Try:

    if ! grep someexpression somefile >/dev/null; then
       ...
    fi
    

    Note that the space after ! is mandatory, otherwise it will (try to) invoke history expansion.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am using grep to detect <a href=xxxx> something here </a> This is not
Using only grep and sed, is there a way I can tranform the output
ls | grep -v //|=/|@/|| will ls then piped to a reverse grep work?
It seems odd that grep does not work with an optional selector argument -
cat 1.html | grep <title> > title.txt This grep statement is not working. Please
We can use grep to return the lines with matched words, but how to
Can grep pick lines if at least one element from a list of words
I'm using grep to extract lines across a set of files: grep somestring *.log
I'm using grep to extract lines across a set of files: grep somestring *.log
I'm using grep to filter the Mac OS X dictionary words file (by default

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.