use same wording, use of bold/underlining:
   code: predefined words: **
      *./script.using.shellia* [**-i|-s|-m**] [**-d**] [--] [*other-script-opts*]

   code: free words: *
      *command sequence*
      *./script.using.shellia* [**-i|-s|-m**] [**-d**] [--] [*other-script-opts*]

   text: very important in context: **
      **shellia**
      **step**
      **interactive-mode**
      **check-mode**
      **trace-mode**

   text: important in context or files: *
      *command sequence*
      *check-mode* option **-c**
      **shellia** is tested successful with *bash*, *dash*, *busybox sh*, *mksh* and *posh*.

describe How to give options to main programm ("a a a" b c)
  $(ia_init)
  o1="$1"
  o2="$2"
  ia_add "mysubfun \"$1\" \"$2\""
  ia

describe full log (output from commands) only with -c

better manpage (not everything is described)

Reihefolge 
  
  ia 
    ia is based onsome basic principles:
      * functions communicate together, via stdout or variables
      * a return value other than 0 is an error
      * output to stderr is either an error, a warning, debug, or other important information.  
        in real life there may also be some commands that send information to stdout.
      * in a productiv run only information needed (information, that will lead the user to react in a different way) should be displayed.

    to solve this targets 
      * commands should be called with opions --quiet, --silent or similar if available.
      * the return value of each command should be checked.
      * the output of each command should be checked.


      example: a command "cmd1 -a -b" exits with return value 7 or 5 if everything is ok.
        ...
        ia_ignore "exit=7" 
        ia_ignore "exit=5"
        ia_add "cmd1 -a -b"
        ...

      example: a command line gives no output, means we can just use it:
        ...
        ia_add "a=$(($x / $y))"
        ...
        
      Information and should not be shown in productiv run.


  basic-mode

    short-description

      basic-mode allows to run parts of the script interactively managed and controlled

    interactive-mode is deactivated by default in the top function using ia.
    interactive-mode can be turned on with "$@" in the top function using ia (-i)
    interactive-mode is heritated to subfunctions using ia.
    interactive-mode can be deactivated interactively by each function using ia for it's subfunctions using ia.(i toggle -i flag).
    interactive-mode can be circumvented interactivly by each function using ia (c continue without questions).

  
  check-mode

    short-description
      run-mode means that stdout, stderr and exitcode of commands given to "ia-add" will be checked. 
  

  can now 
      use "ia -x" to make sure that tracing only traces his commands and not ia.

      trace-mode should ony be used by the programmer
      trace-mode should be turned off before the script goes in production
       
      
      
    
  "-i is deactivated by default in top function. 
  top function can turn on
  
  functions always heritate -i to subfunction, but each function can interactivel turn off -i
  -x 
  -x -c 
  
check if somebody has forgotton eval "$ia_init"

explain >&3

test.ia-c-s-m make sure option -s and -m are tested

trap rm tmpfiles

tmpfile name contains shellia

https://www.debian.org/doc/manuals/developers-reference/ch05.en.html

add test with colors

Explain ia_dev_dbg in man-page

add example for ia_stdout/ia_ignore with "/" in search expression (must be escaped)
