summaryrefslogtreecommitdiffstats
path: root/bash-completion/findmnt
Commit message (Collapse)AuthorAgeFilesLines
* bash-completion: add findmnt --real --pseudoKarel Zak2018-05-111-0/+2
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* findmnt: add --output-all optionSami Kerola2018-05-031-0/+1
| | | | Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* bash-completion: make completions to work when bash set -u is in useSami Kerola2017-07-151-1/+1
| | | | | | | | | | | | | | | User who want to avoid refering to none-existing variables got earlier the following error. $ set -u $ findmnt --output <tab>bash: OUTPUT: unbound variable Here is short explanation of this setting. $ help set -u Treat unset variables as an error when substituting. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* findmnt: add --tree to allow to enable tree output for --mtabKarel Zak2016-12-081-0/+1
| | | | | | | | | | | | The --mtab output is merge from kernel and utab on all modern systems (without classic /etc/mtab). It means we have all necessary information to generate tree output. For the backward compatibility --mtab is the list by default, the new option --tree allows to override the default and enable tree always when the table contains child-parent relations. Signed-off-by: Karel Zak <kzak@redhat.com>
* bash-completion: curly brace missed for findmntAlexander Kuleshov2015-10-021-1/+1
| | | | | | | | | | | | | This patch provides fix for bash-completion/fndmt script. There is curly brace missed in the completion generation for the -M/--mountpoint option. In other way we will get following messages: bash: /etc/bash_completion.d/findmnt: line 91: unexpected EOF while looking for matching `)' bash: /etc/bash_completion.d/findmnt: line 141: syntax error: unexpected end of file Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
* bash-completion: update few options changed since v2.26Sami Kerola2015-08-031-0/+8
| | | | | | | | Attempt to find and update all changes to command line options that has not been reflected in bash-completion files in between versions v2.26 to v2.27-rc1. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* bash-completion: handle comma-separated optionsBoris Egorov2015-06-081-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This solution can become messy when you have too many options listed, because it repeats all of them. For example, after invoking completion with this input: $ partx --output END,SECTORS,SCHEME,START, You got these completions: END,SECTORS,SCHEME,START,FLAGS, END,SECTORS,SCHEME,START,NR, END,SECTORS,SCHEME,START,TYPE, END,SECTORS,SCHEME,START,NAME, END,SECTORS,SCHEME,START,SIZE, END,SECTORS,SCHEME,START,UUID, Nevertheless, it works even with numbers (listed options properly excluded from completion). Try to invoke completion after 'chcpu --disable ' or 'lsblk --exclude ' to see it in action. Few issues remained: * completion interrupts after encountering ':' in listed option, like in 'MAJ:MIN' in lsblk, losetup. * lscpu completion is broken: it inserts space after '--extended', but lscpu assumes there is no space after this option. It also doesn't complete '--parse' option. * some completion options are outdated (for example, lscpu MMHZ). We need to sync them with code. Fix for lscpu follows. Signed-off-by: Boris Egorov <egorov@linux.com>
* bash-completion: Invoke actual commands to be completed, not basenamesVille Skyttä2014-11-181-4/+4
| | | | | Addresses partially: http://bugs.debian.org/769462 Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
* various: erase all traces of the long-obsolete ext filesystemBenno Schulenberg2014-07-281-1/+1
| | | | | | The same argument as for xiafs: dead for over ten years. Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
* various: erase all traces of the long-obsolete xiafsBenno Schulenberg2014-07-281-2/+1Star
| | | | | | | | The xiafs filesystem was removed from the kernel fifteen years ago, and any kernel that contained it reached end of life ten years ago. It's time to stop mentioning it in the mount man page and elsewhere. Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
* bash-completion: use '\n' as IFS when ask for filenamesKarel Zak2013-09-301-0/+1
| | | | | | | | | | | | The bash completion for more(1) treats the space-separated pieces of filenames as different files. $ touch foo\ bar $ more foo<TAB> bar foo Reported-by: Ángel González <ingenit@zoho.com> Signed-off-by: Karel Zak <kzak@redhat.com>
* bash-completion: Don't offer short options where corresponding long one exists.Ville Skyttä2013-04-081-29/+29
| | | | | | | | | Users who know the short options can just hit the short option instead of tab, and it's not likely that it would be helpful to present a list of single character options to users who don't know them, doing so just unnecessarily trashes the list of suggestions. Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
* bash-completion: Avoid some unnecessary subshells.Ville Skyttä2013-04-081-1/+1
| | | | Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
* bash-completion: Don't offer any more completions after help or version.Ville Skyttä2013-04-081-0/+3
| | | | Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
* bash-completion: rename shell-completion -> bash-completionKarel Zak2013-04-051-0/+121
Signed-off-by: Karel Zak <kzak@redhat.com>