unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39081@debbugs.gnu.org
Subject: bug#39081: 26.3; Emacs hangs if external SCIM input method is killed
Date: Thu, 10 Dec 2020 17:45:29 +0800	[thread overview]
Message-ID: <87o8j2xafb.fsf@delllaptop.lockywolf.net> (raw)
In-Reply-To: <CA+A2iZazQQWe0pr6FzP1U_nyZVFypOAA1oV2Q+xWJLzXrD0kNw@mail.gmail.com>


I think, this is actually a SCIM bug.
At the moment, Slackware has decommissioned SCIM, and it was probably
the last distro using it.
I guess, this bug is no longer relevant.

Thanks,
Vlad

Vladimir Nikishkin <lockywolf@gmail.com> writes:

> Does Emacs have any deliberate support for SCIM. (Why should it?)
>
> Almost every other application simply ignores the crash. If input is
> requested again, SCIM daemon seems to get started on demand.
>
> Eli Zaretskii <eliz@gnu.org> 於 2020年1月14日 週二 23:52 寫道：
>
>> > From: Vladimir Nikishkin <lockywolf@gmail.com>
>> > Date: Tue, 14 Jan 2020 11:54:15 +0800
>> > Cc: 39081@debbugs.gnu.org
>> >
>> > This is the "crashed" trace. Note the GTK message in between.
>>
>> Thanks.  This seems to be an X error.
>>
>> And now I'm actually asking myself how reasonable is it to expect
>> Emacs to continue working when its IM service crashes.  Why is this a
>> use case we should support? does it happen a lot in practice.
>>
>> (I admit I know very little about the architecture of SCIM support in
>> Emacs, in terms of what OS services we use to communicate with it, and
>> thus I cannot reason about the difficulty in surviving SCIM crashes.
>> Does someone know?)
>>


-- 
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)





  reply	other threads:[~2020-12-10  9:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-11  5:52 bug#39081: 26.3; Emacs hangs if external SCIM input method is killed Vladimir Nikishkin
2020-01-11  8:03 ` Eli Zaretskii
2020-01-11  8:29   ` Vladimir Nikishkin
2020-01-11 10:05     ` Eli Zaretskii
2020-01-12  6:05       ` Vladimir Nikishkin
2020-01-12  6:34         ` Eli Zaretskii
2020-01-12  6:40           ` Vladimir Nikishkin
2020-01-12  6:49             ` Vladimir Nikishkin
2020-01-12 15:08               ` Eli Zaretskii
2020-01-13  0:03                 ` Vladimir Nikishkin
2020-01-14  3:54                   ` Vladimir Nikishkin
2020-01-14 15:53                     ` Eli Zaretskii
2020-01-14 16:24                       ` Vladimir Nikishkin
2020-12-10  9:45                         ` Vladimir Nikishkin [this message]
2020-12-10 10:29                           ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8j2xafb.fsf@delllaptop.lockywolf.net \
    --to=lockywolf@gmail.com \
    --cc=39081@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).