From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Ivan Yonchovski Newsgroups: gmane.emacs.bugs Subject: bug#42028: [Feature Request] 27.0.91; Provide the ability dynamic modules to post events in emacs event loop Date: Wed, 24 Jun 2020 21:38:31 +0300 Message-ID: <87eeq4fgwo.fsf@gmail.com> References: <875zbh0wbf.fsf@gmail.com> <83bll8ttet.fsf@gnu.org> <83366ktol5.fsf@gnu.org> <83zh8ss87t.fsf@gnu.org> <874kr0gyhi.fsf@gmail.com> <83y2ocs5kr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="53887"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.3.7; emacs 27.0.91 Cc: 42028@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jun 24 20:39:12 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1joAIh-000Dtb-3c for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 24 Jun 2020 20:39:11 +0200 Original-Received: from localhost ([::1]:59968 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1joAIg-0000d5-37 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 24 Jun 2020 14:39:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57638) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1joAIY-0000ch-25 for bug-gnu-emacs@gnu.org; Wed, 24 Jun 2020 14:39:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55690) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1joAIX-0004MC-Os for bug-gnu-emacs@gnu.org; Wed, 24 Jun 2020 14:39:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1joAIX-00027U-Lc for bug-gnu-emacs@gnu.org; Wed, 24 Jun 2020 14:39:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ivan Yonchovski Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 24 Jun 2020 18:39:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 42028 X-GNU-PR-Package: emacs Original-Received: via spool by 42028-submit@debbugs.gnu.org id=B42028.15930239218121 (code B ref 42028); Wed, 24 Jun 2020 18:39:01 +0000 Original-Received: (at 42028) by debbugs.gnu.org; 24 Jun 2020 18:38:41 +0000 Original-Received: from localhost ([127.0.0.1]:39003 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1joAID-00026u-G3 for submit@debbugs.gnu.org; Wed, 24 Jun 2020 14:38:41 -0400 Original-Received: from mail-wr1-f51.google.com ([209.85.221.51]:35681) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1joAIB-00026h-NN for 42028@debbugs.gnu.org; Wed, 24 Jun 2020 14:38:40 -0400 Original-Received: by mail-wr1-f51.google.com with SMTP id g18so3299023wrm.2 for <42028@debbugs.gnu.org>; Wed, 24 Jun 2020 11:38:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=wHck0mTFo/puF8WqyTp12OtABKTN47zw/abUwF2m440=; b=FrL6FMq0nQmRoO3eD9e/fmHHIkNYyVM4ncqJnxb+kZciPpDE4IjYk0STo2VF5UU7az I02IxbnzDfR0Q/llbZJISVzgNLL8+/YZNA+sMujf+LVRu8wf/94+10HDKmGkDFPoO/j2 klr2kT88IiNf/UR4OyJJF7X8Th7PAVnmc7X68J9johtxZMB4CzURK/1Rj8xKju1OReHA H172JyN1fU+N6u631mUt+AwcY36a3JnuMpfombUn7hFYst3TBqEVZaZYAuYCp+YloTxl FU31+CYqZc0jI4BfvcKSJDc9RsVdLjLfnZgz/dqvfQ4qrrzlV9MyAG/RKbrn5XEl1HAh iBCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=wHck0mTFo/puF8WqyTp12OtABKTN47zw/abUwF2m440=; b=ijsm7hw6N8k65vykqhHExIg1CyYB0hOy4fV/kEdNmrU2eotEzwun09rmMGejhL6/3J SuNqhr7aTsm6cRzhrhdAjK7Hg1m0BmcmxhFuWQqfPRDHsFKz5lIJvM/cQVfMrg5hfU2K yzkr4eqwGGlpV44ByHAxByOgI2oSRF6NGR4skDEkOCupzdv5RXVmbAUAybl6IdrsNN/K IUmhkkMUpEipJtLTEwQcL+ksdrmbAG+YdCZ4mIUqF+xKIlq0FypmCuWNkVuU9dGe6atq cp2M8ewJtumPRepcC9cb9SDoEc21y5zcRysfCqMXuwFc8Q7qPhzi5ywEl3HMp9eaSprN CFzw== X-Gm-Message-State: AOAM5305iEZ0fHQivDEcFxbUAGdtyL4c53fYkia4bqQHyNtVHF8wZdrd iHwa727s0/myKh/sB2NTTYpdIrAg X-Google-Smtp-Source: ABdhPJyRjcSxK65ntjkoEgv1McNzxIkYq9RCQLqiMu1B+36BDMr01cedEK832gQvZrGz8H2z7C1DGA== X-Received: by 2002:adf:f711:: with SMTP id r17mr33250779wrp.409.1593023913306; Wed, 24 Jun 2020 11:38:33 -0700 (PDT) Original-Received: from kyoncho-H87-D3H ([2a00:4802:28d:9e00:8c64:bcc8:970f:40b]) by smtp.gmail.com with ESMTPSA id p25sm8946806wmg.39.2020.06.24.11.38.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 24 Jun 2020 11:38:32 -0700 (PDT) In-reply-to: <83y2ocs5kr.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:182357 Archived-At: Eli Zaretskii writes: > > Your feature just asked for a way to queue events, it didn't say > anything about doing that asynchronously, not from a function invoked > by the main thread. If you mean the latter, then it AFAIU would need > a serious redesign of the Emacs event queue, to make it accessible > from several threads running in parallel at once. Yes, sorry about that. I didn't mention it explicitly in the bug report it was described in more details in the linked article. > What you describe is very different from how JIT font-lock works now. > Which is why I asked the question: I know (more or less) how it works > in other editors, I just don't yet understand well enough how > something like that would fit into the existing fontification > framework. I hope there is a way of fitting it, because otherwise it > would mean a serious surgery of the display engine as well, which will > make the job significantly larger and harder. IMO we are good here. At least on lsp-mode side we were able to implement delayed semantic fontification as a result of async source. But in lsp-mode case we are reseiving the messages from the server on the UI thread. Thanks, Ivan