On 2019/10/28 02:37, Carlos E.R. wrote:
On 28/10/2019 07.54, Per Jessen wrote:
I agree it is very slow on 15.1. To investigate, you could try running an strace from another shell.
For bash, it would be far more 'profitable' to set PS4 and "-x" and then try the completion. It will still generate a huge amount of output. When I'm debugging shell, I use PS4 set to:
echo "$PS4" ${BASH_SOURCE:+${BASH_SOURCE/$HOME/\~}}#${LINENO}${FUNCNAME:+(${FUNCNAME})}>
That gives you the source file and line number as well as what function it is in.
Problem: bash completion of systemctl command is very slow or totally hanged up for minutes in case of a great number of systemd units (>250). Reason: Completion routines calls systemctl as times as many systemd units exist. Solution: Patch file
In comparison, to scan through the kernel modules (>500) and filter out ones that are already loaded (~55) and offer the rest as possible completions takes less than a second: Try:
modprobe<space><tab>: ---i.e.: modprobe Display all 494 possibilities? (y or n) ...
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org