put url tricks to copy files on windows

[Roger Eller]

You could also try the revCopyFile and revCopyFolder commands.  I normally
only use the URL syntax to save new data I've created in a variable to a
file.  When copying existing files/folders I either use "get shell" to call
native commands, or the built-in revCopyFile.

~Roger

On Wed, Jun 21, 2017 at 9:40 AM, Mike Kerner via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Let me be clearer.  I think the message could be better (or perhaps the
> dictionary could list the error messages and explain them), because even
> though we use the "open" command in LC to read from a file or create a
> file, the lack of the need for a "create file" command in LCS doesn't
> remove that thing in my intuition that says "well, the only file that needs
> to be opened is the one that exists, already, so the problem must be on
> that side".
>
>
> On Wed, Jun 21, 2017 at 8:39 AM, Matthias Rebbe via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
> > to write to a file, even if it is copied, it has to be opened first.
> >
> > Did you try to remove the 2 slashes in the to path also?
> >
> >
> > Matthias Rebbe
> > +49 5741 310000
> > ‌matthiasrebbe.eu <http://matthiasrebbe.eu/>‌
> >
> > > Am 21.06.2017 um 14:31 schrieb Mike Kerner via use-livecode <
> > use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>>:
> > >
> > > also what is confusing is when I removed the // from the FROM file but
> > left
> > > it in for the TO file, I get the same error, "can't open file", which
> to
> > me
> > > implies that the file that exists can't be read, not that the TO path
> is
> > > wrong.
> > >
> > > On Wed, Jun 21, 2017 at 7:37 AM, Roger Eller via use-livecode <
> > > use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>>
> > wrote:
> > >
> > >> Without meaning to add more confusion, a Windows UNC path from a
> server
> > to
> > >> a file does work with the form
> > >> "binfile://servername/folder/folder/filename.txt
> > <binfile://servername/folder/folder/filename.txt>", while local access
> (or
> > >> mapped drives) are like "binfile:C:/folder/folder/filename.txt".
> > >>
> > >> ~Roger
> > >>
> > >> On Jun 21, 2017 2:07 AM, "Mark Waddingham via use-livecode" <
> > >> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>>
> > wrote:
> > >>
> > >>> As others have pointed out, for binfile and file urls you shouldn't
> > >>> include the standard '//' in front of the (absolute) path. These are
> > not
> > >>> parsed by the engine as standard urls - everything after the : is
> > parsed
> > >> as
> > >>> the filename.
> > >>>
> > >>> On an unrelated not you don't need to twiddle with the defaultfolder
> as
> > >>> files() and folders() now take an optional argument for the path :)
> > >>>
> > >>> Mark
> > >>>
> > >>> Sent from my iPhone
> > >>>
> > >>>> On 21 Jun 2017, at 03:37, Mark Wieder via use-livecode <
> > >>> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com
> >>
> > wrote:
> > >>>>
> > >>>>> On 06/20/2017 07:19 PM, Mike Kerner via use-livecode wrote:
> > >>>>> I'm not on a mac a lot :-(
> > >>>>> So is "binfile:" more universal, or do I have to check the
> platform,
> > >>>>> first?  What is the technique on linux?
> > >>>>
> > >>>> As far as I can remember, the "//" has never been recommended or
> > >>> approved for file or binfile. I'm surprised it gets parsed properly
> for
> > >>> OSX. You don't need or want it.
> > >>>>
> > >>>> --
> > >>>> Mark Wieder
> > >>>> ahsoftware at gmail.com <mailto:ahsoftware at gmail.com>
> > >>>>
> > >>>> _______________________________________________
> > >>>> use-livecode mailing list
> > >>>> use-livecode at lists.runrev.com
> > >>>> Please visit this url to subscribe, unsubscribe and manage your
> > >>> subscription preferences:
> > >>>> http://lists.runrev.com/mailman/listinfo/use-livecode <
> > http://lists.runrev.com/mailman/listinfo/use-livecode>
> > >>>
> > >>>
> > >>> _______________________________________________
> > >>> use-livecode mailing list
> > >>> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>
> > >>> Please visit this url to subscribe, unsubscribe and manage your
> > >>> subscription preferences:
> > >>> http://lists.runrev.com/mailman/listinfo/use-livecode
> > >>>
> > >> _______________________________________________
> > >> use-livecode mailing list
> > >> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>
> > >> Please visit this url to subscribe, unsubscribe and manage your
> > >> subscription preferences:
> > >> http://lists.runrev.com/mailman/listinfo/use-livecode
> > >>
> > >
> > >
> > >
> > > --
> > > On the first day, God created the heavens and the Earth
> > > On the second day, God created the oceans.
> > > On the third day, God put the animals on hold for a few hours,
> > >   and did a little diving.
> > > And God said, "This is good."
> > > _______________________________________________
> > > use-livecode mailing list
> > > use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>
> > > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > > http://lists.runrev.com/mailman/listinfo/use-livecode
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> >
>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>    and did a little diving.
> And God said, "This is good."
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>