unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 19362@debbugs.gnu.org
Subject: bug#19362: 25.0.50; Fix `pp.el' in line with new `elisp-mode.el'
Date: Sat, 30 Apr 2016 18:26:03 +0200	[thread overview]
Message-ID: <87h9ejkqqs.fsf@gnus.org> (raw)
In-Reply-To: <7cb215b9-a70d-472a-ba85-15a9bc613a5e@default> (Drew Adams's message of "Fri, 12 Dec 2014 18:46:39 -0800 (PST)")

Drew Adams <drew.adams@oracle.com> writes:

> Library `elisp-mode.el' was added after Emacs 24.4.  Prior to that,
> functions such as `pp-eval-last-sexp' were aligned with the non-pp
> sister functions from `lisp-mode.el', such as `eval-last-sexp'.
>
> This is no longer the case.  Please bring `pp.el' up to be parallel with
> the behavior of `elisp-mode.el', just as it was parallel with the same
> and similar code that was previously in `lisp-mode.el'.
>
> In particular, `pp-eval-last-sexp' had the same evaluation behavior as
> `eval-lisp-mode'.  The addition of pretty-printing was pretty much the
> only difference.  The two no longer correspond.  Please fix this
> disparity.

What are the differences you think should be fixed?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2016-04-30 16:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13  2:46 bug#19362: 25.0.50; Fix `pp.el' in line with new `elisp-mode.el' Drew Adams
2016-04-30 16:26 ` Lars Ingebrigtsen [this message]
2016-04-30 17:36   ` Drew Adams
2016-04-30 17:43     ` Lars Ingebrigtsen
2016-04-30 18:16       ` Drew Adams
2016-04-30 18:33         ` Lars Ingebrigtsen
2016-07-01  2:04         ` npostavs
2016-07-01  3:07           ` Drew Adams
2016-07-06 20:39             ` Noam Postavsky
2016-07-06 22:35               ` Drew Adams
2016-07-06 23:36                 ` Noam Postavsky
2016-07-06 23:51                   ` Drew Adams
2016-07-07  0:26                     ` npostavs
2016-07-07  2:34                       ` Drew Adams

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=87h9ejkqqs.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=19362@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).