1 |
Hi Felix, |
2 |
|
3 |
That what it exactly. I couldn't notice it because there were tons of |
4 |
files in that directory. |
5 |
|
6 |
I appreciate your help, |
7 |
Ivan |
8 |
|
9 |
On Sun, 2008-08-10 at 22:12 -0700, felix@×××××××.com wrote: |
10 |
> On Mon, Aug 11, 2008 at 12:57:26PM +0000, Ivan Alden wrote: |
11 |
> > Hi all, |
12 |
> > |
13 |
> > I was working in a shell with tar and I changed something where now when |
14 |
> > I type "*" it interprets it as --exlucde |
15 |
> > |
16 |
> > i.e |
17 |
> > |
18 |
> > $ * |
19 |
> > bash: --exlucde: command not found |
20 |
> > |
21 |
> > or |
22 |
> > |
23 |
> > $ ls * |
24 |
> > ls: unrecognized option `--exlucde' |
25 |
> > Try `ls --help' for more information. |
26 |
> |
27 |
> Does this happen in every directory, or do you have a file named |
28 |
> "--exlucde" that you created by mistake in the dir where this happens? |
29 |
> That name would tend to sort first ahead of most other names. I can |
30 |
> recreate it like this: |
31 |
> |
32 |
> $ touch ./--exlucde |
33 |
> $ ls * |
34 |
> ls: unrecognized option '--exlucde' |
35 |
> Try `ls --help' for more information. |
36 |
> $ |
37 |
> |
38 |
> and I can fix it like this: |
39 |
> |
40 |
> $ rm ./--exlucde |
41 |
> $ |
42 |
> |