From: Jeremy Maitin-Shepard <jeremy@jeremyms.com>
To: David Kastrup <dak@gnu.org>
Cc: Juri Linkov <juri@jurta.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: --eval
Date: Sun, 22 Jul 2007 12:25:24 -0400 [thread overview]
Message-ID: <877ioso16z.fsf@jbms.ath.cx> (raw)
In-Reply-To: <851wf1sgmv.fsf@lola.goethe.zz> (David Kastrup's message of "Sat\, 21 Jul 2007 21\:26\:00 +0200")
David Kastrup <dak@gnu.org> writes:
> Juri Linkov <juri@jurta.org> writes:
>>> Uh, -f was a typo. I really meant --eval in my example.
>>
>> BTW, a pity that Emacs doesn't provide a short option for the `--eval'
>> command line argument!
>>
>> By analogy with `--funcall' that have the corresponding `-f',
>> the short option for `--eval' and `--execute' would be `-e'.
>>
>> Even though startup.el currently treats `-e' as a shorthand of `-funcall',
>> it seems that such use of `-e' is obsolete and we are free to reassign it
>> to `--eval' and `--execute' because the manual doesn't document it:
> Deprecating -e is ok with me, but a potentially dangerous command may
> well be spelled explicitly.
Potentially dangerous? Evaluating is hardly something that is
safe-guarded anywhere in emacs. Furthermore, unlike a key binding that
might accidentally be hit and do something unexpected, it is highly
unlikely to perform some harmful action when something completely
different was intended.
Most importantly, if -e is typed by mistake, the argument will almost
certain not be a valid lisp expression, and even if it is, it almost
certainly won't be a lisp expression that results in a function call.
--
Jeremy Maitin-Shepard
next prev parent reply other threads:[~2007-07-22 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 13:12 emacsclient proposal David Kastrup
2007-07-19 17:36 ` Stefan Monnier
2007-07-19 17:58 ` David Kastrup
2007-07-20 2:42 ` dhruva
2007-07-21 18:34 ` --eval (was: emacsclient proposal) Juri Linkov
2007-07-21 19:26 ` --eval David Kastrup
2007-07-22 16:25 ` Jeremy Maitin-Shepard [this message]
2007-07-22 18:37 ` --eval 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=877ioso16z.fsf@jbms.ath.cx \
--to=jeremy@jeremyms.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=monnier@iro.umontreal.ca \
/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.