@AlanMunn when float is loaded in a memoir document, memor disabled its own \newfloat (should probably save it under another name). So you're here using the \newfloat from the float package. Guess if they have have same number of possible arguments. Nope, memoer's \newfloat supports an optional arg, float's version does not
Git questiion. When you guys are working on branches and others are reviewing our code before merging into main. Exactly what do you do then to add your changes to the merge? Just perform them on the branch and do a new merge request or how to that work? (I really need to do some more work in Git)
@daleif for a github merge request (pull request) if you commit to the branch then the PR is automatically updated you don't need to explicitly make another request.
@daleif Thanks. That compounds the problem (at least for me) in two ways. When float sets up the \listof... the format doesn't match the memoir format. And since I instruct my users how to set up new lists, I use the memoir methods. Not quite sure what I should do about that.
@daleif For the algorithm case in particular, the package only sets a formatting macro; the rest is just setting up the floats, so it's simpler in principle not to load it and just use the class methods.
You can probably run the package emulator memoir has, run it before algorithm is loaded then float will not be loaded as the emulator already marked it as having been loaded. Or you can save the memoir macro before algorithm is loaded
