Bertalan Fodor writes:
> I've set it to myedit.bat
> It starts, but doesn't get the parameters.
If you want parameters, you'll have to specify them all in LYEDITOR.
The current algorithm just finds the name of the editor, and if it is
recognised (emacs, jedit, lilypad, ...) it [re]constructs the
Works for me.
Bert
test.ly
=
\version "2.5.31"
\paper {
% change for other default global staff size.
myStaffSize = #20
#(define fonts
(make-pango-font-tree "Times New Roman" "Arial" "Courier New" (/
myStaffSize 20)))
}
melody = \relative c' {
\clef treble
\key c \major
\ti
Yep, the fc-cache (run as root) solved the problem.
Thanks.
George
On Jun 16, 2005, at 4:25 PM, Han-Wen Nienhuys wrote:
George Riley wrote:
Output below.
The long wait is after the line that says: "Initializing
FontConfig..."
The short print commands you don't recognize were added by
me in t
Output below.
The long wait is after the line that says: "Initializing FontConfig..."
The short print commands you don't recognize were added by
me in the python file to try to find what was taking so long.
Not sure, but the problem might be the "/Users/hanwen..." in
some of the environment vars.
Basil Crow wrote:
The following file compiles fine on LilyPond 2.5.31 Linux, but hangs in
Windows on "Converting to `test.pdf'..."
Can you give more details? Where does it hang? try running with
--verbose.--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
_
The following file compiles fine on LilyPond 2.5.31 Linux, but hangs in
Windows on "Converting to `test.pdf'..."
test.ly
=
\version "2.5.31"
\paper {
% change for other default global staff size.
myStaffSize = #20
#(define fonts
(make-pango-font-tree "Times New Roman" "Arial" "Cour
George Riley wrote:
Yep, the fc-cache (run as root) solved the problem.
(it didn't work when run as normal user?)
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists
BAT files are deprecated. Try setting LYEDITOR in your global
environment settings.
I've set it to myedit.bat
It starts, but doesn't get the parameters.
Bert
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listin
Jan Nieuwenhuizen writes:
>> As a result the lilypad editor was started when I used point and
>> click in the pdf-file (the TTF problem seems solved). The cursor
>> didn't jump to the right position.
> Thanks for reporting this, I'll have a look.
Point and click with lilypad works for me, you'll
George Riley wrote:
Output below.
The long wait is after the line that says: "Initializing FontConfig..."
The short print commands you don't recognize were added by
me in the python file to try to find what was taking so long.
Not sure, but the problem might be the "/Users/hanwen..." in
some of t
George Riley wrote:
To follow up on prior, the command line DOES in fact run properly (I
was just
impatient earlier). HOwever, it takes nearly a minute to do anything!
THen
the correct echo's show up and the pdf file created. See below:
Further the GUI also works properly with Compile > Typ
To follow up on prior, the command line DOES in fact run properly (I
was just
impatient earlier). HOwever, it takes nearly a minute to do anything!
THen
the correct echo's show up and the pdf file created. See below:
Further the GUI also works properly with Compile > Typeset File,
but it als
Hi Guys,
I successfully installed the .dmg file. But following the instructions
that say:
2. Select
Compile > Run LilyPond
from the menu.
I find I don't have a "Compile > Run Lilypond" option. I just have:
Compile > Update Syntax
Compile > Typeset File (%R)
Typeset seems to
Peter Leschev writes:
> is there a particular reason why running lilypond
> from the cmd prompt doesn't print any output
> anymore?
Yes, although it could be changed if enough people complain. You only get
console output if you have a console. Ap
Katrien de Vos writes:
> I tested the latest version 2.5.31-1 for windows. I noticed that in
> the map usr\bin lilypond-invoke-editor.bat was missing. So I could not
> change the settings for my favourite editor.
BAT files are deprecated. Try setting LYEDITOR in your global
environment settings.
Hi,
is there a particular reason why running lilypond from the cmd
prompt doesn't print any output anymore? Granted that the output is now
directed to FILENAME.log - Things like lilypond --version don't work anymore...
Or am I missing something obvious?
Also, lilypo
I tested the latest version 2.5.31-1 for windows. I noticed that in the
map usr\bin lilypond-invoke-editor.bat was missing. So I could not
change the settings for my favourite editor. As a result the lilypad
editor was started when I used point and click in the pdf-file (the TTF
problem seems s
Lilypond 2.5.31 compiled on Mandriva 2005
Lilypond makes ps, pdf and tex files ( $ lilypond -b tex -f tex xxx.ly)
But I can't applies LaTeX on my tex file !
$ latex xxx.tex
Error message :
---
LaTeX Info: Redefining \dots on input line 37.
(/mondelibre/Olivier/Master1/lyxx
I think I've found a workaround: putting the Bar_engraver into ChordNames
Bert
Mats Bengtsson wrote:
> Known bug, see volta-bracket-chords-align.ly at
> http://lilypond.org/bugs/v2.5/
>
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://
I think this bug has already been mentioned a few times but I haven't
noticed any reaction and it's not in the bug database.
Setting style to line should give a solid line, right? It doesn't!
Example:
\version "2.5.31"
\score{
\relative c'{
\override TextSpanner #'edge-text = #'("3 " . "")
\ov
Known bug, see volta-bracket-chords-align.ly at
http://lilypond.org/bugs/v2.5/
/Mats
Bertalan Fodor wrote:
%BUG: Volta Bracket in a ChordNames context begins at wrong place.
\version "2.5.31"
staffOne = \new Staff {
\set Staff.voltaOnThisStaff = ##t
\relative c' {
%BUG: Volta Bracket in a ChordNames context begins at wrong place.
\version "2.5.31"
staffOne = \new Staff {
\set Staff.voltaOnThisStaff = ##t
\relative c' {
\repeat "volta" 2 {
c4 c c c
}
\alternative {
{ d4 d d d }
Ah, it works now in 2.5.31. Thanks!
On Tue, 14 Jun 2005 20:26:12 +0200, Han-Wen Nienhuys <[EMAIL PROTECTED]>
wrote:
VSD wrote:
Thanks for the answer. Indeed \mychords are within a \score block. The
exact input file is:
%%
ChordOffset = #(def-music-function (parser location offs
Clearly a serious bug!
To make this bug report complete, I include a small but complete
example of this bug:
\version "2.5.31"
\score {
\context ChoirStaff <<
\new Voice {c d e f}
\new Voice {c d e f}
>>
}
The easiest workaround for you is to explicitly specify where you
want to have new sta
Imruska wrote:
I believe, however, that the fact Lilypond 2.5.30 creates a
DrumStaff where it is explicitly told to create a ChoirStaff is a bug.
indeed. Can you send a bugreport for this.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
_
Will Oram wrote:
Whoops, didn't realise Console was logging events until lilypond told
me so as I tried to quit. From the Console log:
what version is this (see About LilyPond)
"/Users/spamguy/Desktop/Downloads/LilyPond.app/Contents/Resources/
Python/LilyPond.py", line 125, in createProcessL
It would be helpful if you'd post the contents of your \score block.
\score {
\context ChoirStaff <<
\context Voice = discantusNotes << \global \discantusNotes >>
\context Lyrics = discantusLyrics \lyricsto discantusNotes
{ discantusLyrics }
\context Voice = altusNotes << \global \
27 matches
Mail list logo
