lynx-dev Re: [PATCH 2.8.5-pre4] Binary mode required

[Ilya Zakharevich]

On Wed, Feb 04, 2004 at 11:45:15AM -0800, I wrote:
> When lynx handles a file to an external program (e.g., you click on a
> jpeg file), it writes a copy with input file in a text mode.
> 
> (HTLoadFile() opens in text mode unless gzip/bzip2; then it gives it
> to HTParseFile(), which calls HTFileCopy().)  What follows is a
> horrible hack, but I do not understand the details good enough to
> deduce enough info to open file in binary mode...

Doug Kaufman answered:

  This doesn't occur with the DJGPP, Cygwin, or MingW ports, as far as I
  know. Is this problem specific to EMX? If so, is there a more general
  solution to writing in text mode only when that is really intended?

When tracing the problem in the debugger, I did not see any
system-specific #ifdef in the code of HTLoadFile() etc (except for
VMS).  Can you look at it in a debugger and see why HTLoadFile() opens
the file in binary mode?

Here is the scenario: go to a directory with, e.g., JPEG files, do

  lynx .

and press ENTER on a JPEG file (you need to make sure that lynx uses a
correct viewer for JPEG files; the configuration for this is extremely
painful, so I just did

  alias xli my_viewer

to avoid this hassle).

Thanks,
Ilya

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden