Re: convert-ly problem 2

gt; > > > Then I expect you can just call > > > > convert-ly > > > > But I don’t use Windows now, so I haven’t tested this. I do use the > equivalent in MacOS. > > > > HTH, > > Carl > > > > > > > > > > > > >

Re: convert-ly problem

convert-ly.py is a python script, so you have to call it via python: python convert-ly.py https://www.pythoncentral.io/execute-python-script-file-shell/ HTH, Greg

Re: convert-ly problem 2

\usr\bin\convert-ly.py Then I expect you can just call convert-ly But I don’t use Windows now, so I haven’t tested this. I do use the equivalent in MacOS. HTH, Carl From: Peter Gentry Reply-To: Date: Thursday, December 19, 2019 at 8:44 AM To: Lilypond Users Subject: convert-ly problem

Re: convert-ly problem 2

Peter Gentry wrote: Clearly these other pythons have interfered with Lily somewhere and may have a bearing on my other recent issues. Relying on the .py association is asking for these problems. Get convert-ly to work with a single .ly file first. My batch file starts with "%programfiles(x

convert-ly problem 2

Having rediscovered the fact that Frescobaldi does not call convert-ly anymore. I went to the section 2.2 of the usage manual and popped the following into a windows 10 command prompt (with administrator privs) C:\Program Files (x86)\LilyPond\usr\bin>forfiles /s /p "C:\users\peter\Lilypool\Musi

Re: convert-ly problem

On 12/19/2019 6:55 AM, Peter Gentry wrote: Having rediscovered the fact that Frescobaldi does not call convert-ly anymore. I went to the section 2.2 of the usage manual and popped the following into a windows 10 command prompt (with administrator privs) C:\Program Files (x86)\LilyPond\usr\bi

convert-ly problem

Having rediscovered the fact that Frescobaldi does not call convert-ly anymore. I went to the section 2.2 of the usage manual and popped the following into a windows 10 command prompt (with administrator privs) C:\Program Files (x86)\LilyPond\usr\bin>forfiles /s /p "C:\users\peter\Lilypool\Musi

Re: Header title problem or convert-ly problem

Eluze wrote Tuesday, June 30, 2009 5:55 PM one more argument for the "easy" way to convert-ly 9'999 files (all with the same content): convert-ly -e typ2*.ly --> 36 sec. FOR %%x IN (typ1*.ly) DO convert-ly -e %%x --> 35 minutes btw i realized that conve

Re: Header title problem or convert-ly problem

utput which is a bit confusing since the output option does not seem to exist! -- View this message in context: http://www.nabble.com/Re%3A-Header-title-problem-or-convert-ly-problem-tp24210674p24275637.html Sent from the Gnu - Lilypond - User mailing list

Re: Header title problem or convert-ly problem

Eluze wrote Monday, June 29, 2009 12:19 AM Mats Bengtsson-4 wrote: There already is an example in the manual showing the use of *. I think that is probably sufficient. Yes, but it uses a for ... in ... do syntax that only works in BASH, there is a similar syntax in batch processing for wi

Re: Header title problem or convert-ly problem

ad 4GB) determines how many files can be processed! altogether i would suggest to simply recommend convert-ly -e *.ly in the docs -- View this message in context: http://www.nabble.com/Re%3A-Header-title-problem-or-convert-ly-problem-tp24210674p24246527.html Sent from the Gnu -

Re: Header title problem or convert-ly problem

Trevor Daniels wrote: Eluze wrote Friday, June 26, 2009 7:19 PM Trevor Daniels wrote: maybe it should be added in the docs: I'll do that. I'll also fix the documentation to avoid misleading people in the Jay was misled. i think the whole issue comes from the two lines 279 & 280 in conve

Re: Header title problem or convert-ly problem

Eluze wrote Friday, June 26, 2009 7:19 PM Trevor Daniels wrote: maybe it should be added in the docs: I'll do that. I'll also fix the documentation to avoid misleading people in the Jay was misled. i think the whole issue comes from the two lines 279 & 280 in convert-ly.py: opt_parse

