Hi Kieren,
On Jan 3, 2008, at 12:39 PM, Kieren MacMillan wrote:
I have easily spent 10 times the amount of time studying Lilypond
and understand only 1/10th of what I can do in LaTeX.
This may be because LaTeX includes *significantly* more (and more
complex) macros which sit on top of
Le 3 janv. 08 à 21:31, Valentin Villenave a écrit :
[...]
Mmm... I'll still wait for a few days and see if the author has
anything to say on this topic :)
Plus, it would be great to add a few actual notes to demonstrate its
use (I'd be happy to use the 'real_music' tag just once more :)
I
On Thu, 3 Jan 2008 13:50:14 -0500
Kieren MacMillan [EMAIL PROTECTED] wrote:
And you don't need explanations.
I disagree!
1. If these are meant in any way to be instructive (like most, if
not all, of the LSR!), then there *must* be internal documentation.
They're not. They're supposed
Hi Graham,
They're not. They're supposed to be useful.
Because instruction isn't useful?
For future reference, I don't read or respond to posts which begin
with such ludicrous and intentionally irritating statements...
Regards,
Kieren.
___
On Fri, 4 Jan 2008 15:18:07 -0500
Kieren MacMillan [EMAIL PROTECTED] wrote:
Hi Graham,
They're not. They're supposed to be useful.
Because instruction isn't useful?
For future reference, I don't read or respond to posts which begin
with such ludicrous and intentionally irritating
2008/1/4, Kieren MacMillan [EMAIL PROTECTED]:
For future reference, I don't read or respond to posts which begin
with such ludicrous and intentionally irritating statements...
Hi everybody, hi Kieren,
I think there's some kind of a misunderstanding here...
I thought everybody on this list
Kieren,
Once again (and again), thank you for your advice.
On Sunday, December 30, 2007, at 12:47 PM, Kieren MacMillan wrote:
How can I figure out new code to solve new problems when I don't
know the code exists?
I have learned essentially everything I know by looking at the
examples
1. Look at the GDP docs:
http://web.uvic.ca/~gperciva/
2. Specifically, the Learning Manual 3 Fundamental concepts.
Probably 4 Tweaking output as well. Trevor Daniels has spent
dozens of hours working on these chapters.
3. If you have any improvements, please send them.
Cheers,
- Graham
On
Hi Jeremiah,
Once again (and again), thank you for your advice.
=)
In the particular instance above, however, I am not sure how I
would *know*
to replace \GrandStaff with \InnerStaffGroup. See next paragrraph
below.
Okay... I think I'm beginning to understand your issue(s).
(1) Last
On Thu, 3 Jan 2008 12:39:58 -0500
Kieren MacMillan [EMAIL PROTECTED] wrote:
The benefit of LaTeX, coupled with whatever documentclass and
packages you use, is that you don't NEED to access the code at that
level.
Lilypond just doesn't have those abstracted stylesheets.
I'll add that this
2008/1/3, Graham Percival [EMAIL PROTECTED]:
We also now have the perfect place for these stylesheets: LSR. If
there's any interest in this, we'll add a tag specifically for
stylesheets (or modules or packages or whatever we want to call
them). These snippets would be just like LaTeX
Hi y'all:
I'll add that this lack of stylesheets is due to users not
creating them, not a lack of technical support.
I figured that was the case, but it's nice to get official
confirmation! =)
It just requires a helpful user to create the stylesheet.
Coincidentally, I've recently been
Hi Graham,
Don't split it up.
I partially agree.
And you don't need explanations.
I disagree!
1. If these are meant in any way to be instructive (like most, if not
all, of the LSR!), then there *must* be internal documentation.
2. If these are meant to be combined, then they need
2008/1/3, Graham Percival [EMAIL PROTECTED]:
No, no! Don't split it up. And you don't need explanations. At
laest, not for what I'm thinking.
(NB: I haven't even glanced at whatever we're talking about)
Err... IIRC we're talking about maybe 5000 lines of code here. Nicolas
himself has
On 03.01.2008 (13:50), Kieren MacMillan wrote:
Hi Graham,
And you don't need explanations.
I disagree!
Me too. For the reasons Kieren gives, and -
Do normal LaTeX users ever look at the details of packages?
I do... but then again, I'm not normal.
- the follow-up question: ARE there any
Hi Jeremiah,
Thank you TWICE over for your help.
You're twice-over welcome! =)
Your code worked perfectly.
I try my best...
Very frustrating!
(This is a rhetorical question; no response necessary.)
Decided to respond anyway!
How can I figure out new code to solve new problems when I
Kieren,
Thank you TWICE over for your help.
Your code worked perfectly. I compared it to my trial code and this is
what you added:
On Dec 27, 2007, at 9:34 PM, Kieren MacMillan wrote:
\context
{
\InnerStaffGroup
Hi Jeremiah,
Thank you for your advice (and ALL your many helpful comments in
the Lilypond archive).
My pleasure!
I have been able to Start my systems exactly the way I want to
Excellent.
How do I name InnerStaffGroup s?
Hopefully the example code (below) will help.
Best wishes,
Kieran,
Thank you for your advice (and ALL your many helpful comments in the
Lilypond archive).
On Dec 22, 2007, at 6:46 PM, Kieren MacMillan wrote:
Hey there!
Questions: Is there a better, easier, more logical, more consistent
solution with better layout?
Have I missed a staff-group
Foremost, a BIG thank-you to everyone who has written, developed,
tweaked, and improved Lilypond and to everyone who has answered
questions on the Lilypond Users Group.
I am preparing a score in Lilypond for full orchestra and want to use
my customary layout (system starts, naming, etc.).
Hey there!
Questions: Is there a better, easier, more logical, more consistent
solution with better layout?
Have I missed a staff-group command for nestled groups (but
using the system start delimiters of my choice)?
I'm assuming you know about InnerStaffGroup?
Certainly that's what I
21 matches
Mail list logo
