In message 4b0bc390.1080...@internode.on.net, Nick Payne
nick.pa...@internode.on.net writes
Carl Sorensen wrote:
On 11/24/09 2:57 AM, Nick Payne nick.pa...@internode.on.net wrote:
James Worlton wrote:
Hi!
In 2.13.6 I did a project and used:
\set Score.markFormatter =
2009/11/24 Han-Wen Nienhuys hanw...@gmail.com:
I think you send a lot of mail. I suggest reading code; if it were
easy, where would the fun be?
Sorry if it sounds angry. My humble opinion is that it's absolutely
NOT FUN to have a future without LilyPond because reading the code was
not easy
James Worlton wrote:
Hi!
On Nov 23, 2009, at 9:26 PM, Nick Payne wrote:
On this subject of set vs override, if I want rehearsal marks to be
boxed letters and also want to use the letter I as a rehearsal mark,
how can I do that. Each set command overwrites the previous value of
the context
On 11/24/09 2:57 AM, Nick Payne nick.pa...@internode.on.net wrote:
James Worlton wrote:
Hi!
In 2.13.6 I did a project and used:
\set Score.markFormatter = #format-mark-box-alphabet
and I got the boxes and the letter I (all in one command!)
Thanks for that. That particular value for
Carl Sorensen wrote:
On 11/24/09 2:57 AM, Nick Payne nick.pa...@internode.on.net wrote:
James Worlton wrote:
Hi!
In 2.13.6 I did a project and used:
\set Score.markFormatter = #format-mark-box-alphabet
and I got the boxes and the letter I (all in one command!)
Thanks for
Nick Payne nick.pa...@internode.on.net writes:
Carl Sorensen wrote:
On 11/24/09 2:57 AM, Nick Payne nick.pa...@internode.on.net wrote:
James Worlton wrote:
Hi!
In 2.13.6 I did a project and used:
\set Score.markFormatter = #format-mark-box-alphabet
and I got the boxes and the
On Tue, Nov 24, 2009 at 3:50 AM, David Kastrup d...@gnu.org wrote:
Sigh. I guess I give up. Yes, I understood that. Pretty much from the
get-go, and also from the manual. The unanswered question is _why_ you
want only _one_ of the two different things happen to _one_ half of the
Han-Wen Nienhuys hanw...@gmail.com writes:
On Tue, Nov 24, 2009 at 3:50 AM, David Kastrup d...@gnu.org wrote:
Sigh. I guess I give up. Yes, I understood that. Pretty much from the
get-go, and also from the manual. The unanswered question is _why_ you
want only _one_ of the two different
Grammatically
\set Context.Property = #value
\set Grob.GrobProperty = #value
both look like \set STRING . STRING = SCHEME
ie. you can't distinguish between both actions if you unify the syntax.
On Tue, Nov 24, 2009 at 11:26 AM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys
Op dinsdag 24-11-2009 om 12:23 uur [tijdzone -0200], schreef Han-Wen
Nienhuys:
Grammatically
\set Context.Property = #value
\set Grob.GrobProperty = #value
both look like \set STRING . STRING = SCHEME
ie. you can't distinguish between both actions if you unify the syntax.
Hmm, why is
On 11/24/09 4:56 AM, David Kastrup d...@gnu.org wrote:
Nick Payne nick.pa...@internode.on.net writes:
Carl Sorensen wrote:
On 11/24/09 2:57 AM, Nick Payne nick.pa...@internode.on.net wrote:
James Worlton wrote:
Hi!
In 2.13.6 I did a project and used:
\set
Mats Bengtsson mats.bengts...@ee.kth.se writes:
Joe Neeman wrote:
On Sat, 2009-11-21 at 22:45 +, Graham Percival wrote:
On Sat, Nov 21, 2009 at 11:31:40PM +0100, David Kastrup wrote:
I don't see a good rationale why \set, \override, \revert, \tweak should
not work on the same
David Kastrup wrote:
We used to have the same command for setting both context and object
properties, see
http://lilypond.org/doc/v2.2/Documentation/topdocs/out-www/NEWS.html
I read
The syntax for setting properties has been simplified: the following
table lists the
Mats Bengtsson mats.bengts...@ee.kth.se writes:
David Kastrup wrote:
We used to have the same command for setting both context and object
properties, see
http://lilypond.org/doc/v2.2/Documentation/topdocs/out-www/NEWS.html
I read
The syntax for setting properties has been
On Mon, Nov 23, 2009 at 3:56 AM, David Kastrup d...@gnu.org wrote:
And I am arrogant enough to believe that if I don't understand a
design decision after a few days of trying, it is likely that
ultimately a lot of people other than myself will be better off if
the distinction gets abolished.
Han-Wen Nienhuys hanw...@gmail.com writes:
On Mon, Nov 23, 2009 at 3:56 AM, David Kastrup d...@gnu.org wrote:
Right now I don't have the necessary clue level. Merely a gut hunch.
Why dont you invest some time to find out how it really works,
What do you think I am doing? Reading
Hi David,
David Kastrup wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
On Mon, Nov 23, 2009 at 3:56 AM, David Kastrup d...@gnu.org wrote:
Right now I don't have the necessary clue level. Merely a gut hunch.
Why dont you invest some time to find out how it really works,
What do you
Ian Hulin i...@hulin.org.uk writes:
David Kastrup wrote:
I will not doctor the documentation before I consider myself having a
clue. And I am nowhere near that yet.
From the bread-crumb trail of your posts on the various lists, it
looks like you're exploring a similar set of avenues I was
On Mon, Nov 23, 2009 at 12:55 PM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
On Mon, Nov 23, 2009 at 3:56 AM, David Kastrup d...@gnu.org wrote:
Right now I don't have the necessary clue level. Merely a gut hunch.
Why dont you invest some time to find out
Han-Wen Nienhuys hanw...@gmail.com writes:
On Mon, Nov 23, 2009 at 12:55 PM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
On Mon, Nov 23, 2009 at 3:56 AM, David Kastrup d...@gnu.org wrote:
Right now I don't have the necessary clue level. Merely a gut hunch.
On Mon, Nov 23, 2009 at 11:10 PM, David Kastrup d...@gnu.org wrote:
* \override and \revert manipulate the defaults stored in said context
property, pushing and popping values off the alist.
This concise hint is wagonloads clearer than what is in the \set vs
\override documentation node.
On this subject of set vs override, if I want rehearsal marks to be
boxed letters and also want to use the letter I as a rehearsal mark, how
can I do that. Each set command overwrites the previous value of the
context property, so if I use:
\set Score.markFormatter =
Hi!
On Nov 23, 2009, at 9:26 PM, Nick Payne wrote:
On this subject of set vs override, if I want rehearsal marks to be
boxed letters and also want to use the letter I as a rehearsal
mark, how can I do that. Each set command overwrites the previous
value of the context property, so if I
Han-Wen Nienhuys hanw...@gmail.com writes:
On Mon, Nov 23, 2009 at 11:10 PM, David Kastrup d...@gnu.org wrote:
* \override and \revert manipulate the defaults stored in said context
property, pushing and popping values off the alist.
This concise hint is wagonloads clearer than what is in
Joe Neeman joenee...@gmail.com writes:
It would certainly be possible, but I think it would be a bad idea. I
think that having two separate commands is much clearer than having a
command with two distinct behaviours depending on what its argument
is.
If the things that happen are
We used to have the same command for setting both context and object
properties, see
http://lilypond.org/doc/v2.2/Documentation/topdocs/out-www/NEWS.html
If you want to bring this issue up again, don't forget to read the
discussions that lead to the current syntax.
/Mats
Joe Neeman
On Sat, Nov 21, 2009 at 8:31 PM, David Kastrup d...@gnu.org wrote:
And I am arrogant enough to believe that if I don't understand a design
decision after a few days of trying, it is likely that ultimately a lot
of people other than myself will be better off if the distinction gets
abolished.
Han-Wen Nienhuys hanw...@gmail.com writes:
On Sat, Nov 21, 2009 at 8:31 PM, David Kastrup d...@gnu.org wrote:
And I am arrogant enough to believe that if I don't understand a
design decision after a few days of trying, it is likely that
ultimately a lot of people other than myself will be
On Sat, 2009-11-21 at 17:22 +0100, David Kastrup wrote:
There is a chapter set vs override in the manual.
I am afraid that I fail to grasp the difference from the chapter.
It says: There are actually two different kinds of properties.
But then it says
Context properties can change
Joe Neeman joenee...@gmail.com writes:
On Sat, 2009-11-21 at 17:22 +0100, David Kastrup wrote:
There is a chapter set vs override in the manual.
I am afraid that I fail to grasp the difference from the chapter.
[...]
If the element description is a _special_ type of context property,
On Sat, Nov 21, 2009 at 11:31:40PM +0100, David Kastrup wrote:
I don't see a good rationale why \set, \override, \revert, \tweak should
not work on the same set of properties (including subproperties). I
don't see an explanation why it makes sense to differentiate between
them.
And I am
On Sat, 2009-11-21 at 23:31 +0100, David Kastrup wrote:
Joe Neeman joenee...@gmail.com writes:
On Sat, 2009-11-21 at 17:22 +0100, David Kastrup wrote:
There is a chapter set vs override in the manual.
I am afraid that I fail to grasp the difference from the chapter.
[...]
If the
On Sat, 2009-11-21 at 22:45 +, Graham Percival wrote:
On Sat, Nov 21, 2009 at 11:31:40PM +0100, David Kastrup wrote:
I don't see a good rationale why \set, \override, \revert, \tweak should
not work on the same set of properties (including subproperties). I
don't see an explanation why
On Thursday 04 May 2006 06:21, Arjan Bos wrote:
Erik,
That's a great document! I've read about half of it now and it does a
very good job to explain to me how LilyPond works. And seeing the
date on the title page, I think I have to congratulate you on your
Masters Degree! Well Done!
Thanks!
Erik,
That's a great document! I've read about half of it now and it does a
very good job to explain to me how LilyPond works. And seeing the
date on the title page, I think I have to congratulate you on your
Masters Degree! Well Done!
Off topic, but are your music streams implemented in
grob is just a silly abbreviation for graphical object. On one hand,
David is absolutely right that far too much of the implementation
structure is visible in the user interface. On the other hand, unless
the current approach to
do settings in LilyPond is revised completely, each user who
Erik Sandberg wrote:
Great! You now officially know more about this area than me, because I
don't have a clue when to use \override or \set. Please take a few
minutes to send me some clarifications or additions for the manual:
Quoting Michael Brennan [EMAIL PROTECTED]:
My simple understanding of it is that:
\set sets a property for the whole context, and the objects contained
in that context while
\override is for a particular graphical object.
Just a little explanation like that, that separates them would be
On 26-Apr-06, at 10:36 PM, Michael Brennan wrote:
David Feuer wrote:
On 4/19/06, Erik Sandberg [EMAIL PROTECTED] wrote:
In 2.8 there's an essential difference between grob and context
properties,
which is visible for end-users: the \tweak command only makes sense
on layout
object
Hi,
I too find the context/grob property distinction not clear and I did not
find the online doc any help in getting through this barrier of
understanding. It is the one most powerful aspect of Lilypond, but the
one aspect which is treated the most meanly in the introductory docs.
Even user doing
For some time, I have been thinking about adding an introductory text to
the Changing Defaults chapter, which introduces all the main methods
to set context and grob properties with one example for each and links
to the more detailed sections. This would be something along the lines of
On 27-Apr-06, at 2:20 AM, Mats Bengtsson wrote:
For some time, I have been thinking about adding an introductory text
to
the Changing Defaults chapter, which introduces all the main methods
to set context and grob properties with one example for each and links
to the more detailed sections.
Citerar Tomas Valusek [EMAIL PROTECTED]:
Hello,
When I first read the manual I didn't see any clear explanation of the
difference,
the docs could be more clear on that point. But when I realized that one
was for grobs
and the other for context, it became much clearer, for me it
Citerar Graham Percival [EMAIL PROTECTED]:
On 26-Apr-06, at 10:36 PM, Michael Brennan wrote:
David Feuer wrote:
On 4/19/06, Erik Sandberg [EMAIL PROTECTED] wrote:
In 2.8 there's an essential difference between grob and context
properties,
which is visible for end-users: the \tweak
Whats a grob?
--
View this message in context:
http://www.nabble.com/Set-vs.-Override---I%27m-confused-t1433228.html#a4124826
Sent from the Gnu - Lilypond - User forum at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
On 4/27/06, Rick Hansen (aka RickH) [EMAIL PROTECTED] wrote:
Whats a grob?
I agree. The user absolutely should not have to know that there is
any such thing.
David
___
lilypond-user mailing list
lilypond-user@gnu.org
Hm. Here's my understanding of it:
You can say it's all about the granularity of the setting. \override
manipulates
settings which are specific to one graphical object/grob (e.g. a NoteHead).
\set
changes settings on a higher level, and can modify more than one type of
grob.
There is at
On Tuesday 11 April 2006 23:56, Werner LEMBERG wrote:
\set: set the value of a context property
\override: set the value of a layout object property
I've always wondered why it isn't possible to unify them...
In 2.8 there's an essential difference between grob and context properties,
which
On 4/19/06, Erik Sandberg [EMAIL PROTECTED] wrote:
In 2.8 there's an essential difference between grob and context properties,
which is visible for end-users: the \tweak command only makes sense on layout
object properties, not on context properties. This difference might make it
easier for
In 2.8 there's an essential difference between grob and context
properties, which is visible for end-users: the \tweak command
only makes sense on layout object properties, not on context
properties. This difference might make it easier for new users to
understand grob properties.
In 2.8 there's an essential difference between grob and context properties,
which is visible for end-users: the \tweak command only makes sense on
layout
object properties, not on context properties. This difference might make it
easier for new users to understand grob properties.
David Feuer wrote:
On 4/19/06, Erik Sandberg [EMAIL PROTECTED] wrote:
In 2.8 there's an essential difference between grob and context properties,
which is visible for end-users: the \tweak command only makes sense on layout
object properties, not on context properties. This difference might
[...] when I realized that one was for grobs and the other for
context, it became much clearer, for me it helps separating and
understanding grobs and contexts.
A big help would be a simple means to distinguish grobs and context
properties. For example, context property names could always
Hello,
When I first read the manual I didn't see any clear explanation of the
difference,
the docs could be more clear on that point. But when I realized that one
was for grobs
and the other for context, it became much clearer, for me it helps
separating and understanding
grobs and contexts.
Werner LEMBERG writes:
\set: set the value of a context property
\override: set the value of a layout object property
I've always wondered why it isn't possible to unify them...
Or until that time have explicit naming.
Jan.
--
Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music
\set: set the value of a context property
\override: set the value of a layout object property
The followup question is obvious, but I leave it to you to think about it
and see if you get any further.
/Mats
Tomas Valusek wrote:
Hello,
I've read thoroughly LilyPond's Users Manual and I
The followup question is obvious, but I leave it to you to think about it
and see if you get any further.
I've been wondering for some time if the distinction is a helpful one,
but I suspect changing it now would involve too much internal
tinkering, not to mention breaking of old scores.
Geoff
Quoting Geoff Horton [EMAIL PROTECTED]:
The followup question is obvious, but I leave it to you to think about it
and see if you get any further.
I've been wondering for some time if the distinction is a helpful one,
but I suspect changing it now would involve too much internal
tinkering, not
\set: set the value of a context property
\override: set the value of a layout object property
I've always wondered why it isn't possible to unify them...
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
59 matches
Mail list logo