Re: Header title problem or convert-ly problem

rd is also working (as long as no blank is involved in your calling statement): convert-ly -e *.ly convert-ly -e "myfiles*.ly" this will convert all corresponding .ly files, even if they have blanks in their name! -- View this message in context: http://www.nabble.com/Re%3A-Header-t

Re: Header title problem or convert-ly problem

The entire AU is in need of being ripped apart and completely rewritten, albeit not quite as urgently as the website or the release uploading. I've tentatively booked the second week of July to do this. Cheers, - Graham On Fri, Jun 26, 2009 at 10:46:25AM +0100, Trevor Daniels wrote: > Hi Mats >

Re: Header title problem or convert-ly problem

Hi Mats I've already made some changes - see git. More comments below. Trevor - Original Message - From: "Mats Bengtsson" To: "Trevor Daniels" Cc: "-Eluze" ; Sent: Friday, June 26, 2009 10:12 AM Subject: Re: Header title problem or convert-l

Re: Header title problem or convert-ly problem

I don't see any reason why you would need the --to or --from flags, though. /Mats Jay Hamilton wrote: Carl- Really clear instructions and finally I got it to work. whew! Thank you. Jay On Thu, Jun 25, 2009 at 2:58 PM, Carl D. Sorensen > wrote: On 6/25/09

Re: Header title problem or convert-ly problem

Trevor Daniels wrote: maybe it should be added in the docs: http://lilypond.org/doc/v2.13/Documentation/user/lilypond-program-big-page#Updating-files-with-convert_002dly I'll do that. I'll also fix the documentation to avoid misleading people in the Jay was misled. My proposal is to chan

Re: Header title problem or convert-ly problem

Eluze wrote Friday, June 26, 2009 5:47 AM Trevor Daniels wrote: If the path to the file contains spaces you'll need to surround the full path with double quotes. i just found that triple double quotes are needed: convert-ly.py -e """my file.ly""" this works for me in windows vista That'

Re: Header title problem or convert-ly problem

windows vista maybe it should be added in the docs: http://lilypond.org/doc/v2.13/Documentation/user/lilypond-program-big-page#Updating-files-with-convert_002dly -- View this message in context: http://www.nabble.com/Re%3A-Header-title-problem-or-convert-ly-problem-tp24210674p24214920.html Sen

Re: Header title problem or convert-ly problem

Carl- Really clear instructions and finally I got it to work. whew! Thank you. Jay On Thu, Jun 25, 2009 at 2:58 PM, Carl D. Sorensen wrote: > > > > On 6/25/09 2:37 PM, "Jay Hamilton" wrote: > > > A: I have tried over and over to follow the docs. AND I have copy and > pasted > > both Mats sugges

Re: Header title problem or convert-ly problem

On 6/25/09 2:37 PM, "Jay Hamilton" wrote: > A: I have tried over and over to follow the docs. AND I have copy and pasted > both Mats suggestions and now Simon's . > Mats has never worked. Yes the version info is in the file. No it did not > work. > Simon's suggestion, I renamed the file wit

Re: Header title problem or convert-ly problem

Trevor Daniels wrote: Jay If you enter the name into Run the name of the program is "convert-ly.py". Are you missing the ".py"? But both convert-ly and convert-ly.py should work in a Command Prompt window. At least they do here (Windows Vista). This is better than Run as the window stays open

Re: Header title problem or convert-ly problem

; Sent: Thursday, June 25, 2009 9:37 PM Subject: Re: Header title problem or convert-ly problem A: I have tried over and over to follow the docs. AND I have copy and pasted both Mats suggestions and now Simon's . Mats has never worked. Yes the version info is in the file. No it did not w

Re: Header title problem or convert-ly problem

