all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 34504@debbugs.gnu.org
Subject: bug#34504: 'pp' causally mentioned
Date: Mon, 18 Feb 2019 00:01:47 +0100	[thread overview]
Message-ID: <87tvh23tpg.fsf@web.de> (raw)
In-Reply-To: <87h8d2dzki.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Mon, 18 Feb 2019 02:45:01 +0800")

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

> MH> There's `pp-buffer'.  It's only a function, however.
> OK maybe tell the user to
> M-: (pp-buffer)    [eval-expression]
> C-x h              [mark-whole-buffer]
> <tab>              [indent-for-tab-command]
> Now one's lisp looks pretty good.

In some cases it looks prettier, but in others it looks uglier.  For
example

#+begin_src emacs-lisp
(let ((x 1) (y 2))
  (+ x y))

(defun f (n) (1+ n))
#+end_src

becomes

#+begin_src emacs-lisp
(let
    ((x 1)
     (y 2))
  (+ x y))
(defun f
    (n)
  (1+ n))
#+end_src

after your treatment.  Too many added line breaks for my gusto, but OTOH
the empty line between the two expressions has disappeared.

pp may be ok for improving how an evaluation result is presented to the
user, but it's IMHO by far not suitable for reformatting hand-written
code.


Michael.





  reply	other threads:[~2019-02-17 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 19:33 bug#34504: 'pp' causally mentioned 積丹尼 Dan Jacobson
2019-02-17 15:28 ` Eli Zaretskii
2019-02-17 15:37   ` 積丹尼 Dan Jacobson
2019-02-17 17:54     ` Michael Heerdegen
2019-02-17 18:45       ` 積丹尼 Dan Jacobson
2019-02-17 23:01         ` Michael Heerdegen [this message]
2019-02-18  2:03           ` 積丹尼 Dan Jacobson
2019-02-17 18:57     ` Eli Zaretskii
2019-09-16  3:03 ` Stefan Kangas

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=87tvh23tpg.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=34504@debbugs.gnu.org \
    --cc=jidanni@jidanni.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 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.