From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Hook reloading
Date: Thu, 08 May 2008 23:10:12 -0700 [thread overview]
Message-ID: <1210313221-sup-40@south> (raw)
In-Reply-To: <1210152344-sup-9178@h984274.serverkompetenz.net>
Reformatted excerpts from Tyberius Prime's message of 2008-05-07:
> can anyone elucidate me on the subject of when (or how) sup reloads
> it's hooks?
A hook is only read from disk the first time it's called. Every time
the hook is called, that code is evaluated, so if you have a function
definition in there, it will be give that warning.
You can ignore the warning, or you can wrap it in a "unless defined?" as
you point out.
> And can I force sup to reload its hooks (while developing)?
There's no way to do this, but I agree it would be nice and wouldn't be
too hard to add...
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-05-09 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 9:25 Tyberius Prime
2008-05-08 9:50 ` Tyberius Prime
2008-05-09 6:10 ` William Morgan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1210313221-sup-40@south \
--to=wmorgan-sup@masanjin.net \
/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