Re: Feature request

["^..^" <zenfish () gmail com>]

Single quotes work.  Or a backslash:

        $ echo foo\!
        foo!

Double quotes don't work… well, sometimes they don't.  Like:

        $ echo "foo\!"
        foo\!

or:

        $ echo "foo!"
        -bash: !": event not found

But put a space after the ! and:

        $ echo "foo! "
        foo!


If you want to get crazy you can use octals with -e, of course…

        $ echo -e "\0041"
        !

        $ echo -e "\0041"
        !

        But only if quoted:

        $ echo -e \0041
        0041

At least… on many modern linux-like systems (of course lots of ways with helper programs (awk, sed, grep, etc.))  The 
behavior has changed before, prob will again.   Any input should be escaped if doing the shell dance, however, so it 
shouldn't matter in theory.

-- d

^..^

On Sep 10, 2012, at 10:30 AM, Luis MartinGarcia. <luis.mgarc () gmail com> wrote:

> On 09/10/2012 04:44 PM, David Fifield wrote:
> > On Mon, Sep 10, 2012 at 08:15:58AM -0600, Terry Freestone wrote:
> > > Hi.
> > > I love the product, but I would like to request a feature. When using the host filter in the Zenmap GUI, would it 
> > > be possible to add a host "not equal to" option?
> > >
> > > In the filter host field, just give the ability to put != in front of the filter term.
> > >
> > > Example:
> > > os:!=linux
> > How about just:
> >      os:!linux
> >
> > Is there any other interest in this feature?
> >
> > David Fifield
>
> Just note that the ! sign is not that easy to enter in a terminal. In
> bash, for example, it can only be specified between single quotes. For
> example, in my Linux box I get this:
>
> luis@seattle ~ $ echo "Hello!"
> bash: !": event not found
> luis@seattle ~ $ echo 'Hello!'
> Hello!
>
> Regards,
>
> Luis MartinGarcia.
>
>
>
>
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/