Updates:
Status: Verified
Comment #14 on issue 714 by brownian.box: let the .ly file specify the
output filename
http://code.google.com/p/lilypond/issues/detail?id=714
Issue 836 is "Verified", indeed.
--
You received this message because you are listed in the owner
or CC fields of th
Comment #13 on issue 714 by jameseli...@googlemail.com: let the .ly file
specify the output filename
http://code.google.com/p/lilypond/issues/detail?id=714
If one were to verify this, how does the command work? Is there any
documentation for it?
--
You received this message because you ar
Updates:
Owner: ---
Labels: fixed_2_13_8
Comment #12 on issue 714 by percival.music.ca: let the .ly file specify the
output filename
http://code.google.com/p/lilypond/issues/detail?id=714
Regtest is now issue 1040; this is closed and should be verified.
I believe it was fixed
On Tue, Oct 6, 2009 at 12:28 AM, Ian Hulin wrote:
> I'm working on this stuff, but I'm on a steep learning curve, including
> reading Erik Sandberg's thesis, so it's up to you how you mark this tracker,
> as any more work on it will be tracked in 836.
Thanks for the reminder. Good luck with that,
Comment #11 on issue 714 by v.villenave: let the .ly file specify the
output filename
http://code.google.com/p/lilypond/issues/detail?id=714
OK, Ian appears to be working hard on Issue 836 so the regtest will have to
wait.
I'll mark this one as verified when 836 is closed as well.
--
You
Hi Valentin,
Long story. It was originally marked as a duplicate of 404, where it
was marked as fixed because Han-Wen pointed out we could use
output-suffix to make the filenames unique.
Then I started looking at the way it all worked and we found bugs in
this part of the code re internatio
On Mon, Oct 5, 2009 at 6:11 PM, Carl Sorensen wrote:
> We only need a regtest once it's implemented. I think we don't have the
> final work on it yet, but it's going on.
That's what I was afraid of. Why it is marked as "Fixed"? Is the
current code just a draft?
Cheers,
Valentin
__
On 10/5/09 6:12 AM, "codesite-nore...@google.com"
wrote:
>
>
> Comment #10 on issue 714 by v.villenave: let the .ly file specify the
> output filename
> http://code.google.com/p/lilypond/issues/detail?id=714
>
> Do we need a regtest for this feature?
We only need a regtest once it's imple
Comment #10 on issue 714 by v.villenave: let the .ly file specify the
output filename
http://code.google.com/p/lilypond/issues/detail?id=714
Do we need a regtest for this feature?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you star
Updates:
Status: Fixed
Comment #9 on issue 714 by Carl.D.Sorensen: let the .ly file specify the
output filename
http://code.google.com/p/lilypond/issues/detail?id=714
fixed 2_13_4
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Comment #8 on issue 714 by i...@hulin.org.uk: let the .ly file specify the
output filename
http://code.google.com/p/lilypond/issues/detail?id=714
Initial patch sent for review on rietveld.
See http://codereview.appspot.com/110111
This fixes the version numbering when output-suffix is define
Updates:
Status: Started
Cc: Carl.D.Sorensen
Comment #7 on issue 714 by v.villenave: let the .ly file specify the output
filename
http://code.google.com/p/lilypond/issues/detail?id=714
Ian has been working on this issue and has proposed some patches; see for
instance
http:/
Comment #6 on issue 714 by v.villenave: let the .ly file specify the output
filename
http://code.google.com/p/lilypond/issues/detail?id=714
That's because you've marked it as Verified.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Comment #5 on issue 714 by gpermus: let the .ly file specify the output
filename
http://code.google.com/p/lilypond/issues/detail?id=714
why the Mao is that "issue 404" displayed with strikethrough?! Anyway, the
link works.
--
You received this message because you are listed in the owner
Comment #4 on issue 714 by gpermus: let the .ly file specify the output
filename
http://code.google.com/p/lilypond/issues/detail?id=714
Sorry. Issue #404.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may
Comment #3 on issue 714 by hanwenn: let the .ly file specify the output
filename
http://code.google.com/p/lilypond/issues/detail?id=714
please link to the prev. issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this iss
Updates:
Status: Accepted
Labels: -Priority-Low Priority-Postponed
Comment #2 on issue 714 by gpermus: let the .ly file specify the output
filename
http://code.google.com/p/lilypond/issues/detail?id=714
Ok, I'm re-opening this since there's at least one user who'd like it.
Updates:
Status: Verified
Comment #1 on issue 714 by gpermus: let the .ly file specify the output
filename
http://code.google.com/p/lilypond/issues/detail?id=714
Sorry, duplicate of a previously-solved issue. I forgot to change "search
open issues" to "search all issues" when
look
Status: Accepted
Owner: gpermus
Labels: Type-Enhancement Priority-Low
New issue 714 by gpermus: let the .ly file specify the output filename
http://code.google.com/p/lilypond/issues/detail?id=714
It would be great if we could specify the filename, as in
\filename "vn1.pdf"
(or maybe just \fil
19 matches
Mail list logo
