Re: [BUG] write to file

2016-01-27 Thread Kay C Lan
On Wed, Jan 27, 2016 at 8:58 AM, Kay C Lan wrote: > but by someone with actual qualifications, credibility and who's in a > position to take on 'Darth Bug' and save the day for all of us. :-) > > I've just added a comment to a different Bug and had a response back from Panos. It's just after 1am

Re: [BUG] write to file

2016-01-26 Thread Mark Wieder
On 01/26/2016 09:01 PM, Monte Goulding wrote: I’m pretty sure 2013 was in Edinburgh so that was one heck of a shopping cart ;-) Did I forget to mention the trip took a year? -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-

Re: [BUG] write to file

2016-01-26 Thread Monte Goulding
> On 27 Jan 2016, at 3:57 PM, Mark Wieder wrote: > > Heh. My brother lives in San Diego, so I figured out a 15-minute walk from > his house to the San Diego Trolley, so I could take the train to the 2013 LC > conference at the hotel. The train stopped across the street from the hotel. > I was

Re: [BUG] write to file

2016-01-26 Thread Mark Wieder
On 01/26/2016 08:03 PM, Ralph DiMola wrote: The first time I went to the UK from the States I was mad about some vendor or something and walked into the office at 9am and loudly pronounced how "pissed" I was. I quickly learned US=mad UK=drunk. After that when I traveled I refrained from any coll

RE: [BUG] write to file

2016-01-26 Thread Ralph DiMola
-Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Kay C Lan Sent: Tuesday, January 26, 2016 7:59 PM To: How to use LiveCode Subject: Re: [BUG] write to file On Tue, Jan 26, 2016 at 11:34 PM, Peter TB Brett wrote: > >> I would pre

Re: [BUG] write to file

2016-01-26 Thread Kay C Lan
On Tue, Jan 26, 2016 at 11:34 PM, Peter TB Brett wrote: > >> I would prefer if if people wouldn't use "the mothership" to describe the > core dev team. > > Sorry, no disrespect intended. I basically failed English and it's not the first time I've used a turn of phrase on this List which I thought

Re: [BUG] write to file

2016-01-26 Thread Mark Wieder
On 01/26/2016 07:34 AM, Peter TB Brett wrote: I would prefer if if people wouldn't use "the mothership" to describe the core dev team. My goodness. Somebody got up on the wrong side of the bed this morning. and monolithic ...there's that word again... -- Mark Wieder ahsoftw...@gmail.co

Re: [BUG] write to file

2016-01-26 Thread Mark Wieder
On 01/26/2016 08:22 AM, Richard Gaskin wrote: Your find prompted me to do a search in the bug DB for all reports that include "sc...@runrev.com" among the commenters and found some other gems from the olden days, like this useful tidbit I never knew before (is this documented?): ...you can

Re: [BUG] write to file

2016-01-26 Thread Roger Eller
On Tue, Jan 26, 2016 at 11:28 AM, Richard Gaskin wrote: > Peter TB Brett wrote: > > I would prefer if if people wouldn't use "the mothership" to describe > > the core dev team. > > I think the intention is less "Childhood's End" and more "Star Trek", a > tip of the hat to the centrally important

Re: [BUG] write to file

2016-01-26 Thread Richard Gaskin
Peter TB Brett wrote: > On 26/01/2016 14:47, Kay C Lan wrote: >> >> Panos at the mothership has confirmed that this is a bug that >> effects OS X only. > > I would prefer if if people wouldn't use "the mothership" to describe > the core dev team. > > After all, the core dev team working here at Li

Re: [BUG] write to file

2016-01-26 Thread Mike Kerner
Peter, I would consider it high praise, not something else. Over here in The Colonies, there are many references to "The Mothership", and I can't think of one that is derogatory. On Tue, Jan 26, 2016 at 11:22 AM, Richard Gaskin wrote: > Kay C Lan wrote: > > On Tue, Jan 26, 2016 at 9:49 AM, Rich

Re: [BUG] write to file

2016-01-26 Thread Richard Gaskin
Kay C Lan wrote: > On Tue, Jan 26, 2016 at 9:49 AM, Richard Gaskin wrote: > >> Good find. How did you come across that bit of archaeology? > > Not that good, what you really need to know is whether the enhancement > request was ever actioned. I'd guess the URL form remains as Jacque described, a

RE: [BUG] write to file

2016-01-26 Thread John Dixon
once said .. 'What's in a name ? that which we call a rose by any other name would smell as sweet'... :-) > Subject: Re: [BUG] write to file > To: use-livecode@lists.runrev.com > From: peter.br...@livecode.com > Date: Tue, 26 Jan 2016 15:34:42 + > > On 26/01/201

Re: [BUG] write to file

2016-01-26 Thread Peter TB Brett
On 26/01/2016 14:47, Kay C Lan wrote: Thanks Mike, Yes, that is all correct. Panos at the mothership has confirmed that this is a bug that effects OS X only. I would prefer if if people wouldn't use "the mothership" to describe the core dev team. After all, the core dev team working here a

Re: [BUG] write to file

