override / silence output on change of settable #1420

Activity

1. tleonhardt commented on May 23, 2025

   

   tleonhardt

   on May 23, 2025

   Member

   More actions

   @gjvc This is an interesting and reasonable suggestion. I can see several potential ways to go about it, including at least all of the following:

   1. Add -q/--quiet flag to the set command that suppresses default output from cmd2. This is easily done. It would require users to add the -q flag each time.
   2. Add an optional boolean parameter to the cmd2.Cmd.__init__() method called something like silence_set which has a global effect of silencing the default cmd2 output from the set command. This is also relatively easy and has the benefit of not requiring users to enter anything each time.
   3. You can override the do_set method of cmd2.Cmd in your application and modify accordingly. Also easy, but requires work on your end, not on the cmd2 end.

   Which do you think would best meet your needs and would provide the best overall user experience?
2. tleonhardt

   added this to the 2.6.2 milestone on Jun 12, 2025
3. tleonhardt

   self-assigned this

   on Jun 12, 2025
4. tleonhardt

   added the

   Feature

   issue type on Jun 12, 2025
5. tleonhardt

   added

   enhancement

   on Jun 13, 2025
6. tleonhardt commented on Jun 13, 2025

   

   tleonhardt

   on Jun 13, 2025

   Last edited by tleonhardt

   Member

   More actions

   @gjvc Would simply redirecting the output of that command to /dev/null be a reasonable option for you?

   set package_path devel/mold/2.36 > /dev/null
   2025-05-22T23:45:05.615 I           t/b/s/shell.py:99   package_path='lang/python/3.10' -> 'devel/mold/2.36'

   The easiest option I see is for you to either just redirect to /dev/null or to override the do_set method in your class which inherits from cmd2.Cmd. If you want to override it, just make a copy of our code and delete the line with the poutput call outputting that output. Alternatively, you can change the poutput to a pfeedback and change the quiet setting in your app to default to True.

   I don't like the option of adding a -q flag to the set command, it just doesn't feel right for that command. I also don't like the idea of adding another optional parameter to the __init__() method for cmd2.Cmd for this niche case.

   If we had it to do over again, we would perhaps choose to use pfeedback instead of poutput to output that info as it isn't really essential, but doing it at this point would be a breaking change which would pretty much be guaranteed to break someone else's application.
7. python-cmd2

   locked and limited conversation to collaborators on Jun 13, 2025
8. tleonhardt

   converted this issue into a discussion #1448 on Jun 13, 2025