[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).1.txt?
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 05 Feb 2022 03:04:14 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261728
Bug ID: 261728
Summary: If sh became a usable interactive shell, then why
can't it tab-autocomplete file.(mine).1.txt and
file.(mine).1.txt?
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: bin
Assignee: bugs@FreeBSD.org
Reporter: oleglelchuk@gmail.com
If I have these files in my directory:
file.(mine).1.txt file.(mine).2.txt
and my shell is sh, I won't be able to use the tab button to autocomplete
either one of those files (if they are both present). The tab button allows me
to get to this point:
du -cah file.\(mine\).
...but it won't allow me to autocomplete further. I run 14-CURRENT (yesterday's
revision), but even though FreeBSD developers claim that sh became a "usable
interactive shell", I have this kind of problem.
--
You are receiving this mail because:
You are the assignee for the bug.