unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Barry Fishman <barry@ecubist.org>
To: emacs-tangents@gnu.org
Subject: Re: A simple(perhaps dumb) idea for a more responsive emacs
Date: Fri, 06 Oct 2023 18:00:35 -0400	[thread overview]
Message-ID: <7npm1r76nw.fsf@ecube.ecubist.org> (raw)
In-Reply-To: 83bkdc2vvq.fsf@gnu.org

On 2023-10-06 07:54:49 +03, Eli Zaretskii wrote:
>> From: Barry Fishman <barry@ecubist.org>
>> Date: Thu, 05 Oct 2023 17:34:01 -0400
>>
>> I was just suggesting that rather that waiting for some global solution
>> to be found, a less complex approach be considered in the mean time.
>> Where "pain points" could be considered a case by case basis, but still
>> provide a common mechanism to use.
>
> See, I'm not sure even this suggestion (that is already rather radical
> in its implications) will do.  Because, apart of buffers, we have the
> rest of the huge global state in Emacs, and Lisp programs are quite
> cavalier in relying on that, and there's a rare Lisp program in Emacs
> that doesn't access that global state in some way.  Something needs to
> be done about that as well.

[My ideas seem to fit well into the subject's simple (perhaps dumb)
category.  I hope I haven't outwore your patience.]

It would seem that "global state" is the thing that needs to be
dealt with first, when it comes to any thread based approaches in Emacs.

I was trying to start top down, identifying the "pain points",
and syntactically breaking them into a backgroundable, and
non-backgroundable parts.  It seems that approach can't work.

Alternative one can look at things bottom up, and propagate changes in
parts of the global state up the call stack.

In many languages that is done using an asynchronous function and
signaling protocol.

Implementing something like this in Emacs, and in a staged manner that
doesn't break existing code is something I would not propose without
doing a lot more thought and some actual example coding.

-- 
Barry Fishman



---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)

      reply	other threads:[~2023-10-06 22:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 16:03 A simple(perhaps dumb) idea for a more responsive emacs joakim
2023-10-04 17:21 ` Emanuel Berg
2023-10-05 12:49   ` Barry Fishman
2023-10-05 16:24     ` Eli Zaretskii
2023-10-05 21:34       ` Barry Fishman
2023-10-06  4:54         ` Eli Zaretskii
2023-10-06 22:00           ` Barry Fishman [this message]

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=7npm1r76nw.fsf@ecube.ecubist.org \
    --to=barry@ecubist.org \
    --cc=emacs-tangents@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. 
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).