[SCIM] Re: skim 1.0.0 released

[LiuCougar]

On Mon, 20 Sep 2004 21:48:25 +0200, Mike FABIAN <mfabian at suse.de> wrote:
> (skim-1.0.0 CVS head from 20040913).
> 
> Adrian Schröter (CC:, SuSE's KDE package maintainer) want's to start
> skim via the KDE-Autostart mechanism. He made the attached patch for
> skim.
> 
> When using skim with that patch, the line "skim -d" should not be
> executed in ~/.xim if KDE is started, one should wait for the
> autostart mechanism of KDE to do the work instead and set only the
> environment variables above. The ~/.xim file I posted to this mailing
> list recently does that.
Thanks for the patch. I think that with this patch applied, the KDE
will always start skim when skimrc exist in the user's setting dir. Am
I right?

> In that case, the dcop server error message does *not* happen.
> 
> But, if one has a xterm open and restarts KDE, the session
> management will start the xterm again when logging into KDE again.
> Input with skim into that xterm will not work, apparently because
> this xterm starts fast and is started *before* skim is running.
> 
> Starting another xterm when the full KDE session including skim is
> already running is OK, in that xterm the input will work, but not in
> the first xterm which was brought up by the session management.
I just do not know why in SuSE the dcop error occurs. What's the
version of KDE and Qt in SuSE? (I am using 3.3.0).

Regards,
-- 
"People's characters are strengthened through struggle against
difficulties; they are weakened by comfort."
- Old Chinese adage