As discussed in e-mails and calls, for example \note, \see and probably others
A working version in the website-dev branch, some possible tweaks hinted during the call. Thank you A&R.
Is there any command missing? Otherwise we can close (and open a new issue if any other command would be desirable)
Is this merged to main? For example https://jshelter.org/battery-cr/ still contains the line "\see https://lukaszolejnik.com/battery" (also on https://jshelter.org/ecma-array/, https://jshelter.org/ecma-date/, https://jshelter.org/eme/,
Can we generate URL like the ones in https://jshelter.org/geo/ clickable?
https://jshelter.org/h-c/ contains a broken list.
BTW How is "ECMAscript date" generated? I would prefer "ECMAScript Date".
Should I go through all the wrappers? I did not continue because the issues above might be already solved in an unmerged branch.
Hello, once you are back, can you have a look at my previous comment? I verified today and all my questions are still valid.
Ok so 8670fb7 fixes the following:
<>
Hello Ricardo,
8670fb7 is not in the main branch and is kind of hidden in a bunch of unrelated commits.
I am trying to use topic branches - one branch solves a single particular issue which in turn simplifies git history, see for example https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows and https://imagej.net/develop/git/topic-branches.
I think that the best workflow for issues like this is creating a branch for example called website-issue15 and there solving this issue. Another possibility is me cherry-picking the commit.
Can you also go through commits in website branch not in main, e.g. "git log origin/website ^origin/main --oneline" (replace origin with your local name if you use a different one for the pagure repository) and create topic branches for the commits, ideally without merges from main (use git rebase if needed).
Thank you
Libor
Log in to comment on this ticket.