2016-01-26 Thread Kay C Lan
Thanks Mike, Yes, that is all correct. Panos at the mothership has confirmed that this is a bug that effects OS X only. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscript

Re: [BUG] write to file

2016-01-26 Thread Mike Kerner
However, the contents of the file is: This is open/read/write/close On Tue, Jan 26, 2016 at 8:33 AM, Mike Kerner wrote: > Windows output: > > This is open/read/write/close > This is > > On Tue, Jan 26, 2016 at 2:16 AM, Kay C Lan > wrote: > >> On Tue, Jan 26, 2016 at 9:49 AM, Richard Gaskin < >>

Re: [BUG] write to file

2016-01-26 Thread Mike Kerner
Windows output: This is open/read/write/close This is On Tue, Jan 26, 2016 at 2:16 AM, Kay C Lan wrote: > On Tue, Jan 26, 2016 at 9:49 AM, Richard Gaskin < > ambassa...@fourthworld.com> > wrote: > > > > > Good find. How did you come across that bit of archaeology? > > > Not that good, what you

Re: [BUG] write to file

2016-01-25 Thread Kay C Lan
On Tue, Jan 26, 2016 at 9:49 AM, Richard Gaskin wrote: > > Good find. How did you come across that bit of archaeology? Not that good, what you really need to know is whether the enhancement request was ever actioned. I was searching the QCC DB to ensure I wasn't duplicating a Bug report when,

Re: [BUG] write to file

2016-01-25 Thread Richard Gaskin
Kay C Lan wrote: > On Mon, Jan 25, 2016 at 11:49 PM, Richard Gaskin wrote: >> >> > put "Log entry data" after URL ("file:" &> >> specialFolderPath("documents") & tLogFileName) >> >> When using the statement above, is the engine clever enough to use an >> append operation for that, or does it

Re: [BUG] write to file

2016-01-25 Thread Kay C Lan
I've gone ahead and added a Bug report 16761. When a Windows user report back I'll add it - or they can add to the report themselves. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage y

Re: [BUG] write to file

2016-01-25 Thread Kay C Lan
On Mon, Jan 25, 2016 at 11:49 PM, Richard Gaskin wrote: > > > > > put "Log entry data" after URL ("file:" &> > specialFolderPath("documents") & tLogFileName) > > When using the statement above, is the engine clever enough to use an > append operation for that, or does it seek to the end of th

Re: [BUG] write to file

2016-01-25 Thread Kay C Lan
Folks, Richard has confirmed he's not seeing this on Linux. Jacque has confirmed the Bug on OS X. If I can just get a Win user to check I'll then add a Bug report. So please Win users can you, in the msg box: >> >> set the defaultFolder to specialFolderPath("documents") >> put "trash this file.

Re: [BUG] write to file

2016-01-25 Thread J. Landman Gay
On 1/24/2016 9:46 PM, Kay C Lan wrote: The Dictionary says that if I open a file for 'update', then 'read from file' to a specific position that when I 'write to file' it will occur at the position I've read to but that's not what I'm seeing in 6.6.5GM, 7.1.1 rc4 and 8.0 dp13 - OS X 10.9.5. In th

Re: [BUG] write to file

2016-01-25 Thread Roger Eller
I may be wrong, but I think they've made the URL syntax smarter because it sure is fast enough for me, even on fairly large log files. ~Roger On Mon, Jan 25, 2016 at 12:36 PM, J. Landman Gay wrote: > I'm not the team, but logic tells me that opening a file for append will > always be faster and

Re: [BUG] write to file

2016-01-25 Thread J. Landman Gay
I'm not the team, but logic tells me that opening a file for append will always be faster and more efficient because the URL syntax works as a container, like a field or a variable. Every time you reference a URL, the entirety is read into RAM. I've always used "open for append" for that reason

Re: [BUG] write to file

2016-01-25 Thread Richard Gaskin
Roger Eller wrote: > I do the same if I am modifying a specific line in an existing file. > However, if I am appending to a file such as for logging, I use the > before or after modifiers in a file URL. > > put "Log entry data" after URL ("file:" &> specialFolderPath("documents") & tLogFileN

Re: [BUG] write to file

2016-01-25 Thread Richard Gaskin
Kay C Lan wrote: > The Dictionary says that if I open a file for 'update', then 'read > from file' to a specific position that when I 'write to file' it > will occur at the position I've read to but that's not what I'm > seeing in 6.6.5GM, 7.1.1 rc4 and 8.0 dp13 - OS X 10.9.5. In the > msg box: >

Re: [BUG] write to file

2016-01-25 Thread Roger Eller
I do the same if I am modifying a specific line in an existing file. However, if I am appending to a file such as for logging, I use the before or after modifiers in a file URL. put "Log entry data" after URL ("file:" & specialFolderPath("documents") & tLogFileName) ~Roger On Mon, Jan 25, 2016

Re: [BUG] write to file

2016-01-25 Thread Mike Kerner
It probably hasn't broken mine because I don't rely on the file pointers. I always read the entire file, modify, then write the entire container back. On Sun, Jan 24, 2016 at 10:46 PM, Kay C Lan wrote: > The Dictionary says that if I open a file for 'update', then 'read from > file' to a specifi