as per mats suggestion, change directory to where your .ly file is located e.g. On my machine just typing "convert-ly" and hit enter brings up usage instructions. If that does not work for you, try specifying everything explicitely "c:\program files\lilypond\usr\bin\convert-ly.py" -e mytemplate.l

Re: Header title problem or convert-ly problem

A: I have tried over and over to follow the docs. AND I have copy and pasted both Mats suggestions and now Simon's . Mats has never worked. Yes the version info is in the file. No it did not work. Simon's suggestion, I renamed the file without the space and in fact after that copy/pasted his

RE: Convert-ly problem

; I'm glad you mentioned logging off after installation. Ralph -Original Message- From: Mats Bengtsson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 03, 2007 8:11 AM To: Palmer, Ralph Cc: lilypond-user@gnu.org Subject: Re: Convert-ly problem I hope you have logged off and on

Re: Convert-ly problem

ypond-user@gnu.org Subject: Re: Convert-ly problem The short answer is that there haven't been any syntax changes between 2.10.0 and 2.10.7, so there's no need to run convert-ly. Anyway, the procedure is: - Start a command prompt: Start Menu -> Programs -> Accessories -> Command Prom

Re: Convert-ly problem

Other simple procedure , in the folder of myfile.ly, open a new document text with your notepad, write : convert-ly -e myfile.ly . Save this document with the extension *.bat, example : convert.bat . Do launch with a double-clic on this file. -- Martial http://cathemline.org __

Re: Convert-ly problem

The short answer is that there haven't been any syntax changes between 2.10.0 and 2.10.7, so there's no need to run convert-ly. Anyway, the procedure is: - Start a command prompt: Start Menu -> Programs -> Accessories -> Command Prompt - Change working directory to the folder where you have you

Convert-ly problem

Greetings - I guess I have a couple of questions and maybe a problem. I'm running Windows XP Pro V.2002 SP2. I downloaded . I tried to run it and got a message saying I needed to uninstall the old version. I uninstalled the old version (2.10.0), rebooted, and ran without any problem. I was tryi

ec-fonts in 2.6, was: convert-ly problem

> > ... > > You're welcome to reinstate the ec fonts as your private defaults, > > though. > > Well, this (I mean reinstating the ec fonts as my private defaults) is > what I would like to do, and also asked how this could be done in this > list three weeks ago. I got, however, no answer. Could yo

Re: convert-ly problem

Changing fonts has become so much easier. See http://pegasus.rutgers.edu/~elflord/unix/latex/no-bs.html for what it takes to put a Type1 font into LaTeX (let alone into LilyPond) and compare it to dropping the .pfa into ~/.fonts and doing #(define fonts (make-pango-font-tree

Re: convert-ly problem

I have the opposite opinion from Laura. The first project I did using Lilypond was to convert an old file from 1.3 to 2.4. It required a lot of hand editing. In the end, it is easier to hand edit a file than to re-input all the notes. I had to manally move all the open brackets for beaming o

Re: convert-ly problem

