[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV default editor for lynx_w32: Howto?
From: |
Jim Dennis |
Subject: |
Re: LYNX-DEV default editor for lynx_w32: Howto? |
Date: |
Wed, 22 Oct 1997 00:57:15 -0700 |
>
>> Only if the file name is too long for dos or
>> whatever do you then issue the quotes.
>
> Probably more of the "whatever" than anything else since it is more
> of a problem than just being "too long". Windows95 allows/recognizes
> spaces within a file name and distinguishes between upper and lower
> case letters, for example. My stupid question is: where is this info
> held, somewhere in the FAT? I haven't had much time to "play around",
> but putting linux on a DOS partition of a Windows95 machine was a real
> eye-opener. None of the stuff Windows95 led me to believe was on the
> machine was really there, at least not in the form I expected.
The meta information (long filenames) are special directory
entries with the "v" (volume label) bit set. These are
interlaced with the corresponding short names. Thus each
32 bytes of long name becomes one "bogus volume label" adjacent
to the "real" (short, 8.3, DOS legal) directory entry.
OS/2 had a more elegant method -- wherein a each directory
entry used a couple of the "reserved" bytes (directory entries
only use ~20 of the 32 bytes -- with the extra bytes listed
in the programming specs as "reserved"). These were used as
offsets into an "EA DATA" file. I don't remember whether
EA DATA was volume or directory specific -- ISTR that it was
one EA DATA per volume -- and I think it should have been
one per directory!
Linux offers a UMSDOS facility which stores the meta data
in a hidden file named something like LINUX---.--- (I don't
remember the exact name -- but it's pretty obvious when you
see it).
> Is the file name conversion routine proprietary? Converting the name
> to the DOS equivalent (which seems to me to be what is in the FAT and
> what even Windows95 is actually using in the final call to read or write
> a file) might be more robust than relying on quotes. It's what I find
> myself doing manually all the time these days as I carry files on floppy
> from home to office and back (MS-DOS, OS/2, Un*x, WinDOZ - what a mess!)
>
> __Henry
>>
>>> On Mon, 20 Oct 1997, Wayne Buttles wrote:
>>>> On Tue, 21 Oct 1997, Leonid Pauzner wrote:
>>>>> ac81 (lynx_386): echo shows an argument within a pair of doublequotes "
>>>> (for the edit filename)
>>>>> Is it possible to remove " in DOS version ?
>>>> It can be. The quotes are needed for running under win95 so that long
>>>> filenames are preserved.
>>>
>>> If possible, it would be nice to use only the short filenames as arguments
--
Jim Dennis (800) 938-4078 address@hidden
Proprietor, Starshine Technical Services: http://www.starshine.org
PGP 1024/2ABF03B1 Jim Dennis <address@hidden>
Key fingerprint = 2524E3FEF0922A84 A27BDEDB38EBB95A
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;
- Re: LYNX-DEV default editor for lynx_w32: Howto?, (continued)
Re: LYNX-DEV default editor for lynx_w32: Howto?, Leonid Pauzner, 1997/10/20
Re: LYNX-DEV default editor for lynx_w32: Howto?, Leonid Pauzner, 1997/10/20
Re: LYNX-DEV default editor for lynx_w32: Howto?, Nelson Henry Eric, 1997/10/21
Re: LYNX-DEV default editor for lynx_w32: Howto?, David Combs, 1997/10/21
Re: LYNX-DEV default editor for lynx_w32: Howto?, Nelson Henry Eric, 1997/10/21
Re: LYNX-DEV default editor for lynx_w32: Howto?,
Jim Dennis <=
Re: LYNX-DEV default editor for lynx_w32: Howto?, Scott McGee (Personal), 1997/10/22