1. I get this error: /bin/sh: no: command not found
2. Why doesn't ./configure find GTK+ on my FreeBSD system?
3. How do I compile X-Chat on my Sun OS system?
1. How do I enable identd in X-Chat? (How do I get rid of the ~ infront of my username?)
2. How do I auto join more than one channel with keys?
3. How do I autoconnect and join a channel when X-Chat loads?
4. How do I cut and paste in X-Chat?
5. How do I connect through a proxy?
6. Why does X-Chat open a listen port?
7. Why is the "Tint Transparency" option shaded out?
8. How do I set different ban types?
9. Why can't I see accented-letters/umlauts/upper-ascii-chars in X-Chat?
10. Why does the timestamp overlap some nicknames?
11. How do I turn on Conference mode where I will not see join or part messages?
12. How can I run the /dccserver command?
13. Why doesn't DCC send work behind IPNat or IPMasq?
14. How do I execute multiple commands in one line?
1. Why does X-Chat leak so much memory?
2. My copy of X-Chat crashes, what can I do?
If you get an error something like:
Making all in po make[2]: Entering directory `/home/zed/xchat/files/xchat-1.8.7/po' file=./`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=../src:$PATH no -o $file ca.po /bin/sh: no: command not found make[2]: *** [ca.gmo] Error 127 make[2]: Leaving directory `/home/zed/xchat/files/xchat-1.8.7/po' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/zed/xchat/files/xchat-1.8.7' make: *** [all-recursive-am] Error 2
It means you don't have GNU gettext installed. There are two solutions:
FreeBSD usually comes with glib12-config and gtk12-config, so you'll need to set the GLIB_CONFIG and GTK_CONFIG environment variables, e.g:
setenv GLIB_CONFIG /usr/local/bin/glib12-config
setenv GTK_CONFIG /usr/X11R6/bin/gtk12-config
rm config.cache
./configure
Or if you are using a bash shell:
export GLIB_CONFIG=/usr/local/bin/glib12-config
export GTK_CONFIG=/usr/X11R6/bin/gtk12-config
rm config.cache
./configure
X-Chat uses GNU gettext which in turn requires gmake, either install that and or use ./configure --disable-nls with Sun's own make.
UNIX:
Identd isn't actually apart of X-Chat. You will need to download and install
your own ident server. Most distributions, including RedHat, come with an
ident server program called pidentd. Make sure it is enabled in
/etc/xinetd.conf or read you distribution's documentation.
As an alternative, you can try this experimental identd server: xchat_auth
WINDOWS:
The win32 version of X-Chat comes with a builtin identd server. It is
enabled by default, but can be disabled with /set identd 0.
In the Serverlist's channel column enter multiple channels and separate them by commas, eg: "#linux,#warez,#chat". Do not put spaces between the channels. If the channels also have keys (passwords), then the syntax is: "#channel1,#channel2,#channel3 key1,key2,key3"
Example: If you want to join #abc and #talk without keys, but #linux with a key of "secret", you would enter: "#linux,#abc,#talk secret".
In the Serverlist's Edit Window, check the checkbox "Autoconnect" of the entries you want to auto-connect/join. When you restart xchat it should automatically connect to these servers, and join the channels.
It's exactly the same as any other X application. You simply mark the text you want, and then press middle mouse button to paste (if you only have a 2 button mouse, press left and right buttons at once).
Go to the menus, Settings -> Preferences -> Network Setup and fill in the requested information there. There is currently no support for using a username and password to authenticate to proxies.
Normally, X-Chat will not open a listen port, unless you are offering a file by DCC. If you compiled X-Chat with the --enable-panel option, ORBit (a library that is apart of Gnome) will open a port. X-Chat cannot prevent this. If it really bothers you, compile X-Chat with --disable-panel.
It means you've compiled without gdk-pixbuf available. The configure script looks for gdk-pixbuf-config to find out if you have it installed. On a redhat or mandrake system you should have something like:
$ rpm -qa | grep gdk-pix gdk-pixbuf-0.11.0 gdk-pixbuf-devel-0.11.0
The "devel" package is also necessary! You should be able to find these packages on your Linux CDROM or local GNOME ftp site. Once you install gdk-pixbuf, try recompiling xchat.
Three ways:
Version 1.8: Firstly, you should disable fontsets. The setting is in Settings -> Setup -> Channel Windows -> Use a FontSet. There is no reason to have this setting ON, unless you know you need it. Some versions of X-Chat require a restart for this setting to take affect. If that doesn't fix the problem, try using a different font, some fonts simply don't have the characters you want.
Version 2.0: Refer to http://xchat.org/encoding.html. Note: Log files are written in UTF-8/Unicode.
Some networks allow very long nicknames (up to 32 letters). It can be annoying to have the separator bar move too far to the right, just for one long nick. Therefore, it has a set limit for the distance it will move to the right. If you use a large font, you may need to adjust this distance. It is set in pixels, for example:
/set max_auto_indent 320
Once you adjust this setting high enough, overlapping timestamps and nicknames should not occur. The adjustment will not take effect immediately, a restart may be needed.
Version 1.8:
At the bottom right of the X-Chat screen there is a "<" button.
Click that then also click the "Conf" button that will pop up.
Version 2.0.1+:
Right-click on the tab you want to change. In the submenu of the channel
name, there's a toggle-item "Show join/part messages", simply turn this off.
In short you can not do this (easily). This is a mIRC only propriotory feature that is quite nonstandard. There is no code for doing this, mainly because /dccserver runs on port 59 which in turn would require running X-Chat as root. Why do you need this anyway? Just use normal DCC.
If you are behind a IP-NAT or IP-Masqeraude system, you will most likely have an address like 192.168.0.0. This address is not useable on the internet, and must be translated.
When offering a DCC file, xchat will tell the receiver your address. If it says 192.168.0.0, the receiver will not be able to connect. One way to make it send your "real" address is to enable the "Get my IP from IRC Server" option in xchat. In version 2.0, it's available in Prefereces -> File Transfers. When you turn this option ON, you will have to relogin to the server before it'll take effect.
There are two ways to do this:
The simple answer is, it doesn't! There are some GTK+ pixmap based themes around that leak alot of memory. Please try using a different theme and see if that resolves the problem. X-Chat itself only allocates about 40kb of memory through malloc()!
Firstly, make sure it's the latest stable version of X-Chat. Stable versions have an EVEN middle number, e.g.: 2.0.1 or 2.0.2. Often late fixes are placed in this directory: 2.0.x patches
If you still experience crashes, you should consider running it through GDB. This will help us find a fix quickly, and it's easy to do! See here.