From: andrey mirtchovski <andrey@lanl.gov>
To: plan9@kp.km.ua, 9fans@cse.psu.edu
Subject: re: [9fans] xscreensaver hacks
Date: Fri, 21 Jun 2002 14:20:38 -0600 [thread overview]
Message-ID: <047076093ee1d5edf12d3ecd3523f147@acl.lanl.gov> (raw)
>
> What`s wrong?
>
upas seems to have appended two lines of text at the end (probably
because there's no '\n')...
remove
--upas-kojbavveocoghhvaxhnnsdccem--
--upas-kojbavveocoghhvaxhnnsdccem--
from the back of the source and try again :)
the warnings that show up are simply sloppy programming :)
next reply other threads:[~2002-06-21 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 20:20 andrey mirtchovski [this message]
2002-06-21 19:33 ` Sam
-- strict thread matches above, loose matches on Subject: below --
2002-06-21 21:17 andrey mirtchovski
2002-06-21 20:21 Andrey S. Kukhar
2002-06-21 19:53 Andrey S. Kukhar
2002-06-21 19:20 Andrey S. Kukhar
[not found] <andrey@lanl.gov>
2002-06-21 18:43 ` andrey mirtchovski
2002-06-21 18:55 ` Scott Schwartz
2002-06-22 20:39 ` Sam
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=047076093ee1d5edf12d3ecd3523f147@acl.lanl.gov \
--to=andrey@lanl.gov \
--cc=9fans@cse.psu.edu \
--cc=plan9@kp.km.ua \
/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).