Re: Windows Equivalents for Shell: cp (copy)

From the dictionary: The rename command can be used to change a file's or folder's location only if the old and new locations are both on the same volume. Phil Davis On 7/12/16 5:23 PM, Roger Eller wrote: I thought the rename command allows for a different destination. Therefore,

Re: Windows Equivalents for Shell: cp (copy)

I thought the rename command allows for a different destination. Therefore, rename is actually "copy as new name" when the volumes or drive letters differ. ~Roger On Jul 11, 2016 11:19 PM, "Sannyasin Brahmanathaswami" wrote: > What alternatives do we have for basic shell

Re: Windows Equivalents for Shell: cp (copy)

The interesting question about that is now: What is in memory after [1] save? [2] save as? [3] save copy as (not yet implemented)? If I'm correct then it is ALWAYS the same, NOTHING is changed in memory. Only with [2] the file on disk is changed to which the object in memory links (and which is

Re: Windows Equivalents for Shell: cp (copy)

Can't you "save stack as.." and then set the filename of the stack back to what it was? On Tue, Jul 12, 2016 at 3:18 PM, J. Landman Gay wrote: > On 7/12/2016 4:08 PM, Richard Gaskin wrote: > >> Sannyasin Brahmanathaswami wrote: >> >> which file is in memory after we do

Re: Windows Equivalents for Shell: cp (copy)

On 7/12/2016 4:08 PM, Richard Gaskin wrote: Sannyasin Brahmanathaswami wrote: which file is in memory after we do this, the original, or the copy with a new name? A "save copy as" command? ... Did I miss something? When was "copy" introduced? It wasn't, it's being proposed. For now,

Re: Windows Equivalents for Shell: cp (copy)

On 12/07/2016 22:08, Richard Gaskin wrote: Sannyasin Brahmanathaswami wrote: which file is in memory after we do this, the original, or the copy with a new name? A "save copy as" command? I was hoping to see how the Dictionary describes that, but the Dictionary entry for "save" doesn't seem

Re: Windows Equivalents for Shell: cp (copy)

Sannyasin Brahmanathaswami wrote: > which file is in memory after we do this, the original, or the copy > with a new name? > > A "save copy as" command? I was hoping to see how the Dictionary describes that, but the Dictionary entry for "save" doesn't seem to mention a "copy" option at all.

Re: Windows Equivalents for Shell: cp (copy)

which file is in memory after we do this, the original, or the copy with a new name? A "save copy as" command? Peter ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe,

Re: Windows Equivalents for Shell: cp (copy)

behalf of "Dr. Hawkins" <doch...@gmail.com> Reply-To: How LiveCode <use-livecode@lists.runrev.com> Date: Tuesday, July 12, 2016 at 6:58 AM To: How LiveCode <use-livecode@lists.runrev.com> Subject: Re: Windows Equivalents for Shell: cp (copy) What I *want* to happen

Re: Windows Equivalents for Shell: cp (copy)

On Tue, Jul 12, 2016 at 12:18 AM, [-hh] wrote: > save stack as When I use this one, though, execution stops. I've been meaning to ask about this . . . I use it in a bmpVrsn routine to increment the file name of my various stacks (it also checks for and changes the date,

Re: Windows Equivalents for Shell: cp (copy)

On 12/07/2016 16:35, Roger Eller wrote: How about modifying the save option to automatically copy and rename as a versioned file. A "save copy as" command? Peter -- Dr Peter Brett LiveCode Technical Project Manager LiveCode 2016

Re: Windows Equivalents for Shell: cp (copy)

Jacqueline LG wrote: > The problem with "save as" is that you end up working in the backup > copy instead of the original. Roger E. wrote > How about modifying the save option to automatically copy and rename > as a versioned file. Yes, one can simply decide which one to use as backup. I use it

Re: Windows Equivalents for Shell: cp (copy)

How about modifying the save option to automatically copy and rename as a versioned file. On Tue, Jul 12, 2016 at 11:24 AM, J. Landman Gay wrote: > The problem with "save as" is that you end up working in the backup copy > instead of the original. > > Jacqueline

Re: Windows Equivalents for Shell: cp (copy)

The problem with "save as" is that you end up working in the backup copy instead of the original. Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On July 12, 2016 3:01:48 AM "[-hh]" wrote:

Re: Windows Equivalents for Shell: cp (copy)

Most Windows Server admins I know use xcopy. It has far more control over attributes than the standard copy command. http://commandwindows.com/xcopy.htm ~Roger On Tue, Jul 12, 2016 at 10:20 AM, Richard Gaskin wrote: > Sannyasin Brahmanathaswami wrote: > > > What

Re: Windows Equivalents for Shell: cp (copy)

Sannyasin Brahmanathaswami wrote: > What alternatives do we have for basic shell commands on Windows? > > Rumors are out that later this year, Windows will support bash.. and > perhaps then Livecode's shell calls to unix/bash commands will be > cross platform-- Ubuntu's bash environment is

Re: Windows Equivalents for Shell: cp (copy)

Or simply (works on each supported platform): save stack as -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Windows-Equivalents-for-Shell-cp-copy-tp4706590p4706598.html Sent from the Revolution - User mailing list archive at Nabble.com.

Re: Windows Equivalents for Shell: cp (copy)

or the url method put url "binfile:path/to/in/file into url "binfile:path/to/out/file" On Tue, Jul 12, 2016 at 12:42 AM, J. Landman Gay wrote: > On 7/11/2016 10:18 PM, Sannyasin Brahmanathaswami wrote: > >> RevCopyFile (which works on Windows) doesn't offer the option

Re: Windows Equivalents for Shell: cp (copy)

On 7/11/2016 10:18 PM, Sannyasin Brahmanathaswami wrote: RevCopyFile (which works on Windows) doesn't offer the option to copy to a different filename… I suppose I can copy the file and then rename the copy at the new destination, using "rename" which is simple enough. This works: put

Re: Windows Equivalents for Shell: cp (copy)

Windows has copy and xcopy as well as move and rename along with a bunch of other nifty things. On Mon, Jul 11, 2016 at 9:18 PM, Sannyasin Brahmanathaswami < bra...@hindu.org> wrote: > What alternatives do we have for basic shell commands on Windows? > > Rumors are out that later this year,