Dirk Zimoch
90a727c901
Most errors found with: codespell -L cach,thst,odly,aslo,parm,parms,inpu,ges,prset,pevent,ptd,pring,valu,noo,noe,ned,inout,ro,siz,froms,nd,fo,singl,sart,multy,tthe,allong,ment,inate,nodel,tring,alse,ture,thi,wille,numer Some more manually found (its -> it's) c++20: Do not use apostrophe (e.g. can't) in unquoted #error message
1.3 KiB
Expand the use of colour in the IOCs output
This release includes various changes to iocsh.cpp and elsewhere to add and expand the use of color:
-
When loading a startup script, the IOC Shell now displays comment lines in blue, and uses bold to make command lines stand out from other text.
-
The
softIoc -voutput also uses the above color scheme for the commands it prints. -
The default IOC Shell prompt is now displayed in green; this color can be modified in the
configure/CONFIG_SITE_ENVfile for all targets, or set for a specific target by adding aconfigure/os/CONFIG_SITE_ENV.<arch>file. The value of theIOCSH_PS1environment parameter in those files can use theANSI_ENV_*andANSI_*()color macros found in errlog.h to configure the appearance of the prompt. The C string literal concatenation syntax can be used to construct the prompt string:
IOCSH_PS1 = ANSI_ESC_RED "e" ANSI_ESC_YELLOW "p" ANSI_ESC_GREEN "i" \
ANSI_ESC_CYAN "c" ANSI_BLUE("s") "> "
-
More error messages printed by IOC Shell commands now appear in red, or use the red
ERRORprefix that was introduced in previous releases. -
The word "Illegal" has been replaced with "Invalid" in several Shell error messages.
-
The iocsh
varcommand now shows the data type of the registered variables as well as their values.