all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: A femtolisp based emacs clone
Date: Fri, 26 Aug 2016 09:08:52 -0400	[thread overview]
Message-ID: <jwveg5bptqc.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <871t1cgcia.fsf@gmx.de> (Michael Albinus's message of "Fri, 26 Aug 2016 10:28:29 +0200")

> A while ago, Tramp has tried this approach, using the FISH protocol
> (<https://en.wikipedia.org/wiki/Files_transferred_over_shell_protocol>).
> Experience was bad wrt performance, so Tramp removed this protocol meanwhile.

I think the problem is round-trips, so the current
file-name-handler-alist operations just don't cut it.

We could either put higher-level ops in there (like `save-buffer'),
which implies replicating the whole `save-buffer' behavior, which is
a lot of work and likely to be not 100% faithful.

Or we could introduce new low-level ops that are asynchronous, and then
rewrite save-buffer to use them.  IOW save-buffer would start with
a bunch of calls like `start-getting-file-attributes' which could
immediately be passed on to the remote side, and later on checks the
return value of those calls as and when needed.


        Stefan



  reply	other threads:[~2016-08-26 13:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 20:15 A femtolisp based emacs clone edu500ac
2016-08-22  4:17 ` Gene
2016-08-22  5:22 ` Rusi
2016-08-22 21:32   ` edu500ac
2016-08-23  1:23     ` Thien-Thi Nguyen
2016-08-24  3:52     ` James K. Lowden
2016-08-24  4:35       ` Yuri Khan
2016-08-24 21:38       ` edu500ac
2016-08-25 12:28       ` Stefan Monnier
2016-08-26  8:28         ` Michael Albinus
2016-08-26 13:08           ` Stefan Monnier [this message]
2016-08-25 21:22       ` Ben Bacarisse

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

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

  git send-email \
    --in-reply-to=jwveg5bptqc.fsf-monnier+Inbox@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.