You need to hide parameters in the command position, so use tag-order:
zstyle ':completion:*:-command-:*' tag-order '!parameters'
The !parameters part says to hide parameters when the completion is in -command- position:
A string starting with an exclamation mark specifies names of tags that are not to be used. The effect is the same as if all ...
Let's assume this is not a tiny chroot or container with only what they need, but rather a general purpose multi user operating system.
With sufficient automation, logging into the host may not be required. Perhaps provide via some self-serve system these limited options, which the automation does.
For letting them do the thing on the host, try what I would ...
With some general assumption here, in an attempt to answer the question specifically, that is:
So This script will, at this line, always exit no matter what the value of the variable is? (so its buggy).
Yes, more or less, but not necessarily exit the entire script. And also, no, it's not buggy; if my assumptions are correct.
As others have mentioned, it's ...
a common issue i have is, that the server is Reachable by IPv4 and IPv6 and due the fact that IPv6 will be prefered even if its unsupported to the internet of the LAN, it tries to connect.
On Putty you can solve this, that you use instead AUTO, prefer ipv4 as default
this behaviour seems a windows issue mostly, but found also on some linux boxes also
for future visitors, i had miniconda on my machine and its .bashrc entry was the one causing my delayed shell prompt. i no longed needed the conda so removed its entry from .bashrc that looked kike this
# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
The way I've done this in the past is using tar as a go-between -- but I'm sure there are other answers that are more elegant than this.
Where we have a list of files that meet a specific criteria IE: all files in /usr smaller than 1M
$ find /usr -type f -size -1M
That we want to copy to the location /mnt/dst.
You can use tar as a vector to pack/unpack the ...
Unix is a multitasking operating system. It doesn't start ps first or last. It starts all the things in the pipeline in parallel. Some might finish first or start after ps starts, and that's where your race comes from that makes the results slightly non-deterministic.
Basically, there is no order of operations here. A pipeline is a data stream, not a ...
As Bravo points out, a pipe in Linux is not a file, it is dynamic. So ps -x | grep login will actually start both programs at once, so that one can pitch down the pipe and the other can catch. The reason it is not deterministic, why your contrived example doesn't always show four grep instances, is that an instance may not be started until there is something ...