I've released Charm 1.9.0. You can download it from SourceForge, like usual.
In addition to a number of bugfixes and the inclusion of the GPLv2 license
( Read more... )
May I suggest adding a variable in the .charmrc file for the template dir? It would be comparable to the variables for archive_dir and draft_dir. That way, we can invoke a template directly instead of including the full path.
Along the same line of thought, perhaps a variable for a default filter? That way, we wouldn't accidently post a raw Markdown entry that we meant to run through the filter.
Good idea on the template directory; I'll do that.
I'm not sure what you mean by the second. You can set the default_filter variable to specify a default one. Do you want a warning if you've got the default filter set and you try to post without having used it? Or did you mean something else?
Sourceforge is better -- thanks. (I should figure out how to set up an alert for when someone posts a patch... I *think* SourceForge can do that. Best to drop me a comment when you post a patch, I think.)
Comments 6
Along the same line of thought, perhaps a variable for a default filter? That way, we wouldn't accidently post a raw Markdown entry that we meant to run through the filter.
Reply
I'm not sure what you mean by the second. You can set the default_filter variable to specify a default one. Do you want a warning if you've got the default filter set and you try to post without having used it? Or did you mean something else?
Reply
Reply
(The comment has been removed)
Sourceforge is better -- thanks. (I should figure out how to set up an alert for when someone posts a patch... I *think* SourceForge can do that. Best to drop me a comment when you post a patch, I think.)
Reply
(The comment has been removed)
Reply
(The comment has been removed)
Reply
Leave a comment