Call me lazy: some shells use exit (e.g. sh), others use quit (e.g. ftp), but I never remember which. So it's faster to write a patch to make virsh take both than it is to take a 50-50 guess, and get it wrong in half of my attempts. * tools/virsh.c (commands): Add 'exit'. * tools/virsh.pod: Document it. --- So, how many 'exit's in virsh will it take for me to have saved more time than I spent writing up this commit message and email? :) tools/virsh.c | 1 + tools/virsh.pod | 2 +- 2 files changed, 2 insertions(+), 1 deletions(-) diff --git a/tools/virsh.c b/tools/virsh.c index ddcc052..5c56fa6 100644 --- a/tools/virsh.c +++ b/tools/virsh.c @@ -8254,6 +8254,7 @@ static const vshCmdDef commands[] = { {"pwd", cmdPwd, NULL, info_pwd}, #endif {"quit", cmdQuit, NULL, info_quit}, + {"exit", cmdQuit, NULL, info_quit}, {"reboot", cmdReboot, opts_reboot, info_reboot}, {"restore", cmdRestore, opts_restore, info_restore}, {"resume", cmdResume, opts_resume, info_resume}, diff --git a/tools/virsh.pod b/tools/virsh.pod index 9434f31..fc4a70c 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -65,7 +65,7 @@ The following commands are generic i.e. not specific to a domain. This prints a small synopsis about all commands available for B<virsh> B<help> I<command> will print out a detailed help message on that command. -=item B<quit> +=item B<quit>, B<exit> quit this interactive terminal -- 1.6.6.1