[opensuse] Re: apache mod_rewrite

On Sun, 03 May 2009 11:02:37 -0700, Randall R Schulz wrote:

On Sunday May 3 2009, Jim Henderson wrote:
On Sun, 03 May 2009 10:06:36 -0700, Randall R Schulz wrote:
It is not. ! is the history access introducer. It is interpreted
outside of quotes and inside double-quote strings but not inside
single-quote strings.

Yes, I am fully aware of that. However that is the only place "!"
is on the line, so for some reason it's being interpreted that way.

Being interpreted what way? It was used incorrectly and a diagnostic
resulted.

Yes, but for some reason it was picked up and interpreted in a way that
caused the diagnostic.

This is nonsensical. The ! was followed by a character not allowed in
history expansions. That is why BASH rejected the command line and
printed a diagnostic.

You and I are saying the exact same thing in different ways. You're
explaining that "!" calls back the history and it's failing. I'm saying
that the "!" character is being interpreted "incorrectly" - incorrectly
based on the intention of it being included in that command, not
incorrectly based on its actual use.

Bash *should* have induced that the "!" was in a quoted line and
shouldn't have expanded it. It did for some reason - maybe because
Duaine put two single quotes instead of a double quote at the start of
the string. I don't know why and I don't particularly care.

The end result was the diagnostic message was displayed because the shell
interpreted the use as being something other than what the person
entering the command meant.

In other words, the intention was interpreted incorrectly by the shell.

If you want to insist that my read of this is incorrect, fine.

Is there some particular reason you wish to argue about this? Or can
we move on?

You can do whatever you please, but I feel the need to correct false
information on this list. So as long as you keep posting misinformation,
I'm going to keep correcting it.

I would disagree that my information was incorrect. I interpreted the
output based on the input provided.

But fine, whatever. I know the information was correct, and if I didn't
present it up to your standard of clarity, oh well. I know what I meant
and I suspect most others on the list understood what I meant. If you
feel it's necessary to nitpick every answer, go ahead and be my guest.

Your way of expressing things isn't the only way to do so.

Jim
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Writing text string with imbedded quotes to a text stream
    ... I want to write a series of comand line strings having imbedded quotes like ... the command written to the export file. ... The key VBA statement that writes these command line strings is: ...
    (microsoft.public.excel.programming)
  • Re: [SLE] Pullin my hair out... arrrgh
    ... Yes, quotes should be there, in case the programs's named '-n' ... strings on the command line and in scripts. ...
    (SuSE)
  • Re: need syntax help
    ... into the "command" field below? ... it already has quotes around it as you show it above. ... I assume the arguments are all supposed to be strings, so each argument should be an expression which evaluates to a string. ...
    (comp.lang.perl.misc)
  • passing text as command line to another script?
    ... I read each file of the text file and then call the correct shell and ... so the command line should be... ... QUOTES, but when I type the SAME thing and hit enter, $1 and $2 are ... strings WITHOUT the quotes. ...
    (comp.os.linux.misc)
  • Re: The format of filename
    ... The syntax of the command is incorrect. ... C:\temp> REM try with quotes, ...
    (comp.lang.python)