From 63747bf6c33c96ded4ef6bcb50ff71696af2b69c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Sat, 15 Oct 2011 18:02:20 +0300 Subject: [PATCH] Remove obsolete TODO. --- TODO | 33 --------------------------------- 1 file changed, 33 deletions(-) delete mode 100644 TODO diff --git a/TODO b/TODO deleted file mode 100644 index 367fd5e5..00000000 --- a/TODO +++ /dev/null @@ -1,33 +0,0 @@ -bash completion needs to be rewritten from the ground up. ---------------------------------------------------------- - -bash completion really needs to be rewritten from the ground up, using all of -the features available in bash 4.1+ and without regard for compatibility with -earlier versions. - -At that time, it should be split into multiple files for easier source -management. Whether or not it is actually installed on the destination -computer as separate files is a matter for future debate. - -If it were installed as tens or even hundreds of files, each of which had to -be opened to decide whether it should be sourced in its entirety, that could -prove very expensive on some systems. - -Alternatively, a master file could decide which of the individual completion -files should be sourced. In that way, we wouldn't need to open extra files -just to ascertain that the commands for those functions aren't on the system, -anyway. - -A further alternative is that a build process be created, which would -concatenate the various files into a single completion file, similar to what -we have now. This option is my least favourite, because a system with a lot of -packages installed currently has to deal with sourcing over 200 kB of bash -code for each invocation of an interactive shell. - -An even better alternative would be if bash supported dynamic loading of shell -functions (in the manner of zsh), but I don't believe there are any plans to -add this feature. - --- -Ian Macdonald -Amsterdam, March 2006