On Thu, 28 Jun 2012 13:52:49 -0700, Ross Boylan wrote: > Ross% % hg commit --repository I:\LAMOC\Ross --verbose --user Ross Boylan > <[email protected]> --message=mentalNonCoping2: switch to our new > backward elimination approach. > Ran and distributed results, which I add with this commit. -- > I:\LAMOC\Ross\mentalNonCoping2.sas I:\LAMOC\Ross\mentalNonCoping2.log > I:\LAMOC\Ross\mentalNonCoping2.lst > > Does this imply that if I typed what appears from "hg commit" on at a > windows command prompt it would work?
No. It just shows the list of command-line arguments with no escape. https://bitbucket.org/tortoisehg/thg/src/e7be841b9f0f/tortoisehg/hgqt/cmdui.py#cl-225 > Would even double quoting work if there are line breaks? I have doubts > about the argument to --user as well. Spaces in filenames could be > another problem. > > I'm curious because I want to understand how hg works from the command > line, and also because I had a file locking error > (https://bitbucket.org/tortoisehg/thg/issue/1989/process-cannot-access-the-file-because-it) > > for which a reported solution involved closing the GUI and entering the > command on the command line > (https://bitbucket.org/tortoisehg/thg/issue/889/cant-commit-file-over-network-share). > > My suspicion was that the command line would not work as it appears > literally above. Regards, ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
