From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: expressions
Date: Sun, 05 Jan 2003 13:34:13 -0500 [thread overview]
Message-ID: <E18VFbB-0008Tm-00@fencepost.gnu.org> (raw)
In-Reply-To: <E18UCGO-0002vU-00@snap.thunk.org> (tytso@mit.edu)
This is a useful feature. I have a security question for the people
on emacs-devel who support non-GNU-like platforms. server.el sets up
mode 0700 for the socket. Is that sufficient security, on all
platforms, to make it safe to install this feature?
In practice I don't
expect this to be a problem, although if this is a major concern, a
option such as --lisp could be added to emacsclient to inhibit adding
the absolute pathname to the argument, instead of always treating
arguments that begin with an open parenthesis as LISP expressions.
Perhaps there should be an option --file that forces an argument to be
treated as a file even if it starts with open-paren. Scripts could
use that; meanwhile, interactive use would remain maximally convenient.
next parent reply other threads:[~2003-01-05 18:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18UCGO-0002vU-00@snap.thunk.org>
2003-01-05 18:34 ` Richard Stallman [this message]
2003-01-05 19:55 ` expressions Bob Halley
2003-01-06 0:49 ` expressions Kim F. Storm
2003-01-06 1:55 ` expressions Bob Halley
2003-01-06 20:06 ` expressions chad
2003-01-06 20:32 ` expressions Bob Halley
2003-01-07 10:11 ` expressions Kim F. Storm
2003-01-07 19:23 ` expressions Luc Teirlinck
2003-01-11 19:48 ` expressions Stefan Monnier
2003-01-07 10:14 ` expressions Kai Großjohann
2003-01-06 17:13 ` expressions Richard Stallman
2003-01-06 20:37 ` expressions Bob Halley
2003-01-08 21:00 ` expressions Andreas Schwab
2003-01-07 11:53 ` expressions Theodore Ts'o
2003-01-08 8:00 ` expressions Richard Stallman
2003-01-11 19:47 ` expressions Stefan Monnier
2003-01-08 13:50 ` Suggested enhancement: allow emacsclient to send arbitrary LISP expressions Kim F. Storm
2003-01-09 23:13 ` Richard Stallman
2003-01-13 21:08 ` Theodore Ts'o
2003-01-14 18:55 ` 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
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=E18VFbB-0008Tm-00@fencepost.gnu.org \
--to=rms@gnu.org \
--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 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).