unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Jambunathan K <kjambunathan@gmail.com>, 15233@debbugs.gnu.org
Subject: bug#15233: pp-eval-expression: Signature parity with `eval-expression'
Date: Sun, 1 Sep 2013 08:23:33 -0700 (PDT)	[thread overview]
Message-ID: <5d7b5260-afc2-44db-8e7f-7ee1fa70f239@default> (raw)
In-Reply-To: <871u58sq3l.fsf@gmail.com>

> eval-expression takes INSERT-VALUE.  But `pp-eval-expression' doesn't.
> But it should.

FWIW -

Done 5 years ago in pp+.el (and probably suggested to Emacs Dev as well).
http://www.emacswiki.org/emacs-en/download/pp%2b.el

Other pp+.el enhancements to `pp-eval-expression', which Emacs could
consider or integrate:

* Does not use 'emacs-lisp-mode-hook'.

* Fontifies the result buffer, `*Pp Eval Output*'.

* Makes several EmacsLisp keybindings available while reading the
  expression - uses a new keymap, 'pp-read-expression-map'.
  You can use: 
   'C-M-q' to indent a sexp
   'C-M-x' to eval a sexp
   'TAB' to Lisp-indent
   'M-TAB' to complete a Lisp symbol

* (With a prefix arg, inserts the pretty-printed result in the
  current buffer.)  With a negative prefix arg and a string result,
  inserts it without enclosing double-quotes (`"').

* Respects new options 'pp-eval-expression-print-length' and
  'pp-eval-expression-print-level', which control the print length
  and print level.  Respects 'eval-expression-debug-on-error'.


[FWIW2, I use (substitute-key-definition 'eval-expression
                                         'pp-eval-expression
                                         global-map).]





  parent reply	other threads:[~2013-09-01 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-01 12:06 bug#15233: pp-eval-expression: Signature parity with `eval-expression' Jambunathan K
2002-01-01  0:51 ` Jambunathan K
2013-09-01 15:23 ` Drew Adams [this message]
2013-09-01 16:07   ` Jambunathan K
2013-09-01 16:09   ` Jambunathan K
2013-09-03  1:44     ` Stefan Monnier
2013-09-03  2:20       ` Jambunathan K
2013-09-04 15:47         ` Josh

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=5d7b5260-afc2-44db-8e7f-7ee1fa70f239@default \
    --to=drew.adams@oracle.com \
    --cc=15233@debbugs.gnu.org \
    --cc=kjambunathan@gmail.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).