![]() ![]() When the user does not select any specific action at the dispatch-conf prompt after the initial console prompt of dispatch-conf but rather presses the Enter key (which instructs dispatch-conf to display the diff again), the user will be prompted whether to run the GUI-based diff tool or rather again the console-based diff tool.This is because starting a GUI tool might involve considerable overhead, and for small changes it is often not worth it. When comparing files, the first diff for a new configuration file is always done in console mode.Once the scripts have been installed, dispatch-conf works in the following way: The above list of comparison/merging tools can easily be extended and the order of preference can easily be customized by modifying the script functions gui_showdiff(), console_showdiff(), gui_merge() and console_merge() as desired. If none of those tools is installed, the console-based "sdiff" is used as a fallback. The current version of the scripts directly support the following GUI tools for merging out of the box, and if more than one of those tools is installed they use the following order of preference: If none of those tools is installed, the console-based "diff -u" is used as a fallback. The current version of the scripts directly support the following GUI tools for comparison out of the box, and if more than one of those tools is installed they use the following order of preference: If no GUI tool can be found then the scripts also fall back to the console tools without unnecessary prompts. The scripts also probe whether a GUI tool is installed before using it. The scripts also try to be smart and probe for the presence of a $DISPLAY variable - if it is not set, they always use the console-based diff/merge tools and do not prompt the user. That is, my scripts are intended to be as backwards-compatible as possible with the traditional behavior of dispatch-conf. It the user decides not to run the GUI tools, the usual console-based diff and sdiff tools will be run. The scripts always ask before running a GUI tool and remember the last answer as a default for the next prompt. ![]() ![]() In order to achieve this goal, I wrote two scripts which can be set as the "diff" and "merge" tool in /etc/nf and will allow to optionally use a GUI-based tool for diffing/merging when running dispatch-conf. On the other hand, there are situations when I actually want to use a console-based tool - such as when logged into a remote account via a low-bandwidth SSH-session.Īny enhancement to dispatch-conf should therefore support both approaches. I have been using the console-based dispatch-conf for quite a while now.īut there are so many beautiful GUI tools out there like kdiff3, kompare or xxdiff which can be used for showing differences or merging - so why not using them in concert with dispatch-conf? Posted: Wed 10:23 am Post subject: Using dispatch-conf with GUI diff/merge tools Gentoo Forums Forum Index Documentation, Tips & Tricks Using dispatch-conf with GUI diff/merge tools Gentoo Forums :: View topic - Using dispatch-conf with GUI diff/merge tools ![]()
0 Comments
Leave a Reply. |