unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Emacs discussions <emacs-devel@gnu.org>
Cc: Matthew Dempsky <matthew@dempsky.org>
Subject: Re: Codifications of rules
Date: Mon, 07 Dec 2009 20:57:43 -0500	[thread overview]
Message-ID: <jwvhbs2i685.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <C97ECBDF-941B-48C5-91AE-9A2BB9AA70B9@gmail.com> (David Reitter's message of "Mon, 7 Dec 2009 15:56:54 -0500")

> - Executing / evaluating a line or an expression or a region with the
> inferior process, e.g. C-x C-e in Elisp and in SLIME's lisp-mode, but
> C-j (for the line) in R-mode (ESS).   Then, SLIME and Python-mode have
> C-c C-r to evaluate the region, but emacs-lisp-mode doesn't have that.

This does indeed point to one missing functionality:
an "inferior-comint-minor-mode".  I.e. a minor to use in source code
buffers that provides the usual bindings to send commands to some
underlying comint buffer (like C-c C-l).

> - Running the inferior interpreter process.  M-x R in ESS, M-x slime
> in SLIME (rather than M-x lisp), and M-x run-python (rather than M-x
> python) in python-mode.

M-x run-<foo> is the standard name used.  I don't love it because it
breaks the "prefix all functions" convention, but it's been around for
a long time.


        Stefan




  parent reply	other threads:[~2009-12-08  1:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 19:55 Codifications of rules (was Re: bug#5119: ruby-mode binds TAB) Matthew Dempsky
2009-12-07 20:56 ` David Reitter
2009-12-08  1:23   ` Stephen J. Turnbull
2009-12-08  2:03     ` Codifications of rules Stefan Monnier
2009-12-08  5:00     ` Codifications of rules (was Re: bug#5119: ruby-mode binds TAB) David Reitter
2009-12-08  1:57   ` Stefan Monnier [this message]
2009-12-07 21:37 ` Codifications of rules Stefan Monnier
2009-12-07 22:13   ` Matthew Dempsky
2009-12-08  0:03   ` Eric M. Ludlam

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=jwvhbs2i685.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=matthew@dempsky.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).