[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Specify completion without name
From: |
Peng Yu |
Subject: |
Re: Specify completion without name |
Date: |
Wed, 4 Jan 2012 21:37:43 -0600 |
> empty lines. There is no programmable completion mechanism to complete
> on non-empty command names.
I'm wondering if it is worthwhile to add such a feature. I have run
into the problem that it is very slow to command complete an
incomplete command especially when other programs are accessing the
disk (note that I frequently open new terminals, so the caching done
within a bash process does not help me much).
If I can configure how to complete on non-empty command names, I could
just check a file with all the commands in PATH are stored. By
checking just a single file, presumable the search can be much faster
than searching many directories.
--
Regards,
Peng
--
Regards,
Peng
- Specify completion without name, Peng Yu, 2012/01/04
- Re: Specify completion without name, Chet Ramey, 2012/01/04
- Re: Specify completion without name,
Peng Yu <=
- Re: Specify completion without name, Chet Ramey, 2012/01/05
- Re: Specify completion without name, Peng Yu, 2012/01/05
- Re: Specify completion without name, Chet Ramey, 2012/01/05
- Re: Specify completion without name, Peng Yu, 2012/01/05
- Re: Specify completion without name, Clark J. Wang, 2012/01/05
- Re: Specify completion without name, Peng Yu, 2012/01/05
- Re: Specify completion without name, Linda Walsh, 2012/01/11
- Re: Specify completion without name, Chet Ramey, 2012/01/11