Most of gui Editor work in frontground already.. GVim have this option because it spawn it in background by default and have a kind of client/server model (you can edit a file inside a specific instance that is already running).
fossil can't do nothing about that.. (I mean something clean/simple) -- Martin G. Le 2012-02-04 à 13:38, frantisek holop <min...@obiit.org> a écrit : > hi there, > > i tried to use gvimdiff as the gdiff-command > but i always kept getting empty file where > the temporary ~0 file should have been. then > i realized that gvim returns to the shell > right away, and fossil probably takes that > as a signal to removes the temp file. > > i solved this with gvim's -f option > (Foreground: Don't fork when starting GUI) > > $ fossil set gd > gdiff-command (local) gvimdiff -f > > but how is this solved with the other GUI editors? > is there a way to work around this in fossil itself? > > -f > -- > today is a fine day for firm decisions. or is it? > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
