Frequently Asked Questions¶
Yes, if they are somewhat general. And, it is a great way to have me maintain template compatibility for you in case something changes in a future version.
Unfortunately, GitHub have crippled the newline behaviour of Markdown. If you wrap your comments for readability then you’ll be creating new paragraphs with every single line. There is very little that can be done locally to fix this.
The easiest way to workaround the issue is to disable wrapping in your text
editor for template files. The files
hubugs creates are easy to match for
automating this within your editor, just use
Markdown syntax supports two different heading formats, and only one of them
# at the start of a line. Using the alternative setext format
Heading ======= Sub-heading -----------
The other possibility, although not recommended, is to set a custom value for
core.commentchar in your
git configuration settings. program:hubugs
will honour the set value, and strip any lines that begin with that character.
You should note however that this is a recent addition to git, and other tools
may not work correctly with it set to a non-default value.
[It isn’t really a question, but it has come up a couple of times.]
The use of Jinja seems to be an entry barrier to some people, but it isn’t going to change. For the same – invariably pointless and religious – reasons people prefer other templating engines I prefer Jinja.
With all that said, I probably wouldn’t be opposed to accepting patches supporting additional optional engines ;)