		Known gentoo bugs & problems

This file contains notes on known bugs and problems with the gentoo
file manager program. Its main use is to help me remember things I
may need to redo.

The file is formatted into "records"; each record begins with a
date and contains a bulleted list of items.

1998-08-23
* Styles are added with the currently selected style as parent,
  to make building hierarchies easier. While fine, this breaks the
  similarity with other config pages, where the "Add" button
  generally doesn't care which item is selected.
* This file is incomplete, since I created it too late.

1998-08-31
* Sneakily assumes machine is ASCII, for example in xmlutil.c and
  sizeutil.c. These things should be easy to fix, I'm just kind of
  skeptical against the whole idea of non-ASCII machines. I really
  don't think they exist. :)
* The sze_get_size() routine in the sizeutil-module uses doubles
  to represent integers, for maximum flexibility. This imposes some
  interesting limits to precision, which worry me somewhat. However,
  practictal tests indicate that a double can hold the maximum
  value of type size_t (sze_get_size()'s return type), so at least
  on systems using (signed?) 32-bit integers for size_t we're safe. :(

1998-09-20
* When copying files and directories that are write-protected, the
  copy will not have the same mode. User-write (S_IWUSR) is always
  added to the copy, since otherwise gentoo can't write it. It might
  be a good idea to reset the protection after the copy is done...

1998-09-28
* The option menu used in the commands editor seems to have some
  problems with its sensitivity. Very weird.
* The command sequence selection dialog tree sometimes opens up
  not looking proper at all, and the "auto-completion" used when
  you type in that dialog is also somewhat broken (when erasing).

1998-11-21
* If you start a program in a command, and that program in turn
  starts other processes, chances are that when gentoo quits, only
  the root process will be killed (this is the case with x11amp,
  for example). I know of no easy way in which to fix this...

1998-11-26
* The implementation of the path history touches the 'popwin'
  member of the gtk_combo widgets used. That is a no-no, but I
  really couldn't find another way. :( Suggestions welcome.

1999-01-29
* If you try to use a non-existant command for mounting or un-
  mounting, gentoo will die with a SIGPIPE in GTK+. I cannot
  figure this one out, and don't feel like doing a work-around
  (yet).

1999-03-20
* There is something fishy in the styles config page; when you
  add and delete styles, GTK+ emits a critical warning... I haven't
  been able to figure out what causes this (yet).
* GTK+ seems to spew out random warnings (possibly shm-related) on
  Solaris. I don't know if that's my fault, but I (naively?) don't
  think so...

1999-04-22
* Command output grabbing takes a long time if there's a lot of
  output (try grabbing the output of "tar tvf linux-2.2.x.tar.gz":).
  I've noted that the chunks of data fed to gentoo by the GDK I/O
  routines is very small; only 80-300 bytes at a time.

1999-05-16
* Various parts of gentoo now deal explicitly with 64-bit variables
  and constants. Since such behaviour is not easy to do in ANSI C,
  you will now get compiler warnings (or possibly errors, if your
  compiler is strictly ANSI) from these files.
	If your compiler is a (sufficiently up-to-date) version of
  GCC, you might want to add the __extension__ keyword where
  necessary.
	I chose not to include __extension__ in the distributed
  code, since it seems egcs (another common compiler) does not
  like it much. Or perhaps I just tried it on an old egcs...

1999-05-29
* There is a race-condition in the code which is kind of ugly...
  Since gentoo reads directory contents in a two-step process,
  with two complete directory traverals (the first computes the
  storage requirements, the second allocates and fills that
  storage), evil can happen if files are added or removed between
  these two steps. Hm, perhaps I should look into locking of
  directories? Or flatten out the algorithm... Anyway, this doesn't
  strike me as a big problem at the moment.
