Le 12/11/2024 à 19:51, Johannes Sixt a écrit : > Am 11.11.24 um 17:53 schrieb Jean-Noël Avila via GitGitGadget: >> -The raw output format from "git-diff-index", "git-diff-tree", >> -"git-diff-files" and "git diff --raw" are very similar. >> +The raw output format from `git-diff-index`, `git-diff-tree`, >> +`git-diff-files` and `git diff --raw` are very similar. > > Throughout this document we see a lot of commands with dashes `git-foo`. > Does this have any significance, or should they be corrected to the > dashless form `git foo`? It could even be a "while at it"-change as you > are touching every instance anyway. > OK. I didn't pay attention to these points until now. >> >> These commands all compare two sets of things; what is >> compared differs: >> >> -git-diff-index <tree-ish>:: >> - compares the <tree-ish> and the files on the filesystem. >> +`git-diff-index <tree-ish>`:: >> + compares the _<tree-ish>_ and the files on the filesystem. > > Now that the backtick formats the content as in the synopsis, why is it > written _<tree-ish>_ and not `<tree-ish>` in the running text? > With the new processing in place, this is identical in the result. But for the writers, I would still push so that the form _<placeholder>_ be used to remind them that keywords and placeholders need to be differentiated. Moreover, in case the special processing macro is not applied, the markup is still correct pure asciidoc, while generating a "not so bad" output.
