From: Daniel Pittman <slippycheeze@google.com>
To: Eric Lindblad <lindblad@gmx.com>
Cc: emacs-devel@gnu.org
Subject: Re: Elisp 9P?
Date: Tue, 8 Jan 2019 14:05:54 -0500 [thread overview]
Message-ID: <CAC45yQsqUCdEXCYraxDBZnL8Dg81U45hpXmpWyuBAQqVSOM_fg@mail.gmail.com> (raw)
In-Reply-To: <trinity-8f817bf2-96b1-491a-b5d7-c008bb4ec1e5-1545175701326@3c-app-mailcom-bs06>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
An extremely late response, I'm sorry, but: I think you are asking the
wrong question here. Instead of asking "would people be interested in the
protocol", ask "would people be interested in *what can be done because
Emacs supports* the protocol".
Beyond that, it might be a fun hack to add, but brings no real value; the
benefits come from the capabilities it brings.
(I also agree with 2017 RMS on the correct location for it.)
On Tue, Dec 18, 2018 at 7:07 PM Eric Lindblad <lindblad@gmx.com> wrote:
> Do you think GNU Emacs users would be interested in using 9P protocol from
> within the editor, implying an Emacs Lisp 9P Client/Server might be
> authored?
>
> http://9p.cat-v.org/implementations
>
> The 9p.scm (client) hyperlink in the above URL is dead, and it has a new
> home at the below URL.
>
> http://nurmi-labs.blogspot.com/p/9p-scheme.html
>
> Maybe other GNU Emacs users have another opinion to that of R. Stallman's
> (circa 2017) response which is reproduced below.
>
> "It makes no sense to put this feature into Emacs, which is the wrong
> place for it. The right place for it is in the kernel (Linux or the Hurd),
> so that all the application programs will be able to use it."
>
[-- Attachment #2: Type: text/html, Size: 1901 bytes --]
next prev parent reply other threads:[~2019-01-08 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 23:28 Elisp 9P? Eric Lindblad
2018-12-19 5:21 ` Paul Eggert
2018-12-19 13:54 ` Eric Lindblad
2019-01-08 19:05 ` Daniel Pittman [this message]
2019-01-23 13:50 ` Basil L. Contovounesios
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=CAC45yQsqUCdEXCYraxDBZnL8Dg81U45hpXmpWyuBAQqVSOM_fg@mail.gmail.com \
--to=slippycheeze@google.com \
--cc=emacs-devel@gnu.org \
--cc=lindblad@gmx.com \
/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).