[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: convert-ly from the commandline under windows corrupted?

From: James
Subject: Re: convert-ly from the commandline under windows corrupted?
Date: Fri, 16 Aug 2013 13:24:40 +0100


On 16 August 2013 13:13, Eluze <address@hidden> wrote:

> Phil Holmes-2 wrote
> > I think Windows 7 changed the permissions on some directories -
> > particularly
> > the "Program Files" directories.  It was an attempt to stop malware
> > writing
> > to these directories.  What happens if you try convert-ly myfile.ly >
> > c:\ANewDirectory\mynewfile.ly
> I'm on drive d: (not where the programs reside)
> ICACLS shows I havn't full rights on all:
>  VORDEFINIERT\Benutzer:(OI)(CI)(RX)    (RX means read and execute)
> so I guess I'll have to find out how to change that - unless somebody can
> tell me.
> under POWERSHELL it works - so maybe I'll have to execute such programs
> under ps (but I've no idea how this works)?!
> thanks for the hints!

Powershell is more of a real shell than the cmd window is.I cannot find a
decent link but this is quite good


It seems that text processing in PS is much more 'like' a UNIX shell
whereas cmd is not. I expect that the limits that we document in the AU doc
about quotes and double quotes are 'probably' not an issue in PS env.

The difference mainly is that in PS there are already pre-build cmdlets
that you cannot get in just the cmd prompt. It's more powerful for Windows
users than the cmd prompt is. For lilypond though it may be simply a way
for NIX users to run some of the commands on Windows without the unexpected

I've never really tried.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]