From: "Juanma Barranquero" <lekktu@gmail.com>
To: Nordlöw <per.nordlow@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Compacting calls to add-hook
Date: Thu, 3 Jul 2008 18:19:08 +0200 [thread overview]
Message-ID: <f7ccd24b0807030919r6c580023w5ab0688c1bff51c0@mail.gmail.com> (raw)
In-Reply-To: <794f0525-ad5e-472b-b450-797fbd4c23dd@m45g2000hsb.googlegroups.com>
On Thu, Jul 3, 2008 at 16:55, Nordlöw <per.nordlow@gmail.com> wrote:
> Can we make the following repetitive code more compact (perhaps using
> a map-function)?:
What do you mean, "can we"? It's trivial:
(let ((func (lambda () (outline-minor-mode 1))))
(dolist (hook '(c-mode-hook c++-mode-hook text-mode-hook
emacs-lisp-mode-hook sh-mode-hook octave-mode-hook
matlab-mode-hook help-mode-hook info-mode-hook))
(add-hook hook func)))
though I'm not sure that's optimizing for readability...
Juanma
prev parent reply other threads:[~2008-07-03 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 14:55 Compacting calls to add-hook Nordlöw
2008-07-03 15:55 ` weber
2008-07-03 16:19 ` Juanma Barranquero [this message]
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=f7ccd24b0807030919r6c580023w5ab0688c1bff51c0@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=per.nordlow@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.
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).