nt 1/64)
}
\context {
\Staff
\consists "Timing_translator"
\consists "Default_bar_line_engraver"
}
\context {
\Voice
\remove "Forbid_line_break_engraver"
tupletFullLength = ##t
}
}
...which returns a lot of errors.
--
View this mess
barlines manually for each staff individually. This is
a behaviour that I often require to be swtiched but I can't find a simple
way to do it, or any that actually works.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-e
2013/6/23 DW :
> I am trying to typset a choral piece with half bar-lines in different places
> in different voices.
>
> The two approaches I have seen is to use polymetric notation or possibly
> subverting the /breathe command to get the desired effect.
>
> I have been trying to cut and paste exam
Ah, thanks. I was using the latest stable version which is 12.16.2, updating
to the unstable version did the trick.
Thanks again
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147287.html
Sent from the User mailing list
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147287.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https
Urs Liska writes:
> Am 23.06.2013 15:59, schrieb DW:
>> Ah, thanks. I was using the latest stable version which is 12.16.2, updating
>> to the unstable version did the trick.
> It is a really common source of problems that people use examples from
> manuals not matching their LilyPond version ...
.
Unless you are intimately involved with the manuals they can be a frightful
quagmire of information placed in diverse locations.
Not sure if that is a feature or a bug, but it is my experience.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual
context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147292.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo
obviate much of the current problem.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147293.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
DW writes:
> For the manual version problem, this arises largely because the
> manuals are laid out in such a way as to force one to do a google
> search on more obscure implementations, at that point it is very hard
> to see where you end up because you are opening 50 tabs that might
> lead you
ot
bad in principle, but in practice it becomes a nightmare to navigate really
quickly no matter how well you care to index it.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147295.html
Sent from the User mailing
- Original Message -
From: "David Kastrup"
To:
Sent: Sunday, June 23, 2013 3:48 PM
Subject: Re: Cut and paste from manual returns errors
DW writes:
For the manual version problem, this arises largely because the
manuals are laid out in such a way as to force one to d
DW writes:
> That's what I'm referring to (if I am understanding you correctly).
>
> If I want information on barlines I should go to BARLINES, not
> Learning>Barlines or Usage>Barlines or Notation>Barlines or
> Snippets>Barlines. Just BARLINES.
If you want extensive information, you go to the N
rack.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147298.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https:/
Hello,
> most people will do what I did at first, go to the search box on the
> lilypond page, type in "barlines" and proceed to be baffled and confused.
I have literally never used that search box before.
I don't even think it makes sense there — at the very least, it should be "next
to" the do
- Original Message -
From: "DW"
To:
Sent: Sunday, June 23, 2013 4:47 PM
Subject: Re: Cut and paste from manual returns errors
I don't want to harp on this point, but it is significant that when I
mention
to people that I use Lilypond their faces curl up and fru
fact, I still don't know how to find the answer to this particular
question (although I am pretty sure I have seen that it can be done),
perhaps you can enlighten as to the proper search procedure I should have
followed?
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/C
s.html to where I
need to be in my example in the post above?
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147303.html
Sent from the User mailing list archive at Nabble.com.
___
Hi,
> How do I get directly from here: http://lilypond.org/manuals.html to where I
> need to be in my example in the post above?
There should be a "Search v2.16.2 Documentation" field — instead of, or in
addition to, the one that's currently in the upper nav bar — which does a
search on the app
ntext:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147305.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lil
p.s.
> I would venture that would already be an enormous improvement even if it
> isn't a complete fix when it comes to the more obscure stuff.
For the more obscure stuff, I would imagine a very good — and possibly complete
— solution would simply be a matter of getting volunteers to add index e
Hi,
2013/6/23 DW :
> I am more than happy to volunteer, and I realise that it is easy to point
> these things out but much harder to actually fix them.
>
> http://lilypond.org/manuals.html
> ...is next to useless is you are looking for anything but the simplest
> implementations. []
I agree t
to do this? Is it possible to implement
natively at all (reaching, I know).
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147308.html
Sent from the User mailing list archive at Nabbl
2013/6/23 DW :
[...]
> If I am looking for a way to separate a notehead from its stem, how would I
> go about finding this information?
>
> _
>
> First step, according to the advice here is the manual index. But which
> manual do I choose? The obvious one (to
2013/6/23 DW :
> While we are on the topic of general improvements. One way I have found that
> makes editing a lot easier is to export snippets to .jpg and then using
> picture editors for larger scale alignments.
One problem with this approach is, that we've several blind users.
Pictures are us
DW writes:
> Thanks, I will take you up on that if you don't mind :)
>
> I am more than happy contribute my time and effort to such an indexing
> effort, I think something of that nature would help enormously to
> improve the general usability of what I consider to be by far the best
> music edit
2013/6/23 DW :
> While we are on the topic of general improvements. One way I have found that
> makes editing a lot easier is to export snippets to .jpg and then using
> picture editors for larger scale alignments. My problem is that many .pdf to
> .jpg converters often leave artifacts.
>
> Does an
Janek Warchoł writes:
> 2013/6/23 DW :
>> While we are on the topic of general improvements. One way I have found that
>> makes editing a lot easier is to export snippets to .jpg and then using
>> picture editors for larger scale alignments. My problem is that many .pdf to
>> .jpg converters ofte
- Original Message -
From: "DW"
To:
Sent: Sunday, June 23, 2013 8:28 PM
Subject: Re: Cut and paste from manual returns errors
While we are on the topic of general improvements. One way I have found
that
makes editing a lot easier is to export snippets to .jpg and then usi
On 24/06/13 01:19, DW wrote:
That's what I'm referring to (if I am understanding you correctly).
If I want information on barlines I should go to BARLINES, not
Learning>Barlines or Usage>Barlines or Notation>Barlines or
Snippets>Barlines. Just BARLINES.
Never mind various manuals for different
ffects, really make your work stand out and be recognized. Go
get 'em. All I really
want to do is finish this guitar instruction session.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp14
On 24/06/13 08:09, ed shaw wrote:
I'm new at this and expect to be drawing from this well, so, at the risk of
providing common knowledge, I'll contribute what I know about this subject
and how I plan to go about preparing .pdf pages for current publishing
project.
As a Quark and InDesign user, I
Yeah, DW, I see what you mean. I'm in the process of setting up a MAC. So
far, can't get the
resolution. I'll work on that tomorrow. Looks like crop copy and paste is
not going to be good
enough.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-pa
ght to try that. Thanks for the advice.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147331.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147331.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https
Am 23.06.2013 21:28, schrieb DW:
> Thanks, I will take you up on that if you don't mind :)
>
> I am more than happy contribute my time and effort to such an indexing
> effort, I think something of that nature would help enormously to improve
> the general usability of what I consider to be by far
t... That's an
awfully big document...
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147339.html
Sent from the User mailing list archive at Nabble.com.
___
lilyp
rget how to
do things.
Thanks, you're a hero.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147341.html
Sent from the User mailing list archive at Nabble.com.
___
lilyp
> That's enormously useful. Shouldn't something like that be front and
> center, along with a short (i.e. 1-2 page) guide on best practice
> for searching it as suggested by others above?
Unfortunately, only Acrobat can read that. There is no free tool yet
which correctly interprets PDF portfoli
s that you can't do a global search like you can in acrobat.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147344.html
Sent from the User mailing list archive at
in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-errors-tp147276p147374.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman
ed shaw writes:
> Produce Inkscape svg.
> Open in Gimp. Increase default resolution as needed. Default is 72. (Below
> Print Standard)
> I used 200. Save as .png.
Why would you do that if you had working SVG already?
> Import into Inkscape and resize or create oversize document.
That makes no
Sorry, syntax error.
"Produce document in Inkscape is the header. Instructions, followed.
In other words, construct document in Inkscape from elements produced
in Gimp.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Cut-and-paste-from-manual-returns-e
43 matches
Mail list logo
