unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: joakim@verona.se
To: emacs-tangents@gnu.org
Subject: A simple(perhaps dumb) idea for a more responsive emacs
Date: Wed, 04 Oct 2023 18:03:37 +0200	[thread overview]
Message-ID: <87zg0ys7c6.fsf@tanaka.verona.se> (raw)

Hello,

Theres been a lot of talk about multi core emacs etc, and thats nice and
all, but difficult to do.

So another idea is this:

- You have a single Emacs instance, you do everything in it, but you get
  sad when a long running operation, in this case Gnus, or generating
  your Org agenda, takes a long time, and you have to wait.

- You start 2 or three emacsen for different purposes, but then you get
  sad because you dont have the same state in all emacsen

- You could have the main emacs communicate with the different special
  purpose emacs using some async option, and that would work, but this
  is a different idea

- You could also use CRDT:s to communicate with the special purpose
  emacsen. There is a crdt emacs package already. In this case, mainly
  the gnus window gets replicated to the main emacs from the gnus emacs.

You could presumably use the crdt for replicating lisp structures,
not just the buffer. A crdt is just a data structure after all.

Anyway, just tossing out an idea.
-- 
Joakim Verona
joakim@verona.se

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

             reply	other threads:[~2023-10-04 16:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 16:03 joakim [this message]
2023-10-04 17:21 ` A simple(perhaps dumb) idea for a more responsive emacs 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

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=87zg0ys7c6.fsf@tanaka.verona.se \
    --to=joakim@verona.se \
    --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).