Laura Conrad wrote: HN> Discussing decisions beforehand is a nice democratic HN> tradition, but Lily is not a democracy. Neither is it a one-man development team for a program used by only one person. Well, whatever. Most changes are discussed with Jan, FWIW. (and no, we don't have rec

Re: convert-ly problem

> "HN" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: HN> Discussing decisions beforehand is a nice democratic HN> tradition, but Lily is not a democracy. Neither is it a one-man development team for a program used by only one person. HN> If you disagree with a change, you're we

Documentation, Was: convert-ly problem

Han-Wen Nienhuys wrote: Changing fonts has become so much easier. See http://pegasus.rutgers.edu/~elflord/unix/latex/no-bs.html for what it takes to put a Type1 font into LaTeX (let alone into LilyPond) and compare it to dropping the .pfa into ~/.fonts and doing #(define fonts

Re: convert-ly problem

Stephen wrote: > As I was working, I was pleased to see how much better the new syntax was. It was very refreshing to see developers who were willing to change a program so much to improve it without regard for compatibility issues. Finally, I found a project whose main objective was to be as go

Re: convert-ly problem

Laura Conrad wrote: I don't think that's exactly what I'm asking for. Of course I love being able to go back to any LaTeX file I or anyone else has ever written and use it to figure out how to do something this year. But for lilypond, I'd just like to know that when my code becomes useless some

Re: convert-ly problem

> "HN" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: >> How about considering whether there would be more future potential >> users if the half-life of lilypond code were longer? HN> I seem to recall that you and I have been through this discussion HN> before, and probably

Re: convert-ly problem

Laura Conrad wrote: HN> 1. the number of future (potential) users is smaller than the HN> number of current users. How about considering whether there would be more future potential users if the half-life of lilypond code were longer? I seem to recall that you and I have been through t

Re: convert-ly problem

> "GP" == Graham Percival <[EMAIL PROTECTED]> writes: >> Which "we" is that? I really think I'd remember a discussion of >> convert-ly not converting lyrics any more if it had happened on either >> lilypond-user or lilypond-devel. GP> I think that Erik is talking about this:

Re: convert-ly problem

On Wednesday 27 July 2005 16.59, Laura Conrad wrote: > > "ES" == Erik Sandberg <[EMAIL PROTECTED]> writes: > >> I'm willing to believe there is no automated way to convert every > >> possible \addlyrics to an equivalent \lyricsto. I don't believe > >> that the most common cases cou

Re: convert-ly problem

Laura Conrad wrote: there must be a lot of stuff that nobody can compile without major manual labor. At what point is this volume of stuff going to feed into design decisions? When either 1. the number of future (potential) users is smaller than the number of current users. 2. the current

Re: convert-ly problem

On 27-Jul-05, at 7:59 AM, Laura Conrad wrote: ES> Yes, this is a known problem which we have discussed earlier. Which "we" is that? I really think I'd remember a discussion of convert-ly not converting lyrics any more if it had happened on either lilypond-user or lilypond-devel. I think

Re: convert-ly problem

> "ES" == Erik Sandberg <[EMAIL PROTECTED]> writes: ES> On Monday 25 July 2005 17.47, Laura Conrad wrote: >> > "ES" == Erik Sandberg <[EMAIL PROTECTED]> writes: ES> \addlyrics (2.0) is converted to \oldaddlyrics, which is ES> strongly deprecated, and pretty unsupported. It

Re: convert-ly problem

On Monday 25 July 2005 17.47, Laura Conrad wrote: > > "ES" == Erik Sandberg <[EMAIL PROTECTED]> writes: > ES> \addlyrics (2.0) is converted to \oldaddlyrics, which is > ES> strongly deprecated, and pretty unsupported. It is known that > ES> it sometimes doesn't work. > > This seems

Re: convert-ly problem

> "ES" == Erik Sandberg <[EMAIL PROTECTED]> writes: ES> On Thursday 21 July 2005 17.42, Laura Conrad wrote: >> The attached lilypond file prints two verses if I run in in 2.0.1. >> >> If I run "convert-ly -f 2.0.1 tenor.ly >tenor-2.6.ly" and then run >> "lilypond tenor-2.6

Re: convert-ly problem

On Thursday 21 July 2005 17.42, Laura Conrad wrote: > The attached lilypond file prints two verses if I run in in 2.0.1. > > If I run "convert-ly -f 2.0.1 tenor.ly >tenor-2.6.ly" and then run > "lilypond tenor-2.6.ly", I get a lot of error messages like: > > tenor-2.6.ly:25:0: warning: junking even

convert-ly problem

The attached lilypond file prints two verses if I run in in 2.0.1. If I run "convert-ly -f 2.0.1 tenor.ly >tenor-2.6.ly" and then run "lilypond tenor-2.6.ly", I get a lot of error messages like: tenor-2.6.ly:25:0: warning: junking event: `LyricEvent' Stay mer- ry mates, proud Nep- tune lowres