On Fri, 2018-01-05 at 13:42 -0500, Richard Hipp wrote: > On 1/5/18, Matt Welland <m...@kiatoa.com> wrote: > > > > Older versions of fossil would provide some very helpful > > information > > from "fossil help set": > > > > gmerge-command A graphical merge conflict resolver command > > operating > > on four files. > > Ex: kdiff3 "%baseline" "%original" "%merge" -o > > "%output" > > Ex: xxdiff "%original" "%baseline" "%merge" -M > > "%output" > > Ex: meld "%baseline" "%original" "%merge" "%output" > > > > Having to start up a UI and dig around for these example merge > > commands > > is a bit annoying. > The "fossil help gmerge-command" command should show you want you > want, does it not? I did split off the pages and pages of details > for > all settings out of the "fossil help settings" command into separate > "help" pages for each setting. But I thought that was a feature. Do > you disagree? Or am I misunderstanding your problem? > > Maybe I just need to improve the "fossil help setting" output to > provide some clue about how to get help on individual settings? > I had tried "fossil help set gmerge" which is similar to how other tools handle complicated multi-layered help. It didn't occur to me to try "fossil help gmerge" as gmerge is not a command:
fossil gmerge fossil: unknown command: gmerge fossil: use "help" for more information _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
