Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

X-Chat with parameters?

1 view
Skip to first unread message

Ziggy SpaceRat

unread,
Dec 20, 2003, 1:19:36 AM12/20/03
to
Hi Group!

Can anybody tell me if X-Chat accepts any paramaters?

I'm looking for a paramater like

-c|--config-dir=<Path>

to tell X-Chat not to use the default location for its configuration
files.

It would be helpful for having different configurations under the same
username, e.g. for testing purposes or to enable my girlfriend to use
X-Chat on my computer without having to use "Execute as" or
"Fast-user-switching", resp. "su girlfriend".

--
Bye
Ziggy SpaceRat

--
XChat-discuss: mailing list for XChat users
Archive: http://mail.nl.linux.org/xchat-discuss/

Peter Zelezny

unread,
Dec 20, 2003, 4:23:44 AM12/20/03
to
On Sat, 20 Dec 2003 07:19:36 +0100
Ziggy SpaceRat <Ziggy.S...@gmx.de> wrote:

> Hi Group!
>
> Can anybody tell me if X-Chat accepts any paramaters?

Yes it does.

$ xchat -h
xchat 2.0.6
Usage: xchat [OPTIONS]... [URL]

Options:
-d, --cfgdir DIRECTORY use a different config dir
-a, --no-auto don't auto connect
-n, --no-plugins don't auto load any plugins
-v, --version show version information

URL:
irc://server:port/channel

Ziggy SpaceRat

unread,
Dec 23, 2003, 6:04:16 PM12/23/03
to
Hi Tag Peter Zelezny,

am Samstag, 20. Dezember 2003 um 10:23 schrieben Sie:

>> Can anybody tell me if X-Chat accepts any paramaters?
> Yes it does.
> $ xchat -h

Was trying xchat --help

I love the consistency of *ix programs *g*

BTW: Does X-Chat support system-wide configs?
That means: Can I put a modified pevents.conf somewhere and X-Chat
will use it if no pevents.conf already exists in the user's
~/.xchat2 directory, or do I need to modify the sources for this?

pevents.conf is just an example, it should work for any config-file,
even partial ones.
So one could, for example, place a partial xchat.conf in

C:\Documents and settings\All Users\Application data\X-Chat 2
resp.
/etc/.xchat2

which contains the settings for DCC ports and stuff, so that users
don't need to care about figuring out which DCC ports work through the
system's firewall.

My idea would be to allow the config-files in the system-wide
config-dir to be named with .override at the end optionally, to
enforce certain options.
E.g. a cautious admin could enforce that the directory for incoming
DCCs is NUL: resp. /dev/null by placing an

xchat.conf.override

with this content

dcc_dir = /dev/null

in the system-wide config dir and no user could change this setting in
his xchat later, while the options in

xchat.conf within the system-wide config-dir

tab_chans = 1
tab_dialogs = 1
tab_dnd = 1
tab_new_to_front = 0
tab_notices = 0
tab_position = 1
tab_server = 0
tab_trunc = 20
tab_utils = 1

would just be suggestions and can be changed by the users later.

--
Mit freundlichen Grüssen
Ziggy SpaceRat

0 new messages