public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kay Sievers" <kay.sievers@vrfy.org>
To: Roland <devzero@web.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: weird bash autocomplete issue
Date: Tue, 16 Dec 2008 20:47:22 +0100	[thread overview]
Message-ID: <ac3eb2510812161147q1ff0be0ev464237d6ba5d2338@mail.gmail.com> (raw)
In-Reply-To: <098b01c95fb5$bc2d1440$0301a8c0@bui.materna.com>

On Tue, Dec 16, 2008 at 20:37, Roland <devzero@web.de> wrote:
> i have come across a weird autocomplete issue i assume it is related to
> btrfs.
>
> let`s have some dirs:
>
> /non-btrfs-mount
>   ./linux
>   ./testdir
>
> /brtfs-mount
>   ./linux
>   ./testdir
>
> now, if i do "cd t<tab>" in /non-btrfs-mount, "t" autocompletes to "testdir"
> same for l<tab>inux - bash autocompletes as expected.
>
> now, the weird thing is, that on /btrfs-mount this behaves different.
>
> autocompletion for testdir works, but not for linux dir. weird.
>
> can someone reproduce this ?

Open another shell, find the bash process pid of the first shell with:
  ps afx
and do:
  strace -p <pid>
Go back to the first shell, hit <tab>, and the trace should show
what's going on. You see a significant difference there?

Kay

  reply	other threads:[~2008-12-16 19:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 19:37 weird bash autocomplete issue Roland
2008-12-16 19:47 ` Kay Sievers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-16 20:46 devzero
2008-12-16 21:41 ` Kay Sievers
2008-12-17  2:55   ` Kay Sievers
2008-12-17  8:45     ` Roland
2008-12-17 13:59       ` Kay Sievers
2008-12-17 14:17         ` Chris Mason
2008-12-17 14:46           ` Kay Sievers
2008-12-17 22:15             ` Kay Sievers
2008-12-17 23:58               ` Chris Mason
2008-12-17 14:40 devzero
2008-12-19  0:59 devzero
2008-12-19  1:27 ` Kay Sievers
2008-12-19  9:15 devzero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ac3eb2510812161147q1ff0be0ev464237d6ba5d2338@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=devzero@web.de \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox