https://bugzilla.novell.com/show_bug.cgi?id=486333 Summary: Bash does not autocomplete after file creates Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: werner@novell.com ReportedBy: agruen@novell.com QAContact: qa@suse.de Found By: --- This sequence of actions causes bash not to autocomplete when it should ({key} means "type this key"; carriage return is explicit): --Session A-- --Session B, same directory-- rm -f mumblefoo*{cr} cat mumblefoo{tab} touch mumblefoobar{cr} {tab} At the first {tab}, bash finds that "mumblefoo" has no completion. At the second {tab}, bash finds that it now complete to "mumblefoobar". However, instead of autocompleting, it shows a list of possible completions with one choice, instead of completing to "mumblefoobar" right away. If the order of the touch and cat is reversed, bash immediately autocompletes to "mumblefoobar" as expected. This is a long-standing bug that I run into a lot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.