all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: dick <dick.r.chiang@gmail.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Access control in Emacs?
Date: Tue, 14 Sep 2021 18:02:16 +0200	[thread overview]
Message-ID: <CADwFkmn1JKauXxyf1=gfJaDyHmZVfCPeVW5GHUxMdCbmcsgv4g@mail.gmail.com> (raw)
In-Reply-To: <87zgsff93x.fsf@dick>

dick <dick.r.chiang@gmail.com> writes:
>
> > I don’t think UNIX is a good multi-user OS — Elisp will do much better.
>
> User programs live in n-dimensions, and the OS is (n+1)-dimensional.  Emacs,
> being a user program, cannot conceive of, much less create, an OS.

May I suggest that you indicate when you leave something out from a
quote with "[...]"?  In this case, your way of quoting makes it look
like something rather different from what was originally written: "I
don’t think UNIX is a particularly good multi-user OS — the access
control model is arbitrary and coarse grain. There’re improvements
like SELinux, but a CLOS generic function in Elisp will do much
better."

In other words, the author is saying that Elisp would be better for
implementing access control, not for implementing an OS.



  reply	other threads:[~2021-09-14 16:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 12:49 Access control in Emacs? Qiantan Hong
2021-09-14 14:09 ` Phil Sainty
2021-09-14 14:28 ` dick
2021-09-14 15:05   ` Qiantan Hong
2021-09-14 15:52     ` dick
2021-09-14 16:02       ` Stefan Kangas [this message]
2021-09-14 14:49 ` Stefan Monnier
2021-09-15 20:11   ` Richard Stallman
2021-09-15 20:21   ` Robin Tarsiger
2021-09-14 18:13 ` Christine Lemmer-Webber
2021-09-14 19:59   ` tomas
2021-09-15 23:16   ` Qiantan Hong
2021-09-16  2:16     ` Christine Lemmer-Webber
2021-09-18  0:29       ` Richard Stallman

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='CADwFkmn1JKauXxyf1=gfJaDyHmZVfCPeVW5GHUxMdCbmcsgv4g@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=dick.r.chiang@gmail.com \
    --cc=emacs-devel@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.
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.