Damien Nadé wrote:
I've tried to insert a single quote into a variable content.
With something like this :
bash-3.2$ foo=bar
bash-3.2$ echo "${foo/%/'}"
If you look at that, you understand that > is the $PS2, so it means that
bash is interpreting the single quote a special char.
Bash is ac
Sam Steingold wrote:
Where is the readline/history cvs (or git or whatever) repository?
There is no public cvs repository.
to keep the clisp readline module up to date with the current
readline/history releases, I would like to be able to get a diff between
readline.h & history.h from readli
Where is the readline/history cvs (or git or whatever) repository?
to keep the clisp readline module up to date with the current
readline/history releases, I would like to be able to get a diff between
readline.h & history.h from readline 5.0 and readline 5.2.
how do I get those diffs (without
Damien Nadé wrote:
I've tried to insert a single quote into a variable content.
With something like this :
bash-3.2$ foo=bar
bash-3.2$ echo "${foo/%/'}"
>
If you look at that, you understand that > is the $PS2, so it means that
bash is interpreting the single quote a special char.
So, nat
Bob Proulx wrote:
Of course that makes sense for the "==" and "!=" cases. But is that
true even for the "=" case? For the "=" case I thought it was
"STRING1 = STRING2" and not "STRING = PATTERN".
`=' and `==' are always equivalent. When used in the test/[ command,
they match strings. In th
