[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Lynx W32 bug report

From: Wayne Buttles
Subject: Re: LYNX-DEV Lynx W32 bug report
Date: Thu, 6 Mar 1997 20:57:07 -0500 (EST)

On Thu, 6 Mar 1997, Benjamin C. W. Sittler wrote:

> On Thu, 6 Mar 1997, Wayne Buttles wrote:
> > On Wed, 5 Mar 1997, Christopher R. Maden wrote:
> > 
> > > Lynx substitutes the HOME (or TEMP/TMP) variable's value for any
> > > occurence of ~ - even though ~ is common in the DOS version of long
> > > file names.
> > 
> > I am going to start with * as an alias for $home in LYNX_CFG on Win32 only
> > and see how it goes.  There are some other places that react to ~ as well
> > but we can address them one at a time.  Some of them may be desired
> > (maybe). 
> Keep in mind that both * and ~ are valid characters in UNIX filenames.
> In fact, the only place ~ has a special meaning is inside certain shells,
> which do the following bit of clever processing to expand a word to a
> filename (which Lynx might benefit by, and bash just happens to have
> GPL'ed code for):

The only code I had changed so far in my personal code is the Win32 way of
parsing the lynx_cfg environment variable.  * is a non-usable character in
95 so it seemed like a good char to use in an environt variable.. 

I guess you are right, Ben{jamin?}, in that it appears the lynx is wrongly
accusing most `~' as being aliases to the home directory.  If you want to
point me to the GPL tilde code ;-) I will merge it.  Or, if you want to do
it I will then not integrate this `*' fix since Win95 will rarely if ever
use ~ as the first character.

Wow, good call.  I was thinking it was a clash between Win95 filesystems
and lynx and it didn't even click that lynx was cutting corners. 


; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]