From f7441431697e4ba94202a1484721ae8acf3a4ab7 Mon Sep 17 00:00:00 2001 From: Todd Leonhardt Date: Tue, 18 Feb 2020 21:05:10 -0500 Subject: Moved custom cmd2 exceptions to a separate file and removed them from public API --- docs/features/hooks.rst | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'docs/features') diff --git a/docs/features/hooks.rst b/docs/features/hooks.rst index ee1d5fbc..ba9af573 100644 --- a/docs/features/hooks.rst +++ b/docs/features/hooks.rst @@ -102,12 +102,7 @@ called each time it was registered. Postparsing, precommand, and postcommand hook methods share some common ways to influence the command processing loop. -If a hook raises a ``cmd2.EmptyStatement`` exception: -- no more hooks (except command finalization hooks) of any kind will be called -- if the command has not yet been executed, it will not be executed -- no error message will be displayed to the user - -If a hook raises any other exception: +If a hook raises an exception: - no more hooks (except command finalization hooks) of any kind will be called - if the command has not yet been executed, it will not be executed - the exception message will be displayed for the user. -- cgit v1.2.1