Re: Fw: new message

[mskala]

On Mon, 25 Apr 2016, Simon Albrecht wrote:
> I very much hope that you didn’t click the link. Of course it’s spam. Can we
> do anything about it?

Blocking HTML messages from the mailing list would block these and most
other spam messages.

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[Wols Lists]

On 25/04/16 23:48, J Martin Rushton wrote:
> Your comments about broadband being ubiquitous are unfounded.  Even
> where broadband is claimed, plenty of people still struggle on with
> around 1Mb/s.  Using BT in the south east of England we only get 1.6
> Mb/s and I don't appreciate sitting and waiting just so that exploding
> blancmange can be projected onto my screen.  Stick to ASCII for text
> and keep the fancy stuff for when it's needed.

I'm lucky - living 100 yards from the exchange, I get 17Mb over copper -
that is when I've got a working DNS! Half the time it seems my internet
link is fine, but unusable because BT's DNS has decided to stop working!

(And of course, I can't get the widely touted super-fast Infinity -
otherwise known as Fibre To The Cabinet - because I don't have a cabinet!!!)

Cheers,
Wol

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Multi-measure rests and mark collisions ...

[Wols Lists]

On 25/04/16 05:31, David Wright wrote:
> On Sun 24 Apr 2016 at 19:18:01 (+0100), Anthonys Lists wrote:
>> On 24/04/2016 03:13, David Wright wrote:

>>
>> Ah - does that mean the rehearsal mark would happily overwrite the
>> blank space at the start of the other markup string?
> 
> Typically, yes.

Ah good ...
> 
>> But as for "why would I want to do that" - to serve as an example
>> maybe. Let's change it then. Get rid of the tempo. The title would
>> still collide with the rehearsal mark, and it would still take three
>> lines - I wouldn't save a line. But shift the title a couple of mill
>> to the right, and it would drop down and save us a line. SAVING
>> VERTICAL SPACE is the point.
>>>

>>
>> Most people? Most people probably give up and go back to Sibelius,
>> or Finale, or whatever. My day job was programming, and I haven't
>> managed to get to grips with Scheme (it was FORTRAN/C, so Scheme is
>> a bit of a culture shock :-) because time to concentrate and learn
>> is a luxury :-(
> 
> Fair enough. I was making the point that LP sometimes looks like a
> programming language but isn't actually one.
> 
> But it never ceases to amaze me how, if you post a reasonably
> well-defined problem here, someone often posts a scheme solution.
> But you have to factorise your problem into chunks that people
> will feel inclined to tackle.

Well, I would like to tackle them myself. But, as I said, time to
concentrate is a luxury (I'm a carer, and dealing with someone with
memory problems can be very difficult :-(
> 
>>> Why not push the rehearsal mark left if you want loads of text to the right?
>>> I don't get the bit about notes in a MMR. Isn't that a contradiction?
>>
>> Not really. My modus operandi is
>>
>> voiceStaff = ...
>> voiceInstrument1 = ...
>> voiceInstrument2 = ...
>>
>> \score {
>>   <<
>> voiceStaff
>> voiceInstrument1
>>   >>
>> }
>> \score {
>>   <<
>> voiceStaff
>> voiceInstrument2
>>   >>
>> }
>>
>> The problem is that the contents of voiceInstrumentx has a *major*
>> influence on the way the contents of voiceStaff is displayed :-(
>> Instrument1 may have an MMR, Instrument2 may have notes, they affect
>> the bar spacing in different ways, and I may get markup collisions
>> in one part, and no collisions in the other. Basically, lily is
>> setting the notes, and then fitting the markup over the notes. There
>> are occasions when you want to set the markup and then fit the notes
>> under it.
> 
> Without wishing to imply that I could code it, that's why you might
> have fragments of markup suitable for notes, and others for MMRs,
> and then select between them to assemble each part.

In other words, put loads of \tags or instrument-specific stuff in
voiceStaff, which is supposed to be instrument-independent :-(
> 
> Why would you "go back to" Sibelius? Would that automate this?
> Even if you had to assemble the fragments manually for each part,
> that would be simpler, I'd have thought. You may or may not end up
> with a part like one of mine:
> texttenorsA = \lyricmode {
>   \Tteetuka \Tteetuka \Tteetuka \Tteetuka \Tteetuka \Tteetuka \Tteetuka 
> \Tteetuka
>   \barNumberCheck #17
>   \Tteetuka \Tteetuka \Ttravi \Ttravs \Ttravs \Ttravr \Ttravs \Ttravs
>   \Ttravz
>   \barNumberCheck #27
>   \Tzumpaka \Tzumpaka \Tzumpaka \Tzumpaka \Tzumpaka \Tzumpaka \Tzumpaka 
> \Tzumpaka \Tzumpakaz
>   Oo __ _ _
>   \barNumberCheck #35
>   \Tvumtb \Ttravs
> }
> where I'm selecting from a menu of lyrics fragments.
> 
?

And let's say the piece is SSAATTBB, could you combine that single
lyrics part with two different tenor melody parts, to give two different
part-sheets? Because THAT is the problem I would like to solve.

>>>
>>>
>> And you've given me a wonderful example of what I want :-) Let's say
>> a new tune starts at B, so I put a tune name there. You can't play
>> two tunes at once, can you? But you've got two tune names stacked
>> one above the other ... (Yes I know you can play two tunes at once,
>> but it's not normal :-) And you could get stacking tempi the same
>> way...
> 
> If the names of the tunes are so important (which is pretty
> unusual for a part), then why not place them underneath (like "halt!"
> in my example) so they don't interfere with the tempos.

Because I don't give a monkeys about interfering with tempi? Because I
*DO* give a massive monkeys about wasting vertical space, and moving the
tune-name underneath gains me nothing?

> If the names of the tunes are long, you're already going to have to
> deal with how they mesh with your linebreaks (which is tricky
> because you usually don't know where the latter will fall).
> 
> You could shrink the names of the tunes. You could print them in a
> heap at the foot of the page. You could leave them out of the parts,
> as is conventional. You could decide on your priorities.
> 
>> At the end of the day, the basic problem is that lily, by default,
>> stacks markup upwards. There is no way to tell it that markup should
>> 

Re: Replying to posts

[Kieren MacMillan]

Hello all,

> keep the fancy stuff for when it's needed.

Like PGP?  ;)

Regards,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[J Martin Rushton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 25/04/16 13:39, Tim McNamara wrote:
> On Apr 25, 2016, at 5:00 AM, Andrew Bernard
> >
> wrote:
> 
>> Greetings All,
>> 
>> In a recent post David Wright asks of  a user:
>> 
>>> Please configure your client to post a text equivalent of your
>>> HTML
>> code.
>> 
>> He also asked me to do that.
> 
> The reality is that the world, given the ubiquity of broadband and 
> graphical interfaces, has moved on from plain text.  It is no
> longer the standard and has not been for a decade or more- most
> Internet users have, I suspect, no knowledge of this old standard
> any longer. Expecting others to accommodate what is now an out of
> date standard will simply continue to create issues.  It's like
> expecting web developers to accommodate lynx in creating Web pages-
> probably not going to happen very often.
> 
> One can choose to use text-only software but at this point we are 
> responsible for our own problems if we do.  The world has changed
> and left us behind.
> 
> 
> ___ lilypond-user
> mailing list lilypond-user@gnu.org 
> https://lists.gnu.org/mailman/listinfo/lilypond-user

Your comments about broadband being ubiquitous are unfounded.  Even
where broadband is claimed, plenty of people still struggle on with
around 1Mb/s.  Using BT in the south east of England we only get 1.6
Mb/s and I don't appreciate sitting and waiting just so that exploding
blancmange can be projected onto my screen.  Stick to ASCII for text
and keep the fancy stuff for when it's needed.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJXHp64AAoJEAF3yXsqtyBldjcQAJY01Tps3TH8XT15lPWPRnde
HeI4iulwxTmUNa8eSxD4wr+50LtUkm4q5jv4vgtBKriqshvgqi8BpafZKkZKzYCR
0uKsxe4THS6RL+37UhZoacSAdI/PCmBf6P+4WI2Op/C8jFT3d/I8NrIA9DZdK311
OEnnNfH2pVbfc7a1AtyDwi5A/CjDX7l2+GcCHJfDcBnqKLALzAZrRP5sjTEOKpWE
P6O/wjb4scTOeMz3nHU5Xx1DYSkfgp0t8w/9x+3Ye7q28rCqWER0ov2JvmnvZ60Y
z/rEs2n7SROMefnlFwvoEQjYuSgKd21YowK8RosGTnS3xjpySZFchC16hPEa/yAF
hTklD/sfs4PIJoSSakkF5IjgCG1t9EcwjYChgNazGmsL68q3UIFRNMVvnf35Gp62
NwHjpKBy6X0Hk4s6IZZCwDUq1tCHHoeHUyBms1c+3+5tNUdZbSx56L/qpe95vOyf
2j4ke5VAZvvaHoLKP/y+Efcc3+f2dXg2w1H4b+cFeAutuyNjNNtnzZvsoE8MaqSC
w9p03abDJJ5qvv8k0GIlZ7pqX718lTmm99+SBnhTHxuH5vl+zLhZDf4Up4vdHUwG
kypb3pXuaLGWYsUGs7quSxDeShldU+HzBvUSvSR+yK3GTrum1AKBxRHjKizS7uTZ
278CC1l35c5a168DEELn
=dZ8W
-END PGP SIGNATURE-

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Guitar bend error

[Thomas Morley]

2016-04-25 0:18 GMT+02:00 Federico Bruni :
> On Sun, Apr 24, 2016 at 11:38:31PM +0200, Thomas Morley wrote:
>> 2016-04-24 17:13 GMT+02:00 Stephen MacNeil :
>> >
>> > It was written by Marc Hohl I just adapted it to have no tab since I don't
>> > use tab
>> >
>> >
>> > see
>> >
>> > https://github.com/openlilylib/openlilylib/tree/master/notation-snippets/guitar-string-bending
>> >
>
> For the records, this is the new home:
> https://github.com/openlilylib/snippets/tree/master/ly/tablature
>
> (the file is the same as in the old one, but future updates will be
> pushed to the new location.. unless Urs wants to keep the old
> in sync)
>
>> > Line breaks over bending notes are not supported and they are currently
>> > disabled, because otherwise the file would not compile as soon as page
>> > formatting decisions create such a situation.
>>
>>
>>
>> Manual inserting \noBreak or \break will probably not enough, without
>> \layout { \autoLineBreaksOff }
>>
>> Opposed to what is claimed in the quote from openlilylib above,
>> disabling line-breaks do not work sufficiently.
>
> I can add this to the README on github.

Please do.

But it's more a
TODO:
  - How should this feature behave at line-break?
  - Until this is cleared disable line-breaks sufficiently.

Thanks,
  Harm

>
>> See the out put from:
>> \include "definitions.ily"
>>
>> \displayLilyMusic
>> \relative c'' {
>> \bendOn
>> c1( d)
>> c1( d)
>> }
>>
>> It returns in terminal:
>>
>> { { \override Voice.Slur.stencil = #slur::draw-pointed-slur
>> \override TabVoice.Slur.stencil = #slur::draw-bend-arrow
>> c''1( \noBreak } d''1) c''1( d''1) }
>>
>> The overrides last until the end, but the \noBreak occurs only once!!
>>
>
> True. Better to avoid these (likely) errors and use manual breaks.
> Minimal example reworked in the new openlilylib style:
>
> \version "2.19.40"
> \include "openlilylib"
>
> \useLibrary Tablature
> % Workaround for issue #136 at
> % https://github.com/openlilylib/snippets/issues/136
> #(display "")
> \useModule tablature.bending
>
> % Hack needed until issue #136 is fixed:
> % https://github.com/openlilylib/openlilylib/issues/136
> #(ly:message "loaded")
>
>
> music = \relative c'' {
>   \displayLilyMusic
>   \bendOn
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
>   c1( d)
> }
>
> \new StaffGroup <<
>   \new Voice \music
>   \new TabVoice \music
>>>
> % comment this line and it won't compile
> \layout { \autoLineBreaksOff }

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

ANN: Abjad 2.17

[josiah oberholtzer]

Dear friends,

I'm pleased to announce that Abjad 2.17 is now available.

Abjad is a Python API for Formalized Score Control

Abjad helps composers build up complex pieces of music notation in an
iterative and incremental way. Use Abjad to create symbolic
representations of all the notes, rests, staves, tuplets, beams and
slurs
in any score. Because Abjad extends the Python programming language, you
can use Abjad to make systematic changes to your music as you work. And
because Abjad wraps the powerful LilyPond music notation package, you
can
use Abjad to control the typographic details of the symbols on the page.

- Docs: http://abjad.mbrsi.org/
- GitHub: https://github.com/abjad/abjad
- PyPI: https://pypi.python.org/pypi/Abjad/2.17

Details of the new release appear below.



## Improvements:

- Abjad's documentation has seen extensive work, including:

  - a new theme based off of https://github.com/snide/sphinx_rtd_theme
  - crisp SVG Graphviz output for all class lineage graphs
  - expandable image thumbnails
  - a score gallery page showing notation examples from many scores created
with Abjad: http://abjad.mbrsi.org/gallery.html
  - revised installation instructions
  - virtually all code examples in the docs are now interpreted via the
`abjad-book` Sphinx extension, guaranteeing correctness
  - many enhancements to Abjad's Sphinx extension

- A new `PackageGitCommitToken` class for embedding Python package version
  information in LilyPond files as comments.

- A new `IterationAgent.by_timeline_and_logical_tie()` method.

- A provisional collection of new classes in `lilypondnametools` for
  object-modeling various LilyPond entities: `LilyPondGrob`,
  `LilyPondGrobInterface`, `LilyPondContext` and `LilyPondEngraver`.

- Abjad now supports PyPy, in addition to Python 2.7 and Python 3.3+.

## Changes:

- Abjad's dependencies have been separated into `standard`, `development`
and
  `ipython`. See our installation docs for details.

- Abjad's IPython extension now uses `timidity` instead of `ffmpeg` and
  `fluidsynth` to embed audio output from calls to `play()`. OSX users can
  install `timidity` via HomeBrew.

- `GraphvizEdge.__call__()` has been removed in favor of explicit
  `.attach(node_one, node_two)` and `.detach()` methods.

- `sievetools` functionality has been merged into the classes housed in
  `patterntools`.

- All `labeltools` functionality has been migrated into the
  `agentools.LabelAgent` class.

- `LilyPondFile` properties such as `paper_size`, `includes`, etc. are now
  immutable. Set them during instantiation. See the API example for details:
  http://abjad.mbrsi.org/api/tools/lilypondfiletools/LilyPondFile.html

- `TimeSignature` can now only be instantiated from a pair, such as `(3,
4)`:
  `TimeSignature((3, 4))`.

## Bugfixes:

- `GraphvizGraph` instances can now be copied with edges intact.

- `Markup` now properly quotes strings containing `#` symbols.



For installation instructions, see http://abjad.mbrsi.org/installation.html.

We hope you enjoy!

Trevor Bača
* mail: trevorb...@gmail.com
* home: http://www.trevorbaca.com/

Josiah Wolf Oberholtzer
* mail: josiah.oberholt...@gmail.com
* home: http://josiahwolfoberholtzer.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

[Julien Rioux]

On 24/04/2016 12:12 PM, Phil Holmes wrote:

- Original Message - From: "David Kastrup" 


No disagreement here.  At the very least it would be verification that
the ones responsible for doing the GUB part of the transition are
comfortable with the basic necessities.



I think the only person likely to be able to upgrade GUB to python 2.7 2
would be Masamichi.

--
Phil Holmes


A while back I pushed a branch with python 2.6 based on Jan's upstream, 
but it got stalled [1]. While not the latest, 2.6 does have a lot of 2/3 
compatibility helpers included (from __future__ import ...). I outlined 
an update plan [2] which obviously "felt in the water" as the Germans 
say. Maybe there is something to base future efforts upon.


[1] https://github.com/gperciva/gub/pull/6
[2] https://lists.gnu.org/archive/html/lilypond-devel/2014-03/msg00033.html

--
Julien


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: GUILE error when running lilypond-book

[Julien Rioux]

On 25/04/2016 4:12 PM, David Kastrup wrote:

Matt  writes:


Hi,

when running lilypond-book I get the error:

lilypond_test.lytex:16:44: error: GUILE signaled an error for the
expressionbeginning here
  \once \override BreathingSign.stencil = #
  ly:breathing-sign::divisio-maior
Unbound variable: ly:breathing-sign::divisio-maior


When running the score separately in lilypond I don't get the error. So the
score seems to be ok, but lilypond-book has issues with it.

It looks like that the macro definition divisioMajor makes issue:

divisioMaior = {
  \once \override BreathingSign.stencil = #ly:breathing-sign::divisio-maior
  \once \override BreathingSign.Y-offset = #0
  \breathe
}


I'm running lilypond 2.18.2.

Any hints would be appreciated.


Are you using -dsafe ?  That only enables a subset of C++-defined
commands which is rather spotty (to say the least).



The -dsafe argument is likely the reason. If this is compiled by LyX as 
the provided sample document indicates, then the default configuration 
will use the -dsafe argument. The call to lilypond-book (and lilypond) 
can be configured in LyX' converters config dialog, and the -dsafe 
argument removed.


--
Julien


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: GUILE error when running lilypond-book

[David Kastrup]

David Kastrup  writes:

> Matt  writes:
>>
>> I'm running lilypond 2.18.2.
>>
>> Any hints would be appreciated.
>
> Are you using -dsafe ?  That only enables a subset of C++-defined
> commands which is rather spotty (to say the least).
>
> Other than that, ly:breathing-sign::divisio-maior should have existed
> for eternities, so unless there is some other scoping problem, we'd need
> to get more info than this.

Oh, and misspellings of ly:breathing-sign::divisio-maior could also be
at fault.  The most likely cause would be a hyphen that has been
replaced by a "soft hyphen" or other similar-looking character with a
different character code.  Or a non-breaking space at the end of name.

Stuff like that.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: GUILE error when running lilypond-book

[David Kastrup]

Matt  writes:

> Hi,
>
> when running lilypond-book I get the error:
>
> lilypond_test.lytex:16:44: error: GUILE signaled an error for the
> expressionbeginning here
>   \once \override BreathingSign.stencil = #
>   ly:breathing-sign::divisio-maior
> Unbound variable: ly:breathing-sign::divisio-maior
>
>
> When running the score separately in lilypond I don't get the error. So the
> score seems to be ok, but lilypond-book has issues with it.
>
> It looks like that the macro definition divisioMajor makes issue:
>
> divisioMaior = {   
>   \once \override BreathingSign.stencil = #ly:breathing-sign::divisio-maior
>   \once \override BreathingSign.Y-offset = #0
>   \breathe  
> }
>
>
> I'm running lilypond 2.18.2.
>
> Any hints would be appreciated.

Are you using -dsafe ?  That only enables a subset of C++-defined
commands which is rather spotty (to say the least).

Other than that, ly:breathing-sign::divisio-maior should have existed
for eternities, so unless there is some other scoping problem, we'd need
to get more info that this.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: GUILE error when running lilypond-book

[Matt]

Matt  gmx.net> writes:

> PS: system is claiming that I would top-post. So I'm adding some lines of
> text at the very end. And deleting the quote of lilypond_test.lytex in the
> hope that the message is now accepted.

here is lilypond_test.lytex:

%% LyX 2.1.2 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[english]{scrartcl}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage[a5paper]{geometry}
\geometry{verbose,tmargin=1.5cm,bmargin=1.5cm,lmargin=1cm,rmargin=1.5cm,
footskip=0.5cm}
\usepackage{babel}
\begin{document}

\title{Test}

\begin{lilypond}[staffsize=15]

divisioMaior = {   
  \once \override BreathingSign.stencil = #ly:breathing-sign::divisio-maior
  \once \override BreathingSign.Y-offset = #0
  \breathe  
}

<< \new Staff 
\with { 
  \remove "Bar_engraver" 
  \remove "Time_signature_engraver"
}

{ 
  \relative c'
  {
\hide Staff.Stem
\clef violin
\key f \major
f4 g a g a bes a \divisioMaior
a a a a g a g f \divisioMaior
f g a g \divisioMaior
a bes a a g f \divisioMaior
g f g g f g a g \divisioMaior
f g a g a bes a a g f \divisioMaior
  }
}
\addlyrics { t t }
>>
\end{lilypond}

\end{document}
 





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

GUILE error when running lilypond-book

[Matt]

Hi,

when running lilypond-book I get the error:

lilypond_test.lytex:16:44: error: GUILE signaled an error for the
expressionbeginning here
  \once \override BreathingSign.stencil = #
  ly:breathing-sign::divisio-maior
Unbound variable: ly:breathing-sign::divisio-maior


When running the score separately in lilypond I don't get the error. So the
score seems to be ok, but lilypond-book has issues with it.

It looks like that the macro definition divisioMajor makes issue:

divisioMaior = {   
  \once \override BreathingSign.stencil = #ly:breathing-sign::divisio-maior
  \once \override BreathingSign.Y-offset = #0
  \breathe  
}


I'm running lilypond 2.18.2.

Any hints would be appreciated.


PS: system is claiming that I would top-post. So I'm adding some lines of
text at the very end. And deleting the quote of lilypond_test.lytex in the
hope that the message is now accepted.




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Editing lilypond files with Geany

[amir]

Hello,

i am trying to configure Geany to use it for Lilypond. I have made this File
: ~/.config/geany/filedefs/filetypes.lilypond.conf with this content:

[styling]
comment=0x808080;0xff;false;true


[settings]
# default extension used when saving files
extension=ly

# block comments
comment_open=%{
comment_close=%}
comment_use_indent=false


[build_settings]
# %f will be replaced by the complete filename
# %e will be replaced by the filename without extension
# (use only one of it at one time)
compiler=lilypond "%f"
# it is called linker, but here it is an alternative compiler command
# linker=pdflatex --file-line-error-style "%f"
run_cmd=epdfview "%e.pdf"
run_cmd2=timidity "%e.midi"



which i had copied here from the forum from an answer. I have still no
Syntax colors and can not compile the file with F5. But at the bottom most
part of the window i see : filetype:lilypond.
Can any one help me setting geany up for lilypond?  



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Editing-lilypond-files-with-Geany-tp14233p190024.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/lilypond-user

Re: Google Summer of Code projects 2016

[Michael Rivers]

That is just such wonderful news for everyone. Thank you so much to the
students, mentors and everybody involved in organizing this.

>From a personal standpoint, being able to have slurs and ties cross voices
in all the piano music I engrave would increase my quality of life
significantly. 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Google-Summer-of-Code-projects-2016-tp189997p190020.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/lilypond-user

Re: Fw: new message

[Simon Albrecht]

On 25.04.2016 16:28, Blöchl Bernhard wrote:

Am 25.04.2016 15:45, schrieb MarcM:

Hello!

YOU HAVE A NEW MESSAGE, PLEASE READ
http://seguridadbravo.com/agreement.php [1]

[hidden email] [2]

-
 View this message in context: Fw: new message [3]
 Sent from the User mailing list archive [4] at Nabble.com.


Links:
--
[1] http://seguridadbravo.com/agreement.php?lsu4
[2]
http://webmailer.telecolumbus.net/user/SendEmail.jtp?type=node=190013=0 


[3] http://lilypond.1069038.n5.nabble.com/Fw-new-message-tp190013.html
[4] http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Got this message multiple - SPAM?


I very much hope that you didn’t click the link. Of course it’s spam. 
Can we do anything about it?


Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[N. Andrew Walsh]

Actually, I'm more inclined to agree with you (I *despise*
overly-HTML-formatted email, even though I use gmail, because even with a
good fontconfig setup it looks like garbage). I was, rather, expressing
some enthusiasm that we're a community that has intensive discussions about
stuff like this, without taking any position in the discussion itself.

You want a *real* nerd-fight, though, we can go back to talking about
accidentals for music in just intonation.

Cheers,

A

On Mon, Apr 25, 2016 at 4:47 PM, David Kastrup  wrote:

> "N. Andrew Walsh"  writes:
>
> > Oh man, this is going to be the best nerd-fight ever.
> >
> > *gets popcorn and writes a reply out in non-ISO character encoding*
>
> There is no need to fight.  If there is sufficient support for
> abolishing all mailing list etiquette and common sense, those who are
> not willing to contribute to the discussion under such circumstances
> (which includes me) are free to go elsewhere where conversing about a
> typesetting system driven by plain text in a medium of plain text is not
> frowned upon.
>
> --
> David Kastrup
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[David Kastrup]

"N. Andrew Walsh"  writes:

> Oh man, this is going to be the best nerd-fight ever.
>
> *gets popcorn and writes a reply out in non-ISO character encoding*

There is no need to fight.  If there is sufficient support for
abolishing all mailing list etiquette and common sense, those who are
not willing to contribute to the discussion under such circumstances
(which includes me) are free to go elsewhere where conversing about a
typesetting system driven by plain text in a medium of plain text is not
frowned upon.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[Tim McNamara]

> On Apr 25, 2016, at 8:11 AM, Michael Hendry  wrote:
> 
>> On 25 Apr 2016, at 13:39, Tim McNamara  wrote:
>> 
>> On Apr 25, 2016, at 5:00 AM, Andrew Bernard  wrote:
>> 
>>> Greetings All,
>>> 
>>> In a recent post David Wright asks of  a user:
>>> 
 Please configure your client to post a text equivalent of your HTML code.
>>> 
>>> He also asked me to do that.
>> 
>> The reality is that the world, given the ubiquity of broadband and graphical 
>> interfaces, has moved on from plain text.  It is no longer the standard and 
>> has not been for a decade or more- most Internet users have, I suspect, no 
>> knowledge of this old standard any longer. Expecting others to accommodate 
>> what is now an out of date standard will simply continue to create issues.  
>> It's like expecting web developers to accommodate lynx in creating Web 
>> pages- probably not going to happen very often.  
>> 
>> One can choose to use text-only software but at this point we are 
>> responsible for our own problems if we do.  The world has changed and left 
>> us behind.
> 
> Heavens above!
> 
> You’ll be wanting us to start top-posting next!

LOL!  While top-posting is now normal as well, it really irks me and I can’t 
imagine ever wanting to do it that way.


A:  It’s backwards.

Q:  What’s wrong with top posting?


Tim___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[N. Andrew Walsh]

Oh man, this is going to be the best nerd-fight ever.

*gets popcorn and writes a reply out in non-ISO character encoding*

<3

A

On Mon, Apr 25, 2016 at 3:17 PM, Blöchl Bernhard <
b_120902342...@telecolumbus.net> wrote:

> Nonsense, to stay polite!
>
> Have you ever heard of ASCII? If not, google ...
>
> Am 25.04.2016 14:39, schrieb Tim McNamara:
>
>> On Apr 25, 2016, at 5:00 AM, Andrew Bernard 
>> wrote:
>>  what is now an out of date standard
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fw: new message

[Blöchl Bernhard]

Am 25.04.2016 15:45, schrieb MarcM:

Hello!

YOU HAVE A NEW MESSAGE, PLEASE READ
http://seguridadbravo.com/agreement.php [1]

[hidden email] [2]

-
 View this message in context: Fw: new message [3]
 Sent from the User mailing list archive [4] at Nabble.com.


Links:
--
[1] http://seguridadbravo.com/agreement.php?lsu4
[2]
http://webmailer.telecolumbus.net/user/SendEmail.jtp?type=node=190013=0
[3] http://lilypond.1069038.n5.nabble.com/Fw-new-message-tp190013.html
[4] http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Got this message multiple - SPAM?

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Fw: new message

[MarcM]

Hello!

 

You have a new message, please read 


 

m...@mouries.net





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Fw-new-message-tp190013.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/lilypond-user

Fw: new message

[MarcM]

Hello!

 

You have a new message, please read 


 

m...@mouries.net





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Fw-new-message-tp190011.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/lilypond-user

Re: Replying to posts

[Blöchl Bernhard]

Nonsense, to stay polite!

Have you ever heard of ASCII? If not, google ...

Am 25.04.2016 14:39, schrieb Tim McNamara:

On Apr 25, 2016, at 5:00 AM, Andrew Bernard 
wrote:
 what is now an out of date standard
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[Johan Vromans]

On Mon, 25 Apr 2016 07:39:25 -0500
Tim McNamara  wrote:

> The reality is that the world, given the ubiquity of broadband and
> graphical interfaces, has moved on from plain text.

True. They now need megabytes to deliver a 60-character message with 2
characters (or less) semantic content :) .

But this is a mailing list, and people joining mailing lists are of a
different kind. They know about mail tools and at least can be asked to
confirm to list standards.

For those who want glitter and spam, there's facebook and twitter.

> The world has changed and left us behind.

I can feel your pain, but I do not agree.

-- Johan

Warning: 78-character ASCII aligned signature following...


Johan Vromans   jvrom...@squirrel.nl
Squirrel Consultancy  Exloo, the Netherlands
http://www.squirrel.nl  http://johan.vromans.org
PGP Key 1024D/1298C2B4  http://johan.vromans.org/pgpkey.html
--- "Arms are made for hugging" 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[Michael Hendry]

> On 25 Apr 2016, at 13:39, Tim McNamara  wrote:
> 
> On Apr 25, 2016, at 5:00 AM, Andrew Bernard  wrote:
> 
>> Greetings All,
>> 
>> In a recent post David Wright asks of  a user:
>> 
>> > Please configure your client to post a text equivalent of your HTML code.
>> 
>> He also asked me to do that.
> 
> The reality is that the world, given the ubiquity of broadband and graphical 
> interfaces, has moved on from plain text.  It is no longer the standard and 
> has not been for a decade or more- most Internet users have, I suspect, no 
> knowledge of this old standard any longer.  Expecting others to accommodate 
> what is now an out of date standard will simply continue to create issues.  
> It's like expecting web developers to accommodate lynx in creating Web pages- 
> probably not going to happen very often.  
> 
> One can choose to use text-only software but at this point we are responsible 
> for our own problems if we do.  The world has changed and left us behind.

Heavens above!

You’ll be wanting us to start top-posting next!

Michael


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Guitar bend error

[Stephen MacNeil]

>I’ll see if I can get the openlilylib files to work first.

they should be the same file, unless the openlilylib has been updated. I
never modified the file I think

>how come the graceBend slurs are always facing down in the output when it
says “up” in the definitions file?

do you mean pointing down? probalbly to show it goes from a higher note to
a lower. Not sure I don't use tab so i could be wrong. are you referring to

\once \override Voice.Slur.direction = #UP

that puts the slur/bend mark above

>I need bend slurs without the TabStaff. Thanks for that, Stephen!

no problem, since i don't use tab i figured others could use it as well.
glad it's useful.

HTH
Stephen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[Tim McNamara]

On Apr 25, 2016, at 5:00 AM, Andrew Bernard  wrote:
> 
> Greetings All,
> 
> In a recent post David Wright asks of  a user:
> 
> > Please configure your client to post a text equivalent of your HTML code.
> 
> He also asked me to do that.

The reality is that the world, given the ubiquity of broadband and graphical 
interfaces, has moved on from plain text.  It is no longer the standard and has 
not been for a decade or more- most Internet users have, I suspect, no 
knowledge of this old standard any longer.  Expecting others to accommodate 
what is now an out of date standard will simply continue to create issues.  
It's like expecting web developers to accommodate lynx in creating Web pages- 
probably not going to happen very often.  

One can choose to use text-only software but at this point we are responsible 
for our own problems if we do.  The world has changed and left us behind.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Replying to posts

[Urs Liska]

Am 25.04.2016 um 12:00 schrieb Andrew Bernard:
> Greetings All,
>
> In a recent post David Wright asks of  a user:
>
> > Please configure your client to post a text equivalent of your HTML
> code.
>
> He also asked me to do that.
>
> Daivd is using a text based email client. I was unaware until he
> mentioned it that people using such clients cannot always get a proper
> view of HTML posts, as they sometimes lack plain text parts, or with
> Outlook in my case, it does not put internet style quotes in the plain
> text part where the HTML email has vertical bars. This makes it hard
> for text email client users to see what has been quoted and is not ideal.
>
> The list is plain text only. So if you use a mailer like Outlook and
> your default is to send HTML format mail, you need to configure
> Outlook to reply to email in the format in which it was sent, that is,
> here, plain text. Then list users will get properly formatted plain
> text replies with internet style ‘>’ quoting. I am pretty sure Outlook
> used to do this by default, but now it does not, and needs to be set
> up to do so.

Is it possible to configure Outlook to send messages in specific formats
to specific addresses? In Thunder bird you can save the "preferred
message format" together with contacts.

>
> I am certain that most Outlook users are oblivious to this. David is
> going to be sending such requests continually.
>
> Therefore, I wonder is there is anywhere we can put guidelines for
> posting to the list?
>
> Similarly, it would be good to educate people not to reply to the
> digest as a subject line, but to the thread in question. This is
> another thing that comes up frequently. Another point to add to list
> guidelines.
>
> Can this advice go somewhere here perhaps?
>
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>

Well, if it can go there, I'm sure those who need it won't read it ...

Urs

> Andrew
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Replying to posts

[Andrew Bernard]

Greetings All,

In a recent post David Wright asks of  a user:

> Please configure your client to post a text equivalent of your HTML code.

He also asked me to do that.

Daivd is using a text based email client. I was unaware until he mentioned it 
that people using such clients cannot always get a proper view of HTML posts, 
as they sometimes lack plain text parts, or with Outlook in my case, it does 
not put internet style quotes in the plain text part where the HTML email has 
vertical bars. This makes it hard for text email client users to see what has 
been quoted and is not ideal.

The list is plain text only. So if you use a mailer like Outlook and your 
default is to send HTML format mail, you need to configure Outlook to reply to 
email in the format in which it was sent, that is, here, plain text. Then list 
users will get properly formatted plain text replies with internet style ‘>’ 
quoting. I am pretty sure Outlook used to do this by default, but now it does 
not, and needs to be set up to do so.

I am certain that most Outlook users are oblivious to this. David is going to 
be sending such requests continually.

Therefore, I wonder is there is anywhere we can put guidelines for posting to 
the list?

Similarly, it would be good to educate people not to reply to the digest as a 
subject line, but to the thread in question. This is another thing that comes 
up frequently. Another point to add to list guidelines.

Can this advice go somewhere here perhaps?

https://lists.gnu.org/mailman/listinfo/lilypond-user


Andrew


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Fw: new message

[MarcM]

Hello!

 

You have a new message, please read 

 

m...@mouries.net





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Fw-new-message-tp18.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/lilypond-user

Re: Weird key sig accumulation

[Simon Albrecht]

On 25.04.2016 01:05, Thomas Morley wrote:

2016-04-25 0:48 GMT+02:00 David Kastrup :

Simon Albrecht  writes:


Hello everybody,

I’ve built some music functions to handle a large, multi-section
piece, and ran into a strange problem, which I could boil down to the
attached example.
If the concat-part function is called on the \key expression multiple
times in parallel, the \key expressions are accumulated in a way I’ve
never seen before. Why would that be?

Because you are not copying the expression and still using it multiple
times.  A big no-no.  Consequently, \transpose works multiple times on
the identical expression.

If you use stuff multiple times, _copy_ it.  Because LilyPond will
generally _change_ expressions it is working on.

Multiple \transpose, multiple \relative, multiple other stuff: all that
you want to avoid occuring on the identical expression several times.


\version "2.19.39"

global.1 = { \key c \major }

concat-part =
#(define-music-function (al) (list?)
(make-sequential-music (map cdr al)))
buildPart =
#(define-music-function () ()
#{
  \new Voice <<
\concat-part \global
{ c'1 }
  >>
#})

\transpose c d <<
   \buildPart
   \buildPart

--
David Kastrup



David was faster...
Same problem as sometimes with #/$-signs.


Thanks to both of you. I’ll continue to learn…

Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Google Summer of Code projects 2016

[Urs Liska]

Hi all,

I'm happy to be able to announce that LilyPond will have two students
working for us as part of the Google Summer of Code program 2016. We had
a busy time and quite some organization to do but now it's ready, and
it's good that we did arrive at having two slots, two students and two
mentors.

Nathan Chou will work on removing a longstanding and annoying limitation
in LilyPond's input capabilities: the fact that spanners are restricted
to start and end in the same voice. While it may have been considered as
semantically straightforward that a crescendo is tied to a dedicated
voice this doesn't reflect the musical reality for many polyphonic
instruments. While a piano *may* feature strict polyphonic setting it
doesn't *have* to, therefore we often see dynamics, slurs/ties, text
spanners and many more ending in different voices.
The workaround that is necessary so far involves adding a hidden voice
just for the spanners, and this workaround is equally tedious/error
prone as semantically wrong. So successfully removing this limitation
will be a significant improvement for a signficant part of the
repertoire engraved with LilyPond. And while it hasn't fully been
considered yet it can be expected that this improvement will have
significant impact on working with partcombined voices as well.
This project is mentored by Jan-Peter Voigt.

Jeffery Shivers will bring the ScholarLY package to production state.
ScholarLY is a package within openLilyLib that enables inserting
annotations in the LilyPond input, which can then be exported to, say,
LaTeX input files to be typeset as critical reports. The annotations
have also proven extremely useful for documenting editorial issues and
communicating them between (human) editors.
The goals are a) to significantly extend the interface for entering
annotations and enable (to name just the most important) inserting music
examples in annotations, trigger the creation of footnotes and have an
annotation cause visual indications in the resulting score (e.g.:
editorial addition => dashed slur/parenthesized articulation etc.). b)
creating these editorial commands that can be triggered by annotations
(or used directly) and c) the creation and publication of a robust LaTeX
package for typesetting reports from data provided from within LilyPond
scores.
This project will be mentored by me.

We welcome the two students and wish them successful and fruitful
projects. They are encouraged to actively reach out to the community,
and so the community is encouraged to welcome them heartily and provide
any support they might need.

Best wishes
Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user