Groups | Search | Server Info | Login | Register
Groups > comp.sys.acorn.programmer > #6608
| From | Steve Fryatt <news@stevefryatt.org.uk> |
|---|---|
| Newsgroups | comp.sys.acorn.programmer |
| Subject | Re: OS_File case sensitive |
| Date | 2026-02-24 19:20 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <mpro.taz9qr00o36wd05mv.news@stevefryatt.org.uk> (permalink) |
| References | <5cb028ab62bob@sick-of-spam.invalid> |
On 24 Feb, Bob Latham wrote in message
<5cb028ab62bob@sick-of-spam.invalid>:
> I'm trying to find a way to check if a directory on a NAS contains any
> music files. .flac .mp3 .m4a
>
> I've had the realisation this morning that OS_File 13 is case sensitive so
> setting R1 to point to */flac will not cut it. So to find if a (NAS)
> directory contains any flac files it looks like I would need to test for
> flac and Flac and FLAC etc. any combination.
That sounds like the underlying filing system, not OS_File. The NAS is
probably running some Linux-y FS that's case sensitive, and therefore
Music.FLAC and Music.Flac are actually two different files, which can both
exist together.
> The only solution I can see is to use OS_GBPB to read the name of file
> after file and mask out the upper lower case bit ie &DF and if nothing is
> found early I have to read every name in the directory.
>
> Is there a better way?
Make sure that your filing system's filetype mapping is sensible (whether it
uses MimeMap or its own arrangement) and test on filetypes? That way, it
would be the FS's problem to do the extension parsing.
It should work, but in the best traditions of Usenet, I've not tried it...
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
Back to comp.sys.acorn.programmer | Previous | Next — Previous in thread | Next in thread | Find similar
OS_File case sensitive Bob Latham <bob@sick-of-spam.invalid> - 2026-02-24 12:21 +0000
Re: OS_File case sensitive Steve Fryatt <news@stevefryatt.org.uk> - 2026-02-24 19:20 +0000
Re: OS_File case sensitive Bob Latham <bob@sick-of-spam.invalid> - 2026-02-24 21:50 +0000
csiph-web