Since #1391 is merged
therein in particular via
523b956
both STDOUT and STDERR are redirected to the log file.

The redirection of STDOUT causes regressions for things
that are intended to run in an interactive way with a user.

Any code that "just calls" interactively working tools like

less "$some_file"
vi "$another_file"

will appear as if ReaR had hang up because the user
does not see any STDOUT output on his terminal
unless proper specification to use the the original STDIN
STDOUT and STDERR when rear was launched by the user
as follows:

less "$some_file" 0<&6 1>&7 2>&8
vi "$another_file" 0<&6 1>&7 2>&8

cf. "What to do with stdout and stderr" in
https://github.com/rear/rear/wiki/Coding-Style

Because I @jsmeix cannot check the whole code
I assume there are some places where interactive tools
are "just called" that need to be fixed.