In `fossil {changes,status}` and the commit description shown in the editor with `fossil commit`, show the original and renamed path annotation if the file has been renamed and edited. Prior to this, the file was only reported as edited, which can be confusing. Reported by James Cook 5a4c530e6b. Discussed with stephan@ and danield@, plus some forum members. While here, make sure we honour the relative-paths setting/option when displaying the original pathname in the renamed case. ... (check-in: ca9d0ddf user: mark tags: trunk)

This fixes an issue reported by James Cook in d162b6e2dc. Previously, we assumed the fx_git table does not exist when creating a new import, thus the previously untested use case of importing multiple new (read: not incremental) git repos into the same fossil repo failed at this assumption. While here, document the persistent nature of attributions in the import cmd help text; previously, this was only in the online docs: /doc/trunk/www/inout.wiki ... (check-in: 47fb3ddc user: mark tags: trunk)

Tested on OpenBSD 7.3-current and macOS Ventura 13.4 by me, and also on some Linux machines by stephan@

This automatically generates a compile_commands.json file on machines that support the -MJ clang compiler option, which can be consumed by language server clients. ... (check-in: 91f0f00f user: mark tags: trunk)

Reported by James Cook in 2b857ded1b: renamed files were shown as a deletion and an addition. This was because the optional 3rd and 4th field in the manifest's F card to indicate renames were omitted, despite having parsed these data from the git fast-export marks. ... (check-in: 7ab1e118 user: mark tags: trunk)

As per James Cook's report in 2b857ded1b, the /info page provided no hint that a renamed and modified file had been renamed, only modified. This slightly changes the annotation to make it clear the file was also renamed. Discussed with larrybr and stephan in /chat. Slight tweak on stephan's suggested phrasing.

ok stephan@ ... (check-in: 495a4d71 user: mark tags: trunk)