From: Drew Adams <drew.adams@oracle.com>
To: "Michael Heerdegen" <michael_heerdegen@web.de>,
"積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 38818@debbugs.gnu.org
Subject: bug#38818: Dired: mention deleting buffers, not just windows
Date: Tue, 31 Dec 2019 22:53:22 -0800 (PST) [thread overview]
Message-ID: <d8c494db-5335-4767-9b46-91d2a01828ea@default> (raw)
In-Reply-To: <87woabd9oc.fsf@web.de>
> Using lambdas should be ok most of the time. But there's a certain
> risk
> of unintentionally having two copies of a function in a hook when the
> code is executed multiple times, e.g. if you load your init file twice,
> once compiled, and once the lisp source, because `add-hook' then can't
> know that it's the same function. Most of the time even this has no
> visible effect, but when it has, it can be surprising and finding the
> cause can be hard, so I try to just avoid adding lambdas to hooks in my
> init file.
Also, if you're testing stuff and you add a lambda
form to a hook, and later you want to remove it,
you need to use exactly the same text - same
whitespace, everything. The lambda form is taken,
in effect, as text, and it looks for an exact
textual match.
It's very good to get in the habit of not using
lambdas on hooks.
next prev parent reply other threads:[~2020-01-01 6:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 16:09 bug#38818: Dired: mention deleting buffers, not just windows 積丹尼 Dan Jacobson
2019-12-30 17:53 ` martin rudalics
2019-12-30 18:11 ` 積丹尼 Dan Jacobson
2019-12-31 7:59 ` martin rudalics
2019-12-31 17:33 ` Michael Heerdegen
2020-01-01 2:14 ` 積丹尼 Dan Jacobson
2020-01-01 2:47 ` Michael Heerdegen
2020-01-01 3:07 ` 積丹尼 Dan Jacobson
2020-01-01 3:45 ` Michael Heerdegen
2020-01-01 3:59 ` 積丹尼 Dan Jacobson
2020-01-01 4:53 ` Michael Heerdegen
2020-01-01 5:11 ` 積丹尼 Dan Jacobson
2020-01-01 5:31 ` Michael Heerdegen
2020-01-01 6:53 ` Drew Adams [this message]
2020-01-01 14:38 ` Noam Postavsky
2020-01-01 23:18 ` Richard Stallman
2020-01-02 3:29 ` Drew Adams
2020-01-02 21:59 ` Richard Stallman
2020-01-11 9:40 ` Eli Zaretskii
2020-01-01 16:46 ` Pieter van Oostrum
2020-01-02 4:14 ` Michael Heerdegen
2020-01-03 15:10 ` 積丹尼 Dan Jacobson
2020-01-03 23:18 ` Pieter van Oostrum
2020-01-03 23:31 ` 積丹尼 Dan Jacobson
2020-01-03 23:51 ` Pieter van Oostrum
2020-01-04 0:13 ` 積丹尼 Dan Jacobson
2020-01-04 13:58 ` Pieter van Oostrum
2020-01-04 23:48 ` Richard Stallman
2020-01-05 7:39 ` Pieter van Oostrum
2020-01-05 22:18 ` Richard Stallman
2020-01-05 8:06 ` Pieter van Oostrum
2020-01-05 15:31 ` Eli Zaretskii
2020-01-05 18:19 ` 積丹尼 Dan Jacobson
2020-01-05 18:48 ` Eli Zaretskii
2020-01-05 19:09 ` bug#38818: jidanni's mail headers not perfect?! 積丹尼 Dan Jacobson
2020-01-05 19:33 ` Eli Zaretskii
2020-01-05 20:48 ` Pieter van Oostrum
2020-01-06 3:26 ` Eli Zaretskii
2020-01-06 9:56 ` Pieter van Oostrum
2020-01-06 10:09 ` Eli Zaretskii
2020-01-06 10:16 ` Andreas Schwab
2020-01-06 8:30 ` Andreas Schwab
2020-01-06 8:50 ` Eli Zaretskii
2020-01-06 9:23 ` Andreas Schwab
2020-01-06 10:02 ` Eli Zaretskii
2020-01-06 10:13 ` Andreas Schwab
2020-01-05 22:19 ` bug#38818: Dired: mention deleting buffers, not just windows Richard Stallman
2020-01-05 23:30 ` 積丹尼 Dan Jacobson
2020-01-06 3:32 ` Eli Zaretskii
2020-01-06 23:08 ` Richard Stallman
2020-01-22 12:47 ` Lars Ingebrigtsen
2020-01-22 13:17 ` 積丹尼 Dan Jacobson
2020-01-22 13:19 ` Lars Ingebrigtsen
2020-01-04 6:16 ` Michael Heerdegen
2020-01-04 13:57 ` Pieter van Oostrum
2020-01-05 18:20 ` 積丹尼 Dan Jacobson
2020-01-04 13:26 ` Noam Postavsky
2020-01-01 6:47 ` Drew Adams
2020-01-22 12:51 ` 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
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=d8c494db-5335-4767-9b46-91d2a01828ea@default \
--to=drew.adams@oracle.com \
--cc=38818@debbugs.gnu.org \
--cc=jidanni@jidanni.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 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).