Carl Sorensen c_soren...@byu.edu writes:
On 1/24/10 7:42 AM, David Kastrup d...@gnu.org wrote:
You can use an inline attachment for that, like this:
This is even worse for those of us who use digests. The email is
split up into one email plus two attachments, so we never see the end
of
On 1/26/10 1:41 AM, David Kastrup d...@gnu.org wrote:
Carl Sorensen c_soren...@byu.edu writes:
On 1/24/10 7:42 AM, David Kastrup d...@gnu.org wrote:
You can use an inline attachment for that, like this:
This is even worse for those of us who use digests. The email is
split up
Carl Sorensen c_soren...@byu.edu writes:
On 1/26/10 1:41 AM, David Kastrup d...@gnu.org wrote:
Carl Sorensen c_soren...@byu.edu writes:
On 1/24/10 7:42 AM, David Kastrup d...@gnu.org wrote:
You can use an inline attachment for that, like this:
This is even worse for those of us who
Graham Percival gra...@percival-music.ca writes:
On Sun, Jan 24, 2010 at 12:39:51AM +0100, Gilles Sadowski wrote:
IMHO, perfect would be to *attach* a complete lilypond file, so that
people
Well, IMO, it's better to have a short file in the body of the email.
Because that way I can
Gilles asked for an attachment I don't exactly know what to attach so
I've attached the latest pdf output.
This is close but nothing I've tried gets the 1st set of 8ths to be \slurDown
\version 2.12.2
\header {
title = Nested Curves
}
melody = \relative c'
{
\clef bass
\key
On 1/23/10 6:39 AM, i...@soundand.com i...@soundand.com wrote:
Gilles asked for an attachment I don't exactly know what to attach so
I've attached the latest pdf output.
What was wanted was the exact working code to get bad output, which you've
included in the body of the email. Perfect!
Hi.
Gilles asked for an attachment I don't exactly know what to attach so
I've attached the latest pdf output.
What was wanted was the exact working code to get bad output, which you've
included in the body of the email. Perfect!
IMHO, perfect would be to *attach* a complete lilypond
This is what I was looking for. So could a snippet be created from this
simple(r) example with that instruction? The current example of nested
slurs with the schenker example is way too complex for my (and maybe
others?) poor brain.
Thanks to everyone for your help.
Jay
On Sat, Jan 23, 2010 at
Hi Jay,
So could a snippet be created from this simple(r) example with that
instruction?
What exactly is wrong with the [very simple] example in the docs?
http://lilypond.org/doc/v2.13/Documentation/notation/curves#phrasing-slurs
What could you not figure out by looking at that coe, or by
On 1/23/10 7:07 AM, Gilles Sadowski gil...@harfang.homelinux.org wrote:
Hi.
Gilles asked for an attachment I don't exactly know what to attach so
I've attached the latest pdf output.
What was wanted was the exact working code to get bad output, which you've
included in the body of the
Hi.
Gilles asked for an attachment I don't exactly know what to attach so
I've attached the latest pdf output.
What was wanted was the exact working code to get bad output, which you've
included in the body of the email. Perfect!
IMHO, perfect would be to *attach* a complete
Gilles Sadowski wrote Saturday, January 23, 2010 11:39 PM
Gilles asked for an attachment I don't exactly know what to
attach so
I've attached the latest pdf output.
What was wanted was the exact working code to get bad output,
which you've
included in the body of the email.
On Sun, Jan 24, 2010 at 12:39:51AM +0100, Gilles Sadowski wrote:
IMHO, perfect would be to *attach* a complete lilypond file, so that
people
Well, IMO, it's better to have a short file in the body of the email.
Because that way I can look at it and identify errors without having to
13 matches
Mail list logo
