Q1.  I noticed that QuIRC isn't compliant to the CTCP specification.  What are
     you going to do about it?  In what ways is QuIRC not compliant?

A1.  QuIRC does not do CTCP or low level quoting (ie. \a or ^Pn).  Seeing as I
     don't know of any other client that does this either, it would be silly to
     put this in.  There is another issue with FINGER in where the spec
     conflicts with itself in first saying that the FINGER reply should not
     contain spaces, and then gives an example where the reply does contain
     spaces.  What do I plan to do about it? Well, since I can't do anything
     about all the other clients, and the other error appears to be a typo,
     I do not plan to "fix" QuIRC cause that would make it incompatible with
     the rest.  Besides, you can always script your own replies.  In creating
     the replies for QuIRC, I consulted the spec as well as the replies of 
     other clients.  What I discovered was that almost no clients actually
     reply according to the spec.  So, instead of conforming precisely to the
     spec and creating less informative replies, I decided to go with the flow
     and just stick with the general idea behind the reply, not the exact 
     syntax.  The replies correspond more with ircii than the CTCP spec.


Q2.  When I try to start QuIRC, I get an error relating to being unable to
     initialize the Tcl/Tk interpreter.  What are possible causes or solutions?

A2.  Make sure you have the Tcl/Tk libraries (for the appropriate version!)
     installed on your system.  To assist QuIRC in locating these if it cannot
     find them at the standard locations, you can set the TCL_LIBRARY and
     TK_LIBRARY environment variables.  Another possibility is that Tk cannot
     find a valid display to display the client on.  Check your DISPLAY
     environment variable and make sure you have permissions to use the screen
     it points to (xhost will change permissions).  Any messages about being
     unable to init the Tcl/Tk interpreter are practically gauranteed to be
     related to only to the Tcl/Tk installation itself.  Example:

	export TCL_LIBRARY="/usr/lib/tcl8.0"
	export TK_LIBRARY="/usr/lib/tk8.0"


Q3.  Help!  QuIRC is such a memory hog!

A3.  Turn off do_rawview and turn on scrollback buffer size limiting.  The
     scrollback buffers are what really consume memory.


Q4.  QuIRC appears to freeze for a while when I start a new server, what is
     going on?

A4.  Since QuIRC does not presently do non-blocking name lookups, it has to
     wait for a response from the DNS.  While it is waiting, the client is
     non-responsive.


Q5.  I get an error similar to the following in one of my scripts:
  ERROR  Info:
syntax error in expression "0|NOTIFY_TAG_923349433.133047"
    while executing
"expr [set ::internal::complete70]|[set ::internal::tempcomplete70]"
    ("foreach" body line 5)
    invoked from within
"foreach script $::0::scripts {
      if { [info commands ::0::${script}::event_pong]!="" } {
        set ::internal::tempcomplete70 [::0::${script}::e..."
  ERROR  Code: NONE
  ERROR  Additional Info: File: server.cc Line: 147

A5.  Be sure to return a numeric value from your events.  Simply return 0 if
     you don't want it to affect anything else.


Q6.  Help!  My server won't close!

A6.  Make sure there are no remaining DCC entries in the DCC list by right
     clicking in the window to remove them.


Q7.  Feature "X" is missing after upgrade, or things seem broken... what can I
     do?

A7.  Some people have been having problems with features being missing after
     upgrading QuIRC.  If you have gone through the QuIRC install and still
     have problems, you can run quirc -i and choose the Easy install which
     should work every time.  If that doesn't work, there is either a problem
     with the install or a bug in QuIRC.  Try finding all occurences of "quirc"
     in your filesystem and removing them.  If that doesn't work, let me know
     what the problem is and I'll look into it.
