From: Glenn Morris <rgm@gnu.org>
To: 14377@debbugs.gnu.org
Subject: bug#14377: 24.3.50; patch: run a hook after `bookmark-write'
Date: Sat, 11 May 2013 21:42:30 -0400 [thread overview]
Message-ID: <rzzjw12cu1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8761yp2u27.fsf@pusto.de> (Eduard Wiebe's message of "Sat, 11 May 2013 21:30:24 +0200")
>> Of course, we could also install something like your patch, but the hook
>> functions will probably need access to the file name (which might turn into
>> a lexically scoped var any time).
Aren't matters of extensibility like this one reason why
http://www.gnu.org/software/emacs/emacs-paper.html#SEC15
favours dynamic binding?
next prev parent reply other threads:[~2013-05-12 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 20:22 bug#14377: 24.3.50; patch: run a hook after `bookmark-write' Eduard Wiebe
2013-05-10 21:09 ` Stefan Monnier
2013-05-11 19:30 ` Eduard Wiebe
2013-05-12 1:42 ` Glenn Morris [this message]
2013-05-12 18:01 ` Drew Adams
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=rzzjw12cu1.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=14377@debbugs.gnu.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 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).