maillog: 19/09/2005-11:52:26(+0200): Paul de Vrieze types > On Saturday 17 September 2005 22:06, Mike Frysinger wrote: > > On Saturday 17 September 2005 01:15 pm, Ciaran McCreesh wrote: > > > On Sat, 17 Sep 2005 12:56:37 +0200 "Fernando J. Pereda" > > > > > > <[EMAIL PROTECTED]> wrote: > > > | On Sat, Sep 17, 2005 at 02:42:09AM +0100, Ciaran McCreesh wrote: > > > | | Something strange I noticed... Some people are using funny quotes > > > | | and non breaking spaces in ebuilds. Some people are using weird > > > | | characters as substitution delimiters for sed. Don't! It will > > > | | break on many systems. I'm going to go and purge all of those, > > > | | UTF-8 or not, whenever my brain recovers. > > > | > > > | I hope ~ is not considered a weird character... if it is, tell me > > > | and I'll fix all my ebuilds. > > > > > > No, ~ is fine. Anything with a value below 127 (don't use 127, it's > > > weird) that sed accepts is ok. > > > > in other words, ASCII characters are OK. if in doubt, just run `man > > ascii` and see if your character is in the table > > You probably don't want to use the ascii control characters either > (anything below 32), although they should not give issues with people > they could cause havoc for terminals or annoy people (using the BELL > character as sed separator).
Um, I guess everybody got the point. In fact, you probably shouldn't use alphanumerics either -- they work, but are as ugly as... echo herr | sed -e sorolog -- (* Georgi Georgiev (* They can always run stderr through uniq. :-) (* *) [EMAIL PROTECTED] *) -- Larry Wall in *) (* +81(90)2877-8845 (* <[EMAIL PROTECTED]> (*
pgpg5sCWkN0mw.pgp
Description: PGP signature
