SILC Client 1.0.1

The new version of the SILC Client is now available!  The source package
of the software is available from the following sources:

        http://silcnet.org/
        ftp://ftp.silcnet.org/

The SILC Client 1.0.1, has been released.  This release fixes several
minor bugs and inconveniences found since SILC Client 1.0 release.

When you are upgrading from a prior release to SILC Client 1.0.1, there
are two issues you have to take special care of:

First of all the default theme (as defined in the file default.theme in
the source package) has changed. You may need to update your personal
theme to reflect those changes. The second change affects the filename
used to store the session data when /DETACH'ing. If you have detached
from a SILC network with your old client and want to resume the session
with SILC Client 1.0.1, you first have to

	/SET session_filename session

After successfully resuming your session, you can revert the setting to
its default "session.$chatnet" again.

Summary of Changes
------------------

o /NOTICE and /ACTION command now both take a mandatory target argument
  and an option -sign flag.  Both work in channels and queries, /IGNORE
  now correctly treats both.  default.theme has changed, please update
  your theme.  Closes #1.

o /SILCNET [ADD|REMOVE|LIST] command to manage different SILC networks.

o /SMSG and /MMSG now correctly open new query windows if wished.

o New settings session_filename defines the filename used to store
  session information generated by /DETACH.  A setting like
  session.$chatnet allows you to detach from different networks.

The full list of changes is available on the website and in CHANGES file
in the source package.


Installation
------------

The source package is compiled and installed as instructed in the INSTALL
file found from the package.  Quick installation:

  ./configure
  make
  make install


Known Issues
------------

- Known Issues in SILC Client

  - It is possible that some times the user list is not printed or is
    printed as incomplete when joining to a channel.  This is due to a
    failure in the user resolvings and can happen for example when some
    user quits the network at the same time you join the channel.  In
    this case the failure of the resolving may leave the user list
    printing incomplete.

  - It is possible that some notifications, such as channel join,
    are not delivered to user interface due to same resolving reason as
    described above.

kind regards
-- jochen

_________________________________________________________
Info:    http://lists.silcnet.org/listinfo/silc-announce
Archive: http://lists.silcnet.org/pipermail/silc-announce
FAQ:     http://silcnet.org/?page=faq