j
k
j a
j l
skip@pobox.com wrote:
Did this not happen with 2.5.2?
I have 2.5.1 and 2.5.2 and it produces an IOError, just as it should. So this was indeed introduced by 2.5.3. -Scott -- Scott Dial scott@scottdial.com scodial@cs.indiana.edu
Back to the thread
Back to the list