in tables.

to debug.  Small code cleanup around tables.

macpath section).

		   fixes a rendering problem on IE5.

General adjustments to the table* environments, including using
<thead> and <tbody>.  Attempt to adjust the vertical alignment of the
table cells so that the baseline of the first cell matches the
baseline of the remaining cells:  When the first cell is small and the
second cell of the same row is multi-line, the first cell was
vertically centered by default.  Specifying valign=baseline fixes the
problem on IE, but Netscape seems to ignore both valign=top and
valign=baseline (even though valign is NS's fault!).  Make the
horizontal alignment of 'p' columns left instead of center (for the
headings).

(1) Fix reference to pwd.error to be KeyError -- there is no pwd.error
and pwd.getpwnam() raises KeyError on failure.

(2) Add cookie support, by placing the 'Cookie:' header, if present,
in the HTTP_COOKIE environment variable.

(My fault, not Dom's -- he submitted a correct patch to configure.)

(thanks Fred!)

on every invocation, instead of just the first.

invocation, instead of just the first.

PyncheWidget.__init__(): Add the extrapath argument which can be used
to pass in additional directories to search for Viewers.

lookup protocol.

set_colordb(): Call Viewers' colordb_changed() method if they have
them.  Notifies them of changes to the color name database.

text widget attribute), the color the attribute currently has is set
in the main widget.

platforms where tell() returns a long.  (Perhaps tell() should be
fixed too?)  Reported by Greg Humphreys.

to the 'load palette' entry.   Just don't put the quit button on
there.

(with some controversy surrounding AliceBlue :-)

You can switch database by just loading the new one; the list window
and nearest colors adapt to the new database.

Some reorganizing of code.  Also, the name of the database file is
stored in the ~/.pynche pickle.  If it can't be loaded, fallbacks are
used.

file URLs.

Ho ho ho -- that's trickier than it sounded!  The colorizer is working with
"line.col" strings instead of Text marks, and the absolute coordinates of
the point of interest can change across the self.update call (voice of
baffled experience, when two quick backspaces no longer fooled it, but a
backspace followed by a quick ENTER did <wink>).

Anyway, the attached appears to do the trick.  CPU usage goes way up when
typing quickly into a long triple-quoted string, but the latency is fine for
me (a relatively fast typist on a relatively slow machine).  Most of the
changes here are left over from reducing the # of vrbl names to help me
reason about the logic better; I hope the code is a *little* easier to

Bill Bedford's Apple Data Detector extensions for Python. Unchanged, except for the readme filename. Untested too, because I don't have ADD/IAD installed yet.

added 'org.python.core' to the maymiss list (pickly.py tries to import it, probably for JPython support) -- jvr

The test really wanted to distinguish between the two.  So now we test
for __GLIBC__ instead.  I have confirmed that this works for glibc and
I have an email from Christian Tanzer confirming that it works for
libc5, so it should be fine.

and an explanation of why any of stat.S_*() would be used instead of
os.path.is*().  (With some really small enhancements by me.)

<lannert@lannert.rz.uni-duesseldorf.de>.

on comments from Detlef Lannert <lannert@lannert.rz.uni-duesseldorf.de>.