From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: :prescript
Date: 12 Mar 1999 23:07:37 -0500 [thread overview]
Message-ID: <m3pv6eghh2.fsf@peorth.rgo.gweep.net> (raw)
In-Reply-To: Stainless Steel Rat's message of "12 Mar 1999 22:53:13 -0500"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* Stainless Steel Rat <ratinox@peorth.gweep.net> on Fri, 12 Mar 1999
| The second is a bit tougher for me to track down. Colons in the program
| string are converted to spaces. That is, "1110:peorth.gweep.net:110"
| becomes "1110 peorth.gweep.net 110". Escaping with backslashes does not
| appear to fix the problem (sigh).
Hmmm... turns out this is not a bug, but an artifact of what ps(1) reports.
So progress is being made... it'll be nice to be able to use my own code
again :).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE26eSJgl+vIlSVSNkRAr9gAKCDNdRHDtGMVLaayk3zlT8NzwHG6wCfTO6u
gJzo0iWbuqda/rDB6dWURgY=
=/s6y
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ Happy Fun Ball may stick to certain types
Minion of Nathan - Nathan says Hi! \ of skin.
PGP Key: at a key server near you! \
next prev parent reply other threads:[~1999-03-13 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-11 15:59 :prescript John Saylor
1999-03-11 16:36 ` :prescript Shaun Lipscombe
1999-03-11 16:46 ` :prescript Kai.Grossjohann
1999-03-11 22:13 ` :prescript Katsumi Yamaoka
1999-03-12 0:55 ` :prescript Stainless Steel Rat
1999-03-12 1:29 ` :prescript Neil Crellin
1999-03-13 3:53 ` :prescript Stainless Steel Rat
1999-03-13 4:07 ` Stainless Steel Rat [this message]
1999-03-14 16:12 ` :prescript Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
1999-03-11 1:05 :prescript Stainless Steel Rat
1999-03-11 15:37 ` :prescript empiric
1999-03-14 16:14 ` :prescript Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3pv6eghh2.fsf@peorth.rgo.gweep.net \
--to=ratinox@peorth.gweep.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).