2013/10/26 David Kastrup :
> I've now pushed stable/2.18 and synchronized translations to it.
> I hereby declare the stable/2.18 branch my sole property, to be ruled
> over dictatorially. As long as nobody else pushes to it without my
> permission, I pledge to keep and lead it to releasable state
2013/10/22 Janek Warchoł :
> Hi,
>
> 2013/10/22 Jean-Charles Malahieude :
>> If it could by chance "ameliorate" this situation as well:
>>
>> \relative c { \clef bass f4( f,) b2 }
>>
>> in order to get what Breitkopf proposes, I would thank you SO m
Hi all,
I see a lot of discussion - great! My apologies for not answering
earlier - i am focusing on \shape improvements (almost finished).
I'll find some time today or tomorrow to analyze your emails, and will
get back to you on Sunday.
Many thanks!
Janek
2013/10/23 Keith OHara :
> On Wed, 23
Hi Keith,
2013/10/23 :
>
> On 2013/10/23 04:22:22, Keith wrote:
>> The commit message makes it sound like there was a blunder in the
>> direction that
>>
>> the old code moved the slur. I don't see any such problem.
>>
>> It looks like the old code intentionally moved the middle of the slur
>> a
2013/10/23 David Kastrup :
>
> Ubuntu 13.10 is delivered with LilyPond 2.16.2 built using a Metapost
> version of 1.802. Consequently, all the included fonts look like crap.
>
> http://code.google.com/p/lilypond/issues/detail?id=3539>
>
> Of course, this was sort of predictable. Would we have bee
Hi,
2013/10/22 Jean-Charles Malahieude :
> If it could by chance "ameliorate" this situation as well:
>
> \relative c { \clef bass f4( f,) b2 }
>
> in order to get what Breitkopf proposes, I would thank you SO much!
That's a different issue. Maybe i could improve the default
formatting of such s
As a side-effect of working on improving \shape, i've improved the
slur formatting engine itself.
Please review:
http://code.google.com/p/lilypond/issues/detail?id=3628
https://codereview.appspot.com/15400049
cheers,
Janek
___
lilypond-devel mailing lis
Hi,
i'm browsing slur formatting code and i found why slurs in these cases
{
\slurUp
d'2( f')
\slurDown
c''2( e'')
}
are soo ugly.
I facepalmed really hard :-)
Expect an awesome patch tomorrow.
best,
Janek
<>___
lilypond-devel mailing lis
2013/10/19 Joseph Rushton Wakeling :
> On 16/10/13 00:11, Janek Warchoł wrote:
>>
>> I need at least 2 people who'd like to experiment with me - doing this
>> alone doesn't make sense. Colin, Joe - are you still interested?
>> Anyone else?
>
> Yup
Hi,
2013/10/20 SoundsFromSound :
> Hello,
>
> I stumbled upon this website recently and just noticed they have this font
> offered for sale, dubbed "Lilypond look is here!"
>
> Do any of you know anything about this vendor and/or fonts? I'm
> curious...anyone try these fonts before?
>
> Paris...
2013/10/19 :
> I cannot review _and_ comment inline, when I click on side-by-sdie diffs
> I get 'error chunk mismatch'. Does anyone else?
me too.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-dev
2013/10/16 Colin Campbell :
> On 13-10-15 04:11 PM, Janek Warchoł wrote:
>> Let's try out some code-development platforms and see if using them
>> would make developing LilyPond easier. GitHub.com is out of question,
>> so we have to check gitlab.com and gitorious.or
2013/10/16 :
> That's not really the main point. It would have been simple previously
> to make \tweak be equivalent to \override rather than \once \override
> when used on symbol lists.
>
> \tweak syntax for overrides is not really pretty, but it makes it easy
> to implement mixed tweaks/overrid
I'm back... better late than never.
Let's try out some code-development platforms and see if using them
would make developing LilyPond easier. GitHub.com is out of question,
so we have to check gitlab.com and gitorious.org.
I need at least 2 people who'd like to experiment with me - doing this
a
2013/10/2 :
>
> https://codereview.appspot.com/13720049/diff/1/scripts/auxiliar/strip-whitespace.py
> File scripts/auxiliar/strip-whitespace.py (right):
>
> https://codereview.appspot.com/13720049/diff/1/scripts/auxiliar/strip-whitespace.py#newcode15
> scripts/auxiliar/strip-whitespace.py:15: prin
2013/9/27 :
> LGTM. You might want to add to your comment at the top: "Also convert
> the file to Unix line endings."
Added.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
2013/10/15 :
> On 2013/10/15 18:04:43, janek wrote:
> Well, that's the slightly icky thing. The \offset is with respect to
> the situation you'll get when doing \revert Arpeggio.positions
> afterwards. So if you want to make a _relative_ offset to the first
> setting, you have to do
> \temporary
2013/9/29 David Kastrup :
> "Phil Holmes" writes:
>
>> From: "Eluze"
>>>
>>> I will treat what's left tomorrow (I'm not the only bug squad member
>>> allowed to do it!)
>>
>> But you seem the most efficient at this :-)
>
> So what? If you find that some worker in a factory line is more
> efficie
2013/9/27 Janek Warchoł :
> 2013/9/26 Colin Campbell :
>> Well, I'm unskilled and uneducated in most areas useful to development and
>> change management, but I'm offering to help in whatever way you think I can.
>
> Excellent! We'll probably start b
2013/9/26 Colin Campbell :
> On 13-09-26 03:48 AM, Janek Warchoł wrote:
>>
>> Hi all,
>>
>> after a long discussion i think it's time to gradually move towards
>> doing things :-)
>>
>> David is going to talk with Savannah people - that'
Hi,
2013/9/26 Hans Aberg :
> On 26 Sep 2013, at 17:16, Phil Holmes wrote:
>> Joseph Wakeling wrote:
>> I was also rather discouraged by the fact that the quarter-tone arrow
>> notation issue didn't find a solution -- see:
>>> https://code.google.com/p/lilypond/issues/detail?id=1278
>>>
>>
>> I t
2013/9/26 :
> On 2013/09/26 10:51:34, janek wrote:
>> Uh, David, thanks for this explanation, but i'm afraid it was not
>> needed. If the code doesn't need a comment, just say so.
>>
>> Now, speaking in general: i don't understand that when Mike submits a
>> patch, you often complain that it's no
Hi,
to make things clear: i do not intend to attack anyone personally, or
imply that anyone has bad will or malicious intentions. I only want
to explain how the situation looks like from my point of view.
2013/9/26 Phil Holmes :
> Janek wrote:
>>2013/9/26 Phil Holmes :
>> > Good luck. Let me gi
2013/9/25 :
>
>> > On 2013/09/24 07:44:44, janek wrote:
>> >> Hmm. From my point of view, this deserves some comment
>> >> (but i don't insist).
>
> Well, multiple matching regexps are messy and might call for an
> appropriate comment. But the whole point of the change is not to have
> multiple m
2013/9/26 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>
>> after a long discussion i think it's time to gradually move towards
>> doing things :-)
>>
>> David is going to talk with Savannah people - that's great!
>> Ot
Hi all,
after a long discussion i think it's time to gradually move towards
doing things :-)
David is going to talk with Savannah people - that's great!
Other things that are worth looking at are:
- gitorious
- gerrit
- something else i've forgotten?
I'm going to have a short break from LilyPond
2013/9/25 Jan-Peter Voigt :
> Hi David,
> lilypond has a header field "piece", which is meant for movement names. To
> have this field centered - default is left above the score - one has to
> modify scoreTitleMarkup in paper.
> Perhaps other markups would be nice. (a markup is a template by itself
2013/9/25 :
> On 2013/09/24 22:01:17, janek wrote:
>> Thanks, this should help me understand what's going on.
>
> Without looking at the code, that's not all that likely.
uh, my point was that i wanted to see the example before reading the
code so that i can understand the code in the context of
Hi David,
2013/9/24 :
> Do you have an actual problem with how the new code is
> written in comparison to the old code?
No, not at all! I apologize for not making my intentions clearer. I
asked for an example not because i doubted your patch - i just wanted
to have some output to look at, so t
> Here are the Git-formatted patches.
thanks, this makes things easier for us.
2013/9/21 Keith OHara :
> Janek Warchoł gmail.com> writes:
>> As for the patches themselves, are you using Git? It would be
>> slightly more convenient for us if you sent us "Git-formatted&q
Hi,
2013/9/24 Joseph Rushton Wakeling :
> I'd be much more willing to temporarily put in that effort to work aroundr su
> those issues, if I felt that at least there was recognition of the usability
> issues I (and others) have raised. But every time there is this reaction:
> "Why don't you do it
2013/9/23 David Kastrup :
> It would be actually a rather small step: replacing Rietveld with
> something allegedly better catering to Git, hopefully facilitating the
> review of commit series rather than single commits.
>
> Quite a few of our most troublesome commits are of the "dozen unrelated
>
When i go to http://lilynet.net/, i see
Fedora Test Page
This page is used to test the proper operation of the Apache HTTP
server after it has been installed. If you can read this page, it
means that the web server installed at this site is working properly,
but has not yet been configured
It's l
2013/9/22 David Kastrup :
> "Phil Holmes" writes:
>> IMHO this is solving a problem that doesn't exist. Using LilyDev
>> (possibly in a Virtual Machine) provides git and git-cl. Git allows a
>> developer to create a patch with 2 commands: git commit and git
>> format-patch. That can be uploaded
2013/9/22 Janek Warchoł :
> 2013/9/22 Phil Holmes :
>> IMHO this is solving a problem that doesn't exist. Using LilyDev (possibly
>> in a Virtual Machine) provides git and git-cl. Git allows a developer to
>> create a patch with 2 commands: git commit and git for
2013/9/22 Phil Holmes :
> IMHO this is solving a problem that doesn't exist. Using LilyDev (possibly
> in a Virtual Machine) provides git and git-cl. Git allows a developer to
> create a patch with 2 commands: git commit and git format-patch. That can
> be uploaded to Rietveld with a single comm
2013/9/21 Phil Holmes :
> FWIW, I find my build machine on Ubuntu is much faster.
I've noticed that compiling LilyPond scores is 2-3 times faster on my
Ubuntu 12.04 than on Windows 7. Interesting.
Janek
___
lilypond-devel mailing list
lilypond-devel@g
2013/9/20 Heikki Tauriainen :
> Hi,
>
> [...] I have a series of patches to add functionality to control
> additional MIDI parameters (besides the MIDI instrument) directly from
> within the LilyPond source (namely, pan position, and reverb and chorus
> effect levels). I post and describe them her
2013/9/19 David Kastrup :
> Werner LEMBERG writes:
>> I'm now even more convinced that this is a bug.
>
> It very much looks like "working as designed".
Well, i suppose Werner meant "this is a bug in the design".
> Poking exceptions into
> it will only make things more confusing: at least now th
2013/9/19 Werner LEMBERG :
> I would expect that `opus' appears vertically before `top1'.
>
> Is this a bug? Otherwise, I suggest to change the code so that the
> header block really stays together.
I suppose that this is a consequence of having _two_ header blocks -
one for \book and one for \sc
:(
2013/9/17 David Kastrup :
> David Kastrup writes:
>
>> This is a reminder that next weekend, Sept 20th to 24th, there will be a
>> LilyPond developer and user meeting in Waltrop, Germany.
>
> Ok, the current possible participant list would look like the following:
> Jan, Janek, Harm and myself
2013/9/18 Phil Holmes :
> - Original Message - From: "David Kastrup"
>> Urs Liska writes:
>>> When review is finished prepare a patch file (or series of patch
>>> files) and find someone with push access whom I can send it to?
>>
>> Yup.
>
> Strictly, not necessarily even that. I've push
2013/9/17 David Kastrup :
> Now basically we have to split these into two different sets of
> requirements: Savannah does not provide accounts or services to the
> general public; its services will be restricted to actual developers.
>
> But what you list above mostly is _not_ related to participat
2013/9/18 Janek Warchoł :
> 2013/9/17 Urs Liska :
>> But as far as I've understood, code doesn't get into upstream master that
>> way anyway, there is the Rietveld code review stage in between?
>> How do commits (from developers) actually end up in master?
>
>
2013/9/17 Urs Liska :
> But as far as I've understood, code doesn't get into upstream master that
> way anyway, there is the Rietveld code review stage in between?
> How do commits (from developers) actually end up in master?
> Are they a) pushed to some branch, the diff uploaded to Rietveld, and u
2013/9/18 David Kastrup :
>
>>> The one area where I'd consider a web interface a possibly good
>>> tradeoff of matching tools to skills would be translation work: that
>>> could/should be a lot more crowdsourced than it is now. It turns out
>>> that organizing and tracking incremental translation
2013/9/18 David Kastrup :
> Comparing the amount of code actually getting reviewed and the amount of
> development getting done, the Linux kernel does not seem to suffer all
> that badly from working with a patch/mail-centric [review] workflow.
>
> Of course there are some reasons that don't hold f
ng some other features.
>> In my opinion Github is the best tool for the job, and i'm going to
>> use it. I'm not forcing anyone to use it,
>
> You are essentially currently trying to migrate work on the LSR there:
>
> From: Janek Warchoł
> Subject:
2013/9/17 David Kastrup :
> James writes:
>
>> Hello
>>
>> I'm having problems with my broadband at home and am not in the office
>> this week. It means that I cannot run patchy-test or do
>> Countdowns. Patchy-merge runs from my office machine as well as from
>> home, so that is covered so depend
g the change, a pull
request is sent to the original repository). Also, being able to post
comments on commits, and integration of pull requests with code
review. And the ability to update a pull request with new commits.
As far as i know Savannah doesn't have these features. When it will
h
2013/9/16 Mark Polesky :
> what does the M mean on Rietveld?
> I couldn't find an answer in their docs.
I'd guess that M means Modified, A - Added.
No idea what files without any letter would be.
Janek
___
lilypond-devel mailing list
lilypond-devel@gnu
2013/9/16 Graham Percival :
> On Mon, Sep 16, 2013 at 10:49:42AM +0200, David Kastrup wrote:
>> > What's wrong with GitHub, anyway?
>>
>> It requires separate accounts and credentials (much more likely to be a
>> target for attacks), has its own "terms of service", may choose to
>> discontinue proj
Hi,
in the meantime i saw Graham's email, so just a short reply:
2013/9/16 David Kastrup :
> [github] can cause tool lock-in and so on,
every tool can. In this case, i think that the degree of lock-in is
small and probably negligible (as Graham said, git repositories are
portable).
Note that i
2013/9/16 Janek Warchoł :
> 2013/9/16 David Kastrup :
>> Janek Warchoł writes:
>>
>>> lol of the month! Some time ago I've discovered a user named
>>> 'lilypond' on GitHub, who seemed to be pretty inactive. I thought
>>> that it w
2013/9/16 David Kastrup :
> Janek Warchoł writes:
>
>> lol of the month! Some time ago I've discovered a user named
>> 'lilypond' on GitHub, who seemed to be pretty inactive. I thought
>> that it would be nice to have a github organization with this
lol of the month! Some time ago I've discovered a user named
'lilypond' on GitHub, who seemed to be pretty inactive. I thought
that it would be nice to have a github organization with this name,
and i was going to contact him... but it turned out that the account
belonged to me! LOL!
Anyway, I'v
Hi,
2013/9/14 David Kastrup :
> This is a reminder that next weekend, Sept 20th to 24th, there will be a
> LilyPond developer and user meeting in Waltrop, Germany. After the
> first attempt to schedule the meeting in August, we rescheduled in order
> to better meet people's calendars.
I'd like t
Hi,
sorry - this email slipped past my eyes...
2013/9/9 David Kastrup :
> philehol...@googlemail.com writes:
>
>> error: some local refs could not be updated; try running
>> 'git remote prune origin' to remove any old, conflicting branches
>
> Well, yes. Either do that, or look up how to prune
Hi all,
2013/9/11 Franciszek Boehlke :
> Hi,
> Janek has just pushed newer (still development, though) version of my patch
> to dev/frax/colorful-make branch. It is almost completely rewritten and
> greatly simplified, and fixes several mentioned issues. I'd be happy if you
> give it a try and sha
2013/9/5 Mark Polesky :
> Janek Warchoł wrote:
>> mmm, this looks impressive!
>> Since this cannot be placed in LSR, maybe you'd like add
>> it to a snippet repository which I've just created
>> together with Urs?
>> http://github.com/openlilylib/snipp
Hi!
2013/9/5 Mark Polesky :
> Hi everyone,
>
> On a whim I decided to try to implement a roman numeral
> harmonic analysis interface, entirely in scheme.
mmm, this looks impressive!
Since this cannot be placed in LSR, maybe you'd like add it to a
snippet repository which I've just created togethe
A small update:
2013/8/21 Janek Warchoł :
> It was my dream for more than a year to automate the process of
> compiling custom LilyPonds from source code in a way that would allow
> to use these versions completely independently, and at the same time
> have them linked together.
2013/7/19 :
> On 2013/07/19 19:35:13, Mark Polesky wrote:
>> Is there no way to extract the averages of the NoteColumn
>> X-positions between two voices? So given these voices:
>
> Please check out
> http://code.google.com/p/lilypond/issues/detail?id=3232>. Its
> original title was "LilyPond sho
I like this! Please put this example into commit message and/or a
comment in the code :)
best,
Janek
2013/8/27 :
> Reviewers: janek,
>
> Message:
>
> On 2013/08/27 07:43:41, janek wrote:
>>
>> Hi,
>
>
>> could you write a 2-sentence explanation why we want to do this?
>
>
>> Janek
>
>
> \new St
ok, thanks.
2013/8/27 :
> Reviewers: janek,
>
> Message:
>
> On 2013/08/27 07:48:08, janek wrote:
>>
>> Looks like a good thing to do, but what does this change mean?
>
>
> It means it lets the parser accept symbols after \new, \context, \unset
> and implicit \set. After the symbol list changes
Hi,
sorry for delay...
2013/8/23 Urs Liska :
>
> "Janek Warchoł" schrieb:
>>I've realized that while git log is enough for viewing code,
>>commenting on it should be made more convenient - sorry! I've
>>uploaded the diff to Rietveld: https://coder
Hi,
2013/8/26 Frédéric Bron :
> Hi,
> When I use git-cl, a pop-up window opens with vim. I typed a message
> but couldn't find it anywhere in the issue tracker nor in codereview.
> Also, I noticed that git-cl was continuing in the initial terminal
> while I was typing the message in the popup wind
Hi all,
every now and then many of us need to use different versions of
LilyPond - this is especially true for developers. In fact, most
developers usually want many concurrent LilyPond versions built from
the source code.
It was my dream for more than a year to automate the process of
compiling
2013/8/20 Frédéric Bron :
[.]
Thanks for your comments, Frederic! I've added them to the Rietveld
issue for your convenience (and answered two of them). Let's continue
the discussionn there: https://codereview.appspot.com/13051044/
___
lilypond-de
Hi,
2013/8/20 Frédéric Bron :
>> For the programmers, i'd like to ask you to look at the branch
>> dev/tie-crusade/comments
>> and read the comments we've added to the code together with Franek.
>
> Just in case some would need, we can read all the added comments with:
> git diff 5c99661096f110920
2013/8/19 :
>
> https://codereview.appspot.com/13007044/diff/1/Documentation/changes.tely
> File Documentation/changes.tely (right):
>
> https://codereview.appspot.com/13007044/diff/1/Documentation/changes.tely#newcode76
> Documentation/changes.tely:76: @end lilypond
> Did you mean to use an @exam
Hi,
2013/8/15 David Kastrup :
> Franciszek Boehlke writes:
>
>> I think I can promise to support and maintain it.
>
> If we have a subsystem depend on continued support by a single person,
> it must be easy to remove the subsystem as a whole.
>
> Consider it LilyPond's life insurance. We don't r
2013/8/19 Phil Holmes :
> - Original Message - From: "Janek Warchol"
>> What you said would be true if the snippets were so simple that they
>> never change. But they do change.
>
> Hardly ever. I maintain the current LSR and the changes are so infrequent I
> often forget to check whether
2013/8/19 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>
>> 2013/8/19 Phil Holmes :
>> > However, my other opposition to git for this
>> > purpose is that it's intended as a Version Control system, which is
>> > com
Hi,
some things were already answered by other people
2013/8/19 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>> A valid concern, but i have a counterargument: there is a web
>> interface for git that allows you to copy-and-paste code directly in,
&g
2013/8/19 Werner LEMBERG :
>> Well, one question may be whether git could be an alternate
>> interface into the LSR. In a limited manner, it already is
>> (snippets migrate back from LilyPond git repository into the LSR).
>
> Actually, I like the idea of using git for the LSR *as the storage*.
> E
2013/8/19 Urs Liska :
> PS: I'd also second the idea of hosting lilypond on a more accessible server
> (if that doesn't imply complicated side-effects). It is so easy to create a
> fork and open a pull request, I'm sure such a step would increase the number
> of contributions by people who can't or
2013/8/18 :
> WOW!! I've just found this patch and this is awesome!!
> In my eyes, this single patch made LilyPond 2 times more user-friendly.
>
> I think that this is totally worth of an entry in "changes" - i would be
> soo sorry if i hadn't found this change by accident today. Would
> you
2013/8/19 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>> After some thinking, i came to the conclusion that LSR should be
>> redesigned.
>> Fristly, it should be a git repository, to make collaboration easy -
>> when something&
Hi,
2013/8/17 Janek Warchoł :
>
> 2013/8/14 Thomas Morley :
>> The right place for them would be the LSR, _if_ the LSR would be able
>> to compile them and not use a LilyPond-version far too old for many of
>> my ideas.
>>
>> There were some insinuations on t
2013/8/18 David Kastrup :
> It's not entirely clear since you can't write
>
> mus = \addlyrics ...
>
> anyway. The main problem is that \mus differs from #mus in that it
> needs to be evaluated _before_ a token can be handed to the parser.
> This will only change once every \xxx has the same token
2013/8/18 Thomas Morley :
> 2013/8/18 Janek Warchoł :
>> Hi Harm,
>>
>> 2013/8/18 Thomas Morley :
>>> Hi Janek,
>
>>>> side-question: what git version do you have? ('git --version')
>>> git version 1.7.0.4
>>> (from lilyde
Hi Harm,
2013/8/18 Thomas Morley :
> Hi Janek,
>
> 2013/8/18 Janek Warchoł :
>> Hi,
>>
>> 2013/8/18 Thomas Morley :
>>> 2013/8/18 Janek Warchoł :
>>>> PS if anyone needs *any* help with git, i'll gladly help!
>>>
>>> let
Hi,
2013/8/18 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>>
>> 2013/8/18 Thomas Morley :
>>> Recently you posted
>>> http://lists.gnu.org/archive/html/lilypond-devel/2013-08/msg00138.html
>>> with the public branch
Hi,
2013/8/18 Thomas Morley :
> 2013/8/18 Janek Warchoł :
>> PS if anyone needs *any* help with git, i'll gladly help!
>
> let me take you at your word.
excellent! I like it when my words are taken seriously :-)
> Recently you posted
> http://lists.gnu.org/archive/h
PS if anyone needs *any* help with git, i'll gladly help!
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi folks,
it's time to start collaborating on LilyPond ties with a bigger group
of people (you don't have to be a programmer to help!) :-)
The most important thing at the moment is to have many people - both
programmers and non-programmers - study the details of the problem and
proposed solution
2013/8/18 :
> On 2013/08/18 10:20:07, janek wrote:
>> Sorry for a possibly ignorant question: will this patch also remove
>> the error in case of
>> mus = { a }
>> \mus
>> ?
>
> No.
>
>> If not, would there be an easy way to fix that?
>
> Well, we could delete all functionality of \addlyrics etc
>
2013/8/18 Graham Percival :
> On Fri, Aug 16, 2013 at 02:32:35PM +0100, Phil Holmes wrote:
>> >On Fri, Aug 16, 2013 at 08:53:44AM +, k-ohara5...@oco.net wrote:
>> >>I would be tempted to simply insert \bar "|." into the longer examples
>> >>in the LM, with no explanation, so it is there for cur
2013/8/17 :
> On 2013/08/16 08:59:36, Graham Percival wrote:
>> I don't think we need to respond to every single doc suggestion;
>> often users are unaware of the trade-offs we've chosen or are
>> particularly focused on their application domain ("why bother with
>> stuff for singers? the LM shou
2013/8/17 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
> I'm not sure what you mean.
> Maybe i didn't make myself clear? Here's what i'd like to do:
> X-offset of a Stem is currently calculated by a function
> Stem::offset_callbac
2013/8/15 :
> "Keith OHara" writes:
>
>> '!' also looks like a staccatissimo,
>> is a stop character so conceptually related to the '.' for staccato,
>> conflicts less with the use of ''' in pitches:
>>e'4-! cs-! bf-! g-! e'-! cs-! \tuplet3/2{bf-> g-> e->}
>>e'4-' cs-' bf-' g-' e'-' cs-'
Hi,
2013/8/14 Thomas Morley :
> 2013/8/14 Janek Warchoł :
>> Harm and David N. (and some other people) write lots of very advanced
>> (and very helpful!) Scheme functions. These funcitons are improved
>> over time, and there is a problem related to that: it's easy to ge
Hi Phil,
2013/8/14 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>> I'd like to change stem and flag code so that stems, flags and
>> noteheads are attached to each other using generic functions from
>> Self_alignment_interface inste
Hi Phil,
2013/8/14 Phil Holmes :
> - Original Message - From: "Janek Warchol"
>> Are you still working on this? I was looking at this area of the code
>> with my alignment work
>> (http://code.google.com/p/lilypond/issues/detail?id=3239 and others,
>> which are the foundation for actually
Hi,
my cousin Franek changed the output of make from a heap of unreadable
gobbledygook to some delicious eye-candy! Checkout branch
dev/frax/colorful-make and build lilypond. How do you like it?
As for me, i can spend whole day just looking at lilypond being built.
I think we should add this t
Hi,
Harm and David N. (and some other people) write lots of very advanced
(and very helpful!) Scheme functions. These funcitons are improved
over time, and there is a problem related to that: it's easy to get
lost in all the email threads about them, and it's not always obvious
where the most rec
2013/8/14 :
> I'm in a rush right now so can't test. But would that even help with
> whole notes and breves?
Good point. But i think that this can be added anyway, as it makes
sense in itself.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
ht
2013/8/14 :
> I don't really agree. staccato is -. so it seems natural for me to have
> staccatissimo as -! (I mean, it was -| before). In addition, ' and ,
> are slanted in most fonts and that does not really match the visuals of
> staccatissimo.
>
> I crosschecked with the parser and it would
Hi Phil,
2013/7/30 Phil Holmes :
> I've been experimenting with alternative algorithms to create the flags used
> in mensural notation (see
> http://code.google.com/p/lilypond/issues/detail?id=3105), and part of the
> problem appears to be that the stems aren't attached symmetrically to the
> note
201 - 300 of 1382 matches
Mail list logo
