Re: [Bash-completion-devel] merging related completions into a file for dynamic loading?

2014-12-29 Thread Ville Skyttä
On Sat, Dec 13, 2014 at 2:42 AM, Peter Cordes pe...@cordes.ca wrote: So, thoughts on replacing some of the many files in completions/* with symlinks to groups of related commands? We do already have some such cases done but I don't think we have rules set when to do it and when not. Note

Re: [Bash-completion-devel] merging related completions into a file for dynamic loading?

2014-12-13 Thread Raphaël
On Fri, Dec 12, 2014 at 08:42:27PM -0400, Peter Cordes wrote: I guess my thinking is that when we can bring COMPREPLY down from 100k to 50k items with sort -u, it's not a bad idea. Worth noting that `sort` use temporary files (= $TMPDIR filesystem accesses). Not sure about bash's compgen.

Re: [Bash-completion-devel] merging related completions into a file for dynamic loading?

2014-12-13 Thread Peter Cordes
On Sat, Dec 13, 2014 at 02:08:08PM -0300, Raphaël wrote: On Fri, Dec 12, 2014 at 08:42:27PM -0400, Peter Cordes wrote: I guess my thinking is that when we can bring COMPREPLY down from 100k to 50k items with sort -u, it's not a bad idea. Worth noting that `sort` use temporary files (=

[Bash-completion-devel] merging related completions into a file for dynamic loading?

2014-12-12 Thread Peter Cordes
apt-cache and apt-get completions use very similar commands, but slightly different. This is silly. apt-get should just be a symlink to apt-cache, with the contents in apt-cache. e.g. _apt_cache_sources() { apt-cache dumpavail | command grep ^Source: $1 | cut -f2 -d | sort -u } vs.