I'm somewhat split in this question:
I very much like stackexchange and use it as a resource for latex, git and
python questions regularly.
Finding answers to Lilypond questions there would be nice too.
But I think the user base of Lilypond is significantly smaller than of the
other mentiones
If you're not confortable with the Terminal and use Texworks, you have to
tell to Texworks with command to run: lilypond-book in place of pdflatex (or
pdfxelatex etc. according to your usual LaTeX choice).
In Texworks, go to the Preferences, in the Typesetting tab.
In Path for Tex..., add the
I am also totally up for this idea as well.
What's wrong with this list? Everybody wants to take his LilyPond
business to the web interface of his choice that takes a lot of
additional work over just reading and typing text and further
dilutes the LilyPond knowledge.
I second that. We
I agree with Urs that a Stack Exchange page shouldn't be instead of this
list, if that was the suggestion.
But as Gilberto pointed out there is already LilyPond questions asked on
different Stack Exchange forums (I answered one myself earlier this
week). And it seems to be some confusion
Allow me to clarify that in no way did I intend for the Stack Exchange page
to replace this list. It would have been purely an addition of resources.
For me, the purpose of the Stack Exchange page is about accessibility to
those who are 1) not familiar with LilyPond or 2) not familiar with
Peter Bjuhr peterbj...@gmail.com writes:
I agree with Urs that a Stack Exchange page shouldn't be instead of
this list, if that was the suggestion.
But as Gilberto pointed out there is already LilyPond questions asked
on different Stack Exchange forums (I answered one myself earlier this
Allow me to clarify that in no way did I intend for the Stack
Exchange page to replace this list. It would have been purely an
addition of resources.
Well, you might answer all lilypond questions by simply pointing
questioners to the list :)
For me, the purpose of the Stack Exchange page
ryanmichaelmcclure ryanmichaelmccl...@gmail.com writes:
Allow me to clarify that in no way did I intend for the Stack Exchange
page to replace this list. It would have been purely an addition of
resources.
For me, the purpose of the Stack Exchange page is about accessibility
to those who
On 11/02/2013 08:28 AM, David Kastrup wrote:
Well, they are on-topic in this mailing list.
If it's community policy or at least a general agreement that we should
always refer to this list, I will of course do so the next time!
But I hope we agree that it, as Ryan wrote, would be helpful
If it's community policy or at least a general agreement that we
should always refer to this list, I will of course do so the next
time!
Yes, please do so.
But I hope we agree that it, as Ryan wrote, would be helpful for the
community if we found ways to deal with questions posted outside
On 11/02/2013 10:28 AM, Werner LEMBERG wrote:
If it's community policy or at least a general agreement that we
should always refer to this list, I will of course do so the next
time!
Yes, please do so.
No problem! Then I suppose I should also post that answer to the meta
question I linked
Werner LEMBERG w...@gnu.org writes:
If it's community policy or at least a general agreement that we
should always refer to this list, I will of course do so the next
time!
Yes, please do so.
But I hope we agree that it, as Ryan wrote, would be helpful for the
community if we found ways
Then I suppose I should also post that answer to the meta question I
linked to previously!?
I think this would be good, yes.
So, is this the link to give?
https://lists.gnu.org/mailman/listinfo/lilypond-user
It depends. For casual users, the gmane interface is perhaps better
suited, thus
On 11/02/2013 11:16 AM, Werner LEMBERG wrote:
It depends. For casual users, the gmane interface is perhaps better
suited, thus the link should rather be
http://news.gmane.org/gmane.comp.gnu.lilypond.general
Maybe it is even better to send them directly to the posting!?
Peter Bjuhr peterbj...@gmail.com writes:
On 11/02/2013 11:16 AM, Werner LEMBERG wrote:
It depends. For casual users, the gmane interface is perhaps better
suited, thus the link should rather be
http://news.gmane.org/gmane.comp.gnu.lilypond.general
Maybe it is even better to send them
Maybe it is even better to send them directly to the posting!?
http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general
Probably. I don't use gmane at all, so I can't give a
recommendation. However, as with StackExchange, people should
*search* first before post something whether
Hi,
my 3 eurocents:
1) StackExchange is great. It's QA style of sharing knowledge is
very efficient and pleasure to work with.
2) LilyPond is too small to have its own StackExcange site. If you look at
http://discuss.area51.stackexchange.com/questions/10733/leaving-beta-requirements
you'll
Jan Nieuwenhuizen jann...@gnu.org writes:
David Kastrup writes:
No, the PostScript is still fine. But when you ask Ghostscript to
convert it to anything else, it has its own idea what to convert.
Nice. How did you come by this one?
Accidentally. The weird thing is that I then tried
Janek Warchoł janek.lilyp...@gmail.com writes:
when all you have is a hammer, every problem starts looking like a
nail. Mailing lists are an all-purpose communication tool. Many
things can be done using a mailing list, but some things may be done
more efficiently using other tools - for
Hmm, after reading all arguments against a Stack Exchange page, I have to
say I completely changed my opinion on this regards as well. Indeed it would
not be good for us to spread a small community in two places, and re-posting
questions on both would be a waste of time indeed. My first reaction
On 2013-11-02 05:52, David Kastrup wrote:
Gilberto Agostinho gilbertohasn...@gmail.com writes:
I am also totally up for this idea as well.
What's wrong with this list? Everybody wants to take his LilyPond
business to the web interface of his choice that takes a lot of
additional work
I think there is one thing the mailing list can't really offer compared to a
QA site: accepted answers. This is really a good thing. But definitely no
reason to spread our forceds and competence.
Ther already _are_ places to present solutions, although not as answersx to
posted questions: the
2013/11/2 David Kastrup d...@gnu.org:
Jan Nieuwenhuizen jann...@gnu.org writes:
David Kastrup writes:
No, the PostScript is still fine. But when you ask Ghostscript to
convert it to anything else, it has its own idea what to convert.
Nice. How did you come by this one?
Accidentally.
Hilary Snaden h...@newearth.demon.co.uk writes:
On 2013-11-02 05:52, David Kastrup wrote:
Gilberto Agostinho gilbertohasn...@gmail.com writes:
I am also totally up for this idea as well.
What's wrong with this list? Everybody wants to take his LilyPond
business to the web interface of
Francisco Vila paconet@gmail.com writes:
Or zeroline.ly , not true ordinary word but a likely filename.
Some filenames make gs crash; expect bug reports on this sooner or later.
A pity tiger.ly does not work
I was actually looking for the tiger, but it seems that it is no longer
being
Am 01.11.2013 19:13, schrieb David Kastrup:
I seem to remember that Windows does something weird with = on the
command line.
I know for sure that the equal sign is nothing special for Windows. The
command line is passed to the process as we give it at the command line.
The Scheme
janek.lilypond wrote
QA sites like StackExchange are better for sharing QA knowledge than
mailing lists because they allow to edit information, update it,
remove duplicates, and make order.
I think this is a good point. The mailing list is sufficient and fine, but
it's probably not optimal
Paul Morris p...@paulwmorris.com writes:
janek.lilypond wrote
QA sites like StackExchange are better for sharing QA knowledge than
mailing lists because they allow to edit information, update it,
remove duplicates, and make order.
I think this is a good point. The mailing list is
David Kastrup wrote
Uh, we do have a manual that can be edited, improved, and evolve over time
with different versions of LilyPond...
Right, but formal documentation is not the same as more informal
QA/support, and they have different levels of editing
accessibility/difficulty and quality
Hello all,
Today, while searching for scores at Mutopia, I came across this one
produced in LilyPond 2.9.9:
http://www.mutopiaproject.org/ftp/BachJS/BWV849/bwv849b/bwv849b-a4.pdf
http://www.mutopiaproject.org/ftp/BachJS/BWV849/bwv849b/bwv849b.ly
What intrigued me here is the position of the bar
I'm finishing up a score and I am encountering this problem in many places:
http://lilypond.1069038.n5.nabble.com/file/n153278/Urban.Allegory.png
What would be my best option for making this look better? Could I make the
barline at that section be transparent so that only the text is visible?
Am 02.11.2013 23:39, schrieb ryanmichaelmcclure:
I'm finishing up a score and I am encountering this problem in many places:
http://lilypond.1069038.n5.nabble.com/file/n153278/Urban.Allegory.png
What would be my best option for making this look better? Could I make the
barline at that section
Try this code: whiteout.ly
http://lilypond.1069038.n5.nabble.com/file/n153280/whiteout.ly
which produces:
http://lilypond.1069038.n5.nabble.com/file/n153280/whiteout.png
Another possibility, which I think would look better, would be to have the
sub. F text anchored to the right of the
You can also try this: left-align.ly
http://lilypond.1069038.n5.nabble.com/file/n153281/left-align.ly
Which produces:
http://lilypond.1069038.n5.nabble.com/file/n153281/left-align.png
This looks much better IMO.
Best,
Gilberto
--
View this message in context:
Gilberto, your last option looks great! I do have a quick question--for
subito dynamics, what should be aligned to the first note of said dynamic:
the actual dynamic or subito?
-
Ryan McClure
Luna Music Engraving
--
View this message in context:
As far as I know, the dynamic text should always start at the note which it
affects. This is the simplest and most elegant solution, and then there is
never ambiguity as to when a dynamic change has to be performed.
--
View this message in context:
In my scores, I prefer to put the *subito */after /the dynamic, for example:
f subito, or p subito. I see that all the time on scores, I figured it was
the norm nowadays or something. I don't often see the subito first in modern
scores, but ymmv.
Just my take on things :)
-
composer |
Another plus to this approach is that the dynamic text is always directly
lined up at the note which it affects, so win win!
-
composer | sound designer
LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond
--
View this message in context:
You are totally right on this one, using subito as a suffix instead of a
prefix is indeed very common. Also, according to the Wikipedia:
Sudden changes in dynamics may be notated by adding the word subito
(Italian for suddenly) as a prefix or suffix to the new dynamic notation.
from:
On Sat, Nov 2, 2013 at 5:32 PM, ryanmichaelmcclure
ryanmichaelmccl...@gmail.com wrote:
Gilberto, your last option looks great! I do have a quick question--for
subito dynamics, what should be aligned to the first note of said dynamic:
the actual dynamic or subito?
According to Gould the dynamic
On 10/8/2013 12:07 AM, Keith OHara wrote:
Peter Gentry peter.gentry at sunscales.co.uk writes:
The problem vanishes if the \tempo specification changed to 179
or slower.
I can imagine a problem if you are sending the MIDI down an actual
MIDI cable. Grace notes are played at 1/4 noted
41 matches
Mail list logo
