Date: Sat, 13 Sep 2003 02:49:45 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 201 ************************************************** Friday 12 September 2003 Number 201 ************************************************** Subjects for today 1 Re: Another IFS= problem : James Moe" 2 How-to: make a patch file : James Moe" 3 Re: Possible problem with read() and write()? -- Never mind : Andreas Buening 4 Re: Another IFS= problem : Andreas Buening 5 Re: How-to: make a patch file : Stefan.Neis at t-online.de **= Email 1 ==========================** Date: Sat, 13 Sep 2003 09:40:27 -0700 (MST) From: "James Moe" Subject: Re: Another IFS= problem -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 13 Sep 2003 13:54:48 +0200, Andreas Buening wrote: >Are you sure you have to replace it? As long as there are no filenames >containing drive letters in the string, a ':' should be fine. > That is what I ended up doing. As a sanity check I re-built tdb just now. It is really quite annoying: it worked like it was supposed to, ie, it used the tilde as a separator. I can only guess that something was corrupted in the session where the replacement did not work, and having re-booted since then has cleared that up. - -- jimoe at sohnen-moe dot com pgp/gpg public key: http://www.keyserver.net/en/ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0 OS/2 for non-commercial use Comment: PGP 5.0 for OS/2 Charset: cp850 wj8DBQE/Y0h7sxxMki0foKoRAv9sAKCYJs+S4tl94sb3//3b4VeEn9MuVgCfQIkz X04pASOCM1C2Bvqs0GUHe7k= =BAzw -----END PGP SIGNATURE----- _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Sat, 13 Sep 2003 10:12:24 -0700 (MST) From: "James Moe" Subject: How-to: make a patch file -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, How do I make a patch file using diff? - -- jimoe at sohnen-moe dot com pgp/gpg public key: http://www.keyserver.net/en/ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0 OS/2 for non-commercial use Comment: PGP 5.0 for OS/2 Charset: cp850 wj8DBQE/Y0/4sxxMki0foKoRAj3VAJ97NfK5H0UnFomgEoAk4yHBRPZx7gCff3IF DZ6ps9mA5eE6kV87nLb7XDw= =fV+W -----END PGP SIGNATURE----- _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Sat, 13 Sep 2003 13:54:43 +0200 From: Andreas Buening Subject: Re: Possible problem with read() and write()? -- Never mind James Moe wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 11 Sep 2003 09:04:46 +0100, Stefan.Neis at t-online.de wrote: > > > For some operating > >systems (especially all Unices), there's no difference between text > >mode and binary mode, however. > > > Ah! Again I get it. Another *nix thing, the newline (LF), that is transparent in *nix > but becomes a gotcha in os/2 (CR+LF). > By opening the files in binary mode, I got rid of all that conditional read/write > code. The best solution would be if you politely suggest to the maintainers that they open all files explicitely in binary mode. If other systems don't support O_BINARY they could use #ifndef O_BINARY # define O_BINARY 0 #endif or something similar depending on how they open files. Bye, Andreas _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Sat, 13 Sep 2003 13:54:48 +0200 From: Andreas Buening Subject: Re: Another IFS= problem James Moe wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > A libtool script is using IFS= to tokenize a string. This time it is using a tilde > (~) instead of a colon. Simple attempts to replace the tilde with a semicolon are not > working: > > cmd2=`echo $cmds | tr '~' ';'` > cmd2=`echo $cmds | sed "s/~/;/g"` > > In both cases the replacement character is a space, not a semicolon. I have tried other > replacement characters as well with no change in behavior. There must be something > about a tilde that is special. Escaping it (\~) or using a octal code (\176) made no > difference. > Any ideas about how to change a tilde to a semicolon? Are you sure you have to replace it? As long as there are no filenames containing drive letters in the string, a ':' should be fine. Btw, for the sed command you'd better use single instead of double quotes. Bye, Andreas _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Sat, 13 Sep 2003 21:52:32 +0100 From: Stefan.Neis at t-online.de Subject: Re: How-to: make a patch file > Hello, > How do I make a patch file using diff? Essentially by diff -bu2 old_file new_file where old_file and new_file actually might be original_directory and modified_directory, if you changed more than one file - you might also want to add "-r" flag in this case. If there's a CVS repository, you might want to use "cvs diff ..." A nice, more or less "generic" description with lots of details can be found e.g. here: http://wxwindows.org/technote/patches.htm Regards, Stefan _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs