From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 11934@debbugs.gnu.org
Subject: bug#11934: 24.1; provide variable for pp.el to control max display width
Date: Fri, 29 Apr 2016 16:24:01 +0200 [thread overview]
Message-ID: <8737q47ata.fsf@gnus.org> (raw)
In-Reply-To: <87k2jg4i3j.fsf@web.de> (Michael Heerdegen's message of "Fri, 29 Apr 2016 16:14:56 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> But of course handling this problem is not trivial: we can't distinguish
> "simple lists" from code, and what might look good for the first might
> look weird for a macro call with a special lisp-indent-function value
> (e.g. imagine a `defun' call with a line break inserted just after
> "defun").
Well, pp isn't really designed for handling code. I pp'd a function at
random... it may be pretty, but it sure is unusual for code...
So I don't really think that's a consideration here.
(defun menu-bar-buffer-vector
(alist)
(let
((buffers-vec
(make-vector
(length alist)
nil))
(i
(length alist)))
(dolist
(pair alist)
(setq i
(1- i))
(aset buffers-vec i
(cons
(car pair)
`(lambda nil
(interactive)
(funcall menu-bar-select-buffer-function ,(cdr pair))))))
buffers-vec))
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-29 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 14:48 bug#11934: 24.1; provide variable for pp.el to control max display width Drew Adams
2016-04-28 15:53 ` Lars Ingebrigtsen
2016-04-29 14:14 ` Michael Heerdegen
2016-04-29 14:24 ` Lars Ingebrigtsen [this message]
2016-04-29 17:47 ` Drew Adams
2016-04-29 17:44 ` Drew Adams
2016-04-29 19:26 ` Michael Heerdegen
2016-04-29 19:37 ` Drew Adams
2021-11-05 14:27 ` Lars Ingebrigtsen
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=8737q47ata.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11934@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.