diff options
| author | Joey Hess <joey@gnu.kitenet.net> | 2009-01-27 13:14:53 -0500 |
|---|---|---|
| committer | Joey Hess <joey@gnu.kitenet.net> | 2009-01-27 13:14:53 -0500 |
| commit | 94c932ee3d13924e3d916e859c2c9efa8e07ae31 (patch) | |
| tree | aa9e2b49089d801f6c242e1808449447d4314c5a /doc | |
| parent | db247437fd575a921adbf610c71276d3200442fa (diff) | |
thought
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/todo/need_global_renamepage_hook.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/todo/need_global_renamepage_hook.mdwn b/doc/todo/need_global_renamepage_hook.mdwn index 906bf1220..9c987aac4 100644 --- a/doc/todo/need_global_renamepage_hook.mdwn +++ b/doc/todo/need_global_renamepage_hook.mdwn @@ -87,6 +87,8 @@ hashes is desired, it could return the full set of hashes. > though, because one can't build a hash containing an array of hashes > as a value, without passing this array as a reference. > +>> Sure. +> > I'm not entirely sure about your first concern. Calling the hook > before or after the subpages addition both have their own problems. > @@ -95,3 +97,9 @@ hashes is desired, it could return the full set of hashes. > a given hook function can choose to act only before or after, or both? > > --[[intrigeri]] +>> +>> Have you thought about making the hook be run once *per* file that is +>> selected to be renamed? This would even handle the case where two +>> plugins use the hook; plugin A would see when plugin B adds a new file +>> to be renamed. And the subpage renaming stuff could probably be moved +>> into the rename hook too. --[[Joey]] |