From owner-mint@fishpool.com Thu May 1 11:29:22 2003 Date: Tue, 29 Apr 2003 22:51:10 -0400 (EDT) From: Jim DeClercq To: Thomas Binder Cc: mint_list Subject: Re: [MiNT] possible silly question. In-Reply-To: <20030429164401.A8920@pc272.hrzpub.tu-darmstadt.de> Message-ID: References: <20030429112132.A8762@pc272.hrzpub.tu-darmstadt.de> <20030429164401.A8920@pc272.hrzpub.tu-darmstadt.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: jimd@panix.com Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: OK, understood. It is difficult, or at least takes time, and is not going to happen. I suppose that everyone else who has an sbin directory has found another way to move that RPM file around. And, of course, there is no limit to how long a file name might be, so if you did make bigger buffers, they would never quite be big enough. This did motivate me to look in a Gem function reference to see if there was any other way to read a directory using an operating system call, and it seems that Dreaddir() is the only way, and yes, you are right, it does not work in a useful way for things that are too long for a buffer. But I am still waiting for you to stumble over the large detailed file of the Thing logo, and send me a copy. It is a neat program, and I want to make a t-shirt of the logo. Jim On Tue, 29 Apr 2003, Thomas Binder wrote: > Hi! > > On Tue, Apr 29, 2003 at 09:54:48AM -0400, Jim DeClercq wrote: > > Oh, and speaking of Thing, the freemint-sbin RPM file is 37 > > characters long, and a directory list from Thing just ignores > > it. I had expected to see the first 32 characters. > > That's impossible - how should Thing be able to access that file > later if it only knows part of the complete filename? Furthermore, > it's not documented whether the Dreaddir() call fills the buffer > with a shortened filename if it won't fit completely. It's only > documented that it'll return -64 to tell you that your buffer's > too small. > > Besides, Thing does not silently ignore filenames, it will tell > you when it had to. > > I know people are still waiting for a release of the version of > Thing that handles longer filenames, but I still lack both time > and motivation to continue working on it. > > And don't bother asking for releasing Thing as open source - I've > made my decision and explained the reasons more than once. > > > Ciao > > Thomas > > > -- > Thomas Binder (Gryf @ IRCNet) gryf+usenet@hrzpub.tu-darmstadt.de > PGP-key available on request! > Vote against SPAM: http://www.politik-digital.de/spam/ >