[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34504: 'pp' causally mentioned
From: |
Michael Heerdegen |
Subject: |
bug#34504: 'pp' causally mentioned |
Date: |
Mon, 18 Feb 2019 00:01:47 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
積丹尼 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.