You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If ack encounters a file called - in the current directory then it silently hangs for ever.
It seems that the file - is being treated as though it were a command-line argument -, which would indicate to read from standard input (and would indeed correctly cause ack to hang if there weren't anything on stdin). But a file called ./- is unambiguously a file; it isn't a command-line argument, and it isn't stdin.
Steps to reproduce. This works as expected:
$ mkdir bug_551
$ cd bug_551
$ echo aiieee > Batman.txt
$ ack i
Batman.txt
1:aiieee
Creating ./- causes the hang:
$ touch ./-
$ ack i
Explicitly listing the files to search avoids ./- getting in the way:
$ ack i *txt
aiieee
Bug #269 is sort-of the opposite of this, but they may overlap: both are influenced by ./-.
The text was updated successfully, but these errors were encountered:
If
ack
encounters a file called-
in the current directory then it silently hangs for ever.It seems that the file
-
is being treated as though it were a command-line argument-
, which would indicate to read from standard input (and would indeed correctly causeack
to hang if there weren't anything on stdin). But a file called./-
is unambiguously a file; it isn't a command-line argument, and it isn't stdin.Steps to reproduce. This works as expected:
Creating
./-
causes the hang:Explicitly listing the files to search avoids
./-
getting in the way:Bug #269 is sort-of the opposite of this, but they may overlap: both are influenced by
./-
.The text was updated successfully, but these errors were encountered: