source: trunk/third/findutils/TODO @ 18890

Revision 18890, 4.4 KB checked in by zacheiss, 22 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r18889, which included commits to RCS files with non-trunk default branches.
Line 
1-*-outline-*-
2* lib/filemode.c has "# undef S_ISDOOR" added.  This should be moved upstream.
3
4* -fstype core dumps on sparc-sun-sunos4.1.3_U1 with gcc-2.95.2
5This is on foxtrot.rahul.net.  dbx does not work on compiled find.
6Perhaps gcc is installed incorrectly.  "find / -fstype ufs" core dumps
7quickly.  cc works correctly.
8
9* Speed of locate without "-i" option needs to be increased.
10
11* There are many bugs to be fixed and features to be added to findutils.
12The current distribution is a snapshot which fixes many
13problems, but leaves others unsolved.  Many of the known problems are
14not listed below.  Over the next few releases, I hope to fix more
15items, and add the unfixed problems below.
16
17* Internationalization
18** Is ansi2knr internationalized?  Does it need to be?
19
20** Should these files be internationalized?
21        strftime.c
22
23** Should translated long options be offered in locate and xargs?
24** updatedb.sh should be internationalized as well
25
26* new standards with Austin group
27** "-H" and "-L" options to find were added by Austin group standards.
28They need to be implemented.
29
30**Austin added the following options to xargs:
31-I perhaps replaces -i
32
33-L perhaps replaces -l
34
35-E slightly different from -e
36
37* Should fnmatch.h be a link to fnmatch.h.in?
38See tar distribution for an example.
39
40* Eliminate unnecessary strcpy calls in xargs.
41
42* lib/getline.c
43getline.c contains a function getstr which is needed in locate,
44but is not in the standard library.  In fact getstr is in curses.
45This problem needs to be fixed.  Can getstr be removed?  Can getline.c
46be optionally included, or is it mandatory?
47
48* man pages for frcode, bigram, and code
49Perhaps a better description in texi pages as well.
50
51* Add option for find to sort output in lexical order for use for updatedb
52olarsac@airfrance.fr (Olivier) made the following suggestion:
53
54As I was running thru the code looking for the bug I wondered why the updatedb
55has to use sort...
56why not add an option to find that sorts the output in lexical order?
57my point is:
58- sort on a big list is costly (here we do locate on big big file system)
59- find may (in theory) sort incrementally very easily by sorting only the current
60directory entries before recursion
61- it would also solve the lack of \0 sort that prevents you to use the -print0
62to handle \n in file names properly
63
64
65* large file problems
66depcomp gets added by automake
67strncasecmp is needed
68which requires strcasecmp
69getline.c temporarily removed from Makefile.am
70remove getline.o from LIBOBJS
71remove extra AM_FUNC_GETLINE
72
73* Is lib/strcasecmp.c required?
74
75* xargs: allow newline or arbitrary character to separate arguments
76Tyler 'Crackerjack' MacDonald <yi@yi.org> suggested that it would be
77nice if newlines could separate arguments to xargs.  This would allow
78a single line to be used as an argument, regardless of white space,
79quotes, and backslash.  A function similar to read_string in xargs.c
80can be written which replaces the line:
81
82      if (c == '\0')
83
84with the appropriate character.
85
86* investigate _LIBC when used with TOLOWER and TOUPPER
87_LIBC is used to determine whether TOLOWER should check isupper first.
88Is there something better to check?  Alternatively, can tolower be
89checked at run time to determine whether isupper should be called first.
90
91* make findutils multibyte safe
92Bruno Haible reported many problems with findutils and multibyte.
93
94* BeOS problems with multibyte
95Bruno Haible reported problems with BeOS.
96
97* What should be the default value of PRUNEFS in updatedb?
98Currently, it is:
99: ${PRUNEFS="nfs NFS proc"}
100Perhaps it should default to nothing.
101
102* Include example of use of updatedb in documentation.
103Use something close to the Debian daily cron job.
104
105* Side effects do not allow the implicit use of -print.
106Specifically, the use of -prune turns off the implicit use of -print.
107Look at this line in find.c:
108  else if (!no_side_effects (predicates->pred_next))
109side_effects really means:
110predicate which produces output, according to find.c, at least it does
111some of the time.
112Two predicates, side_effects, and produce_output
113
114
115* Supply example for time range commands for find.
116
117                        --//--
118This is used by Emacs' spell checker ispell.el:
119
120LocalWords: ansi knr strftime xargs updatedb sh fnmatch hin strcpy
121LocalWords: lib getstr getline frcode bigram texi depcomp automake
122LocalWords: strncasecmp strcasecmp LIBOBJS FUNC findutils Solaris
123LocalWords: LIBC TOLOWER TOUPPER tolower isupper PRUNEFS
124LocalWords: nfs proc Debian cron
125LocalWords: Haible BeOS Crackerjack
Note: See TracBrowser for help on using the repository browser.