Results 1 to 4 of 4

Thread: Strange tab-completion behavior

  1. #1

    Default Strange tab-completion behavior

    Hi,

    First time trying out Open Suse. Almost up and running without issues but experiencing some strange behavior with bash tab-completion. For many commands it functions as expected. so I can cat /et[tab]/cryp[tab] to get "cat /etc/crypttab".

    With other commands, tab-completion only works partly. When I write cryptsetup open /dev/md/arcoframe:0, the normal behavour should be that I can tab-complete /dev/md/arcoframe:0, but this don't work. Even if I am in dev/md/ and try tab-completing arcoframe:0, nothing happens.

    I appreciate any suggestions?

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,493
    Blog Entries
    15

    Default Re: Strange tab-completion behavior

    Quote Originally Posted by ronanoon View Post
    Hi,

    First time trying out Open Suse. Almost up and running without issues but experiencing some strange behavior with bash tab-completion. For many commands it functions as expected. so I can cat /et[tab]/cryp[tab] to get "cat /etc/crypttab".

    With other commands, tab-completion only works partly. When I write cryptsetup open /dev/md/arcoframe:0, the normal behavour should be that I can tab-complete /dev/md/arcoframe:0, but this don't work. Even if I am in dev/md/ and try tab-completing arcoframe:0, nothing happens.

    I appreciate any suggestions?
    Hi and welcome to the Forum
    I you try only part of the string eg arco<tab> I would expect to see it is escaped, eg arcoframe\:0? What shell are you using?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Default Re: Strange tab-completion behavior

    Thanks

    I read an OS wiki and found my mistake. If I write "cryptsetup luksOpen", tab-completion works. From Arch I was used to "cryptsetup open", but this does not work at all here.

  4. #4
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,043

    Default Re: Strange tab-completion behavior

    On Wed, 01 May 2019 14:16:03 +0000, ronanoon wrote:

    > Thanks
    >
    > I read an OS wiki and found my mistake. If I write "cryptsetup
    > luksOpen", tab-completion works. From Arch I was used to "cryptsetup
    > open", but this does not work at all here.


    There's probably a bash-completion configuration in Arch that adds some
    intelligence to tab completion for cryptsetup.

    Jim

    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •