In other words rather than have the link name in the form of:
1984 decot bugs
it is now:
1984/decot in bugs.html
so that it matches how the entry itself looks (as in how it's
identified) and to say where (what file) it is (in). The reason it says
'in bugs.html' rather than 'bugs' (saying that the entry has bugs) is
because not all are bugs and it's saying where to see it anyway. But
some are features, others are missing links or files or other things
like that and to keep the same form it now says 'in bugs.html'.
This was done with my sgit(1) tool like:
sgit -e 's,\([0-9][0-9][0-9][0-9]\) \([-a-z\.0-9]*\) bugs,\1/\2 in bugs.html,g' '*/*md'
The link to bugs.html itself has the path '../../bugs.html'. This is
important as it's meant to be rendered in the browser. At first this was
not remembered and I did something like:
sgit -e 's,\[\([0-9][0-9][0-9][0-9]\) \([-a-z\.0-9]*\) bugs\](../../bugs.html,\[\1/\2 in bugs.html\](%%REPO_URL%%/bugs.html,g' '*/*md'
but this was changed to the simpler one due to the problem described
above. It's worth putting this note here as a reminder, though, so I
have included it here.
In other words rather than have the link name in the form of:
it is now:
so that it matches how the entry itself looks (as in how it's identified) and to say where (what file) it is (in). The reason it says 'in bugs.html' rather than 'bugs' (saying that the entry has bugs) is because not all are bugs and it's saying where to see it anyway. But some are features, others are missing links or files or other things like that and to keep the same form it now says 'in bugs.html'.
This was done with my sgit(1) tool like:
The link to bugs.html itself has the path '../../bugs.html'. This is important as it's meant to be rendered in the browser. At first this was not remembered and I did something like:
but this was changed to the simpler one due to the problem described above. It's worth putting this note here as a reminder, though, so I have included it here.