From: Jim Kingdon <kingdon@panix.com>
To: xconq7@sources.redhat.com
Subject: Re: Xconq output files
Date: Mon, 06 Oct 2003 03:42:00 -0000 [thread overview]
Message-ID: <200310060224.h962OP704540@panix5.panix.com> (raw)
In-Reply-To: <l03130302bba3b97825ca@[212.181.162.155]> (message from Hans Ronne on Sun, 5 Oct 2003 23:27:52 +0200)
> And do we really need to put the scores files in a common place
> (/var/lib)?
Well, getting rid of this would remove the need for xconq to be
setgid, which would help with some of the known security holes.
I suppose there probably are people who like a common score file
(e.g. perhaps that ISP which has cconq installed). But I don't know
whether there this is strong enough to warrant keeping the feature.
> I think it would make sense to use the xcq extension only for files
> (game files) that can be opened by Xconq and the txt extension for all
> other text files.
I'm not sure which files this would change. Instead of txt, I might
just omit an extension (e.g. Xconq.Warnings rather than
Xconq.Warnings.txt). But the general idea sounds OK.
> * saved games, checkpoints and debug files all go into a "save" directory,
> either within the xconq top directory itself (Mac and Windows) or a visible
> $HOME/xconq directory on Unix.
I guess I'd put these in .xconq. It isn't really normal for an
application to hardcode the name of any directory not starting in ".".
next prev parent reply other threads:[~2003-10-06 2:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-05 21:47 Hans Ronne
2003-10-06 2:24 ` Peter Garrone
2003-10-06 3:42 ` Jim Kingdon [this message]
2003-10-07 3:28 ` Hans Ronne
2003-10-06 22:04 ` Eric McDonald
2003-11-23 20:12 ` Eric McDonald
2003-11-23 21:54 ` Hans Ronne
2003-11-24 0:26 ` Eric McDonald
2003-11-26 21:53 ` Hans Ronne
2003-11-26 22:56 ` Eric McDonald
2003-12-01 1:38 ` Hans Ronne
2003-11-24 1:25 ` Xconq testing: Win2K Erik Jessen
2003-11-24 2:16 ` Hans Ronne
2003-11-24 2:27 ` Erik Jessen
2003-11-25 1:47 ` Hans Ronne
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=200310060224.h962OP704540@panix5.panix.com \
--to=kingdon@panix.com \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).