Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Going one better... backslashes are omitted' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Going one better... backslashes are omitted
Authored by: Lectrick on Sep 06, '05 12:25:05AM

Please note that even though I surrounded the above code with the relevant Code tags, it STILL omitted the backslashes!!! (grrrr)

Just please assume there are backslashes. I'm going to try again below without the code tags:

jot -r -c 200 33 122 | sed 's/[^[:alnum:]*+@\?!\._]//' | rs -g 0 8

---
In /dev/null, no one can hear you scream



[ Reply to This | # ]
nevermind. backslashes NOT NEEDED!
Authored by: Lectrick on Sep 06, '05 12:52:59AM

Sorry for the repeated followups.

It appears that, unlike "normally" when you have to escape periods and question marks, in this case you don't, and if you do put backslashes there then they will just be treated as a regular allowed character and you will get passwords with backslashes in them (usually a no-no).

So to reiterate, this is perfectly fine:

jot -r -c 200 33 122 | sed 's/[^[:alnum:]*+@?!._]//' | rs -g 0 8

---
In /dev/null, no one can hear you scream



[ Reply to This | # ]
That was the bash version. tcsh here
Authored by: Lectrick on Sep 06, '05 08:18:48AM

For some reason, in the tcsh shell you have to escape the exclamation point by putting a backslash before it... so do that (or omit the !). FYI

---
In /dev/null, no one can hear you scream



[ Reply to This | # ]