Re: Thick barline connections between staves
Thanks for the quick fix--the barline thickness is now consistent. However, now all the barlines look too thick--it's quite noticeable when comparing with professional printed scores as well as previous versions of Lily. I also sent an email to bug-lilypond. --Ed On May 29, 2005, at 6:03 AM, Han-Wen Nienhuys wrote: Thomas Scharkowski wrote: hi ed, han-wen, i mentioned this today as well, and have seen it since approx. 2.5.18 or so. stan sanderson also mentioned it in an email from 12.04.2005 with the subject "2.5.18 bar line thickness error(?)" what stan and i have in common is macos 10.3.x. ed: are you also on a mac? is this maybe a mac-specific problem or is it also on other platforms? for me, the image in the pdf viewer is thicker, but the printout is fine. -sean I also saw the thicker lines on screen, (Acroread 7 on Windows), printout is o.k. Lilypond 2.5.25 on Windows XP. fixed in cvs. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
[ANN] LilyPad Preview 1
Fellow LilyPutians,
As promised a long, long time ago, I'm releasing a preview version of
LilyPad, a simple editor/previewer for LilyPond. It's still a rough
work in progress--what you see represents a very small amount of work
spread over a long period of time--but it's pretty usable in its
current form for editing and previewing simple single-file LilyPond
projects.
Features include:
- A simple code editor with indent preservation
- "Almost live" previewing as you type
- Previews of typeset music (PDF) and audio (MIDI)
- "Point-and-click" links between typeset music and the source code,
all within the same application
To get it, go here:
http://edbaskerville.com/software/lilypad/
Right now, it requires Mac OS X version 10.4 ("Tiger"), and requires
that LilyPond 2.6 for Mac OS X be installed in your /Applications
directory. Documentation is nonexistent, but it should be pretty
straightforward--if you have any questions about how to use it, just
ask me, on or off the list.
Since I wrote the initial code, LilyPond itself has acquired some of
the features LilyPad was supposed to bring: a Mac OS X graphical
interface for LilyPond, point-and-click in PDFs on Mac OS X, etc.
LilyPad takes a slightly different approach, with background
previewing, etc., but the goals are one and the same. As such, I'd
like to work with the LilyPond development team to bring this code
into LilyPond itself, hopefully in time for the 2.8 release. So you
can think of LilyPad not so much as a thing unto itself, but more as
the direction I'd like to see LilyPond take on the Mac OS X platform.
(I will follow this message with one to the development list with
more detailed questions and suggestions.)
Please send me any feedback on this work, again, here or off-list.
I'm aware of many limitations (most notably, that things probably
won't work right for multi-file projects), but I'm sure there are
others I haven't thought of, as well as bugs.
Happy LilyPonding,
Ed
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [ANN] LilyPad Preview 1
On Jul 23, 2005, at 9:38 PM, Will Oram wrote: Sounds great! Wish I could try it out, but I don't have Tiger handy. Out of curiosity, what code/technology makes it Tiger-reliant? I'm using the PDFKit framework, new to Tiger--basically a Preview.app you can embed into your own application--to display the PDFs. I had it working at one point on Panther using a more primitive PDF displaying system--however, without point-and-click functionality, so much less useful--but I broke this and haven't figured out how to fix it again. I have one report of LilyPad crashing on launch--anybody else seeing this? I'll take a look tomorrow; it's probably something stupid. --Ed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
LilyPad fixed
For those of you that tried LilyPad, only to have it fail to launch, I've uploaded a new version that should work: http://edbaskerville.com/software/lilypad/LilyPad.zip --Ed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
[ANN] LilyPad Preview 2
Hi everyone, I've updated LilyPad with some small but important changes to make it more useful. The changes in this version: - Supports command-line (e.g., Fink) installations of LilyPond as well as the application-packaged version - Shows LilyPond output in the preview window - Displays line and character numbers, and lets you jump to a particular line/character - Increase/decrease indent commands (NOTE: these currently break undo, for as of yet unknown reasons. They also only support tab indents, not spaces.) As always, feedback is appreciated. --Ed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
LilyPad link
An important footnote: you can get LilyPad at http://edbaskerville.com/software/lilypad/ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
VersionTracker issues
Hi all, I'm maintaining a listing for Mac LilyPond on VersionTracker. The idea was to only list stable versions on that site, but somebody keeps on submitting development (2.7.x) versions. If whoever is making these submissions is on the list, could you please stop? I've been unsuccessful at getting the VersionTracker people to remember not to accept the submissions. Thanks, Ed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \tempo not working
I just responded on bug-lilypond with a link to previous documentation of the problem: http://lists.gnu.org/archive/html/bug-lilypond/2004-02/msg00346.html For now, you can use Mighty MIDI for playback, available on versiontracker.com. --Ed On Feb 7, 2006, at 5:41 PM, Marius Amado Alves wrote: On 8 Feb 2006, at 00:23, [EMAIL PROTECTED] wrote: I had the same problem. same system configuration. Am 07.02.2006 um 15:07 schrieb Marius Amado Alves: \tempo does not seem to be working here (Mac OS X 10.3, LilyPond 2.6.5, QuickTime Player 7.0.4) It does not have an effect on the MIDI output. I've posted a bug report. In the meanwhile what can we do? Use an older version? Which one? Thanks a lot. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \tempo not working
How much? Besides myself, I bet there are a number of people that would like this, and I'd certainly be willing to chip in. I also notice you have a general MIDI rewrite on the sponsor-worthy feature page...any ballpark on how much the full monty would cost? --Ed On Feb 8, 2006, at 4:27 AM, Han-Wen Nienhuys wrote: Ed Baskerville wrote: I just responded on bug-lilypond with a link to previous documentation of the problem: http://lists.gnu.org/archive/html/bug-lilypond/2004-02/msg00346.html For now, you can use Mighty MIDI for playback, available on versiontracker.com. Hi, I understand the problem, but fixing it requires me to delve into the eon-old MIDI code. This is likely to take a lot of time, and for testing and general cleanup, so I can only do this a sponsored bugfix. Regards, -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \tempo not working
Put me down for 20 EUR to help fix the tempo bug. Any other takers? On Feb 9, 2006, at 2:14 AM, Han-Wen Nienhuys wrote: Ed Baskerville wrote: How much? Besides myself, I bet there are a number of people that would I think 100 EUR is a reasonable amount, given the effort it will require. like this, and I'd certainly be willing to chip in. I also notice you have a general MIDI rewrite on the sponsor- worthy feature page...any ballpark on how much the full monty would cost? I've detailed the first steps, for a total of 1330 eur. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Change pdf viewer on mac
you could try my little lilypad app: http://edbaskerville.com/software/lilypad/ a vastly improved version should be out within the month with completion, syntax coloring, and hopefully some other nice features. i am also planning on releasing it under the gpl. --ed On Apr 2, 2006, at 1:38 PM, mark oilcan wrote: --- Carrick Patterson <[EMAIL PROTECTED]> wrote: Quoting mark oilcan <[EMAIL PROTECTED]>: --- Orm Finnendahl <[EMAIL PROTECTED]> wrote: A couple of days ago I posted a modified lilypond-mode.el which takes advantage of xpdf's -remote option which does what you're asking for. It only works if you use emacs, though... Thanks for the suggestion. Right now I can get a pdf viewer pointing to the final pdf, and it refreshes automatically. The problem on the Mac is that when I do command-R it compiles then pops Preview to the front. If I could make it just do the compiling, without launching Preview (or shifting focus to it) then that would be sufficient. I took a look at lilycall.py in /Applications/LilyPond.app/Contents/Resources but the changes I made there didn't seem to have an effect. I don't really know python, so I'm not sure if that's a limitation of mine or whether lilycall.py is used at all. So, is there a way to customize the behavior of Lilypond to just do the compiling without launching a pdf viewer? I don't have any problem with altering scripts, if that's necessary, but I'll need some pointers on which ones. Mark A Why don't you just put at the top of your file: \set Score.skipTypesetting = ##t There seems some confusion. It's not that I want to stop the typesetting, I just don't want the Mac Lilypond.app application to launch Preview.app (and in particular shift the focus away from Lilypond) after typesetting has been completed. So, I (1) do some editing in a .ly file, (2) hit command- R to typeset and create a pdf file, (3) do more editing. After I do step (2) and perhaps simultaneous to doing step (3) the pdf is displayed in my pdf viewer so I can see what it all looks like. Important here is that between (2) and (3) I don't have to manually switch back to Lilypond from the pdf viewer (ie Preview). Yes, I could do this all easily enough in emacs, but I'm trying to set this up for someone who would find that route far to complicated. The Mac Lilypond.app is great for someone who doesn't want a complicated set-up, but the pushing Preview to the front all the time is actually an annoyance. Thanks for the suggestions. I do appreciate others trying to help out. Is this something that would be better asked on the devel list? Mark A __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
LilyPad update
Hi all, A number of you have inquired recently about LilyPad, my Mac OS X LilyPond front-end, so I thought I'd notify the list that no, it's not dead yet. I've recently restarted development, albeit slowly. (Slow progress is infinitely better than no progress.) The code is now publicly available and licensed under the GPL. The code, a development blog, and a bug-tracking system are all online here: http://code.edbaskerville.com/ I wouldn't recommend using the current code, but a new release will be out soon--that is, when it's ready. :) --Ed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: who uses lilypond
I'm fairly new to LilyPond, and brand-new to this list. I'm a recent college graduate, programmer and cellist living in San Francisco, looking to somehow make myself financially solvent through some combination of Mac programming, freelance technical writing, and cello playing. So far: a few simple arrangements to play at my cousin's wedding. Just begun: a by-ear transcription of the Astor Piazzolla album The Rough Dancer and the Cyclical Night, and subsequent arrangement for whatever combination of friends I can get together to play the thing. (If anybody knows where the sheet music might exist, I'm very eager to turn this into simply an arranging project. Anybody?) Also: I might as well mention that I'm starting to the groundwork for a Mac OS X front end to LilyPond, which will probably bring me back here often over the next few months. I'm actually envisioning two programs: one that's just a previewer (a la TeXShop), and one that has graphical editing, MIDI input, etc. The first I'll probably GPL and ask for donations; the second I'll probably charge for. And I might as well conduct my own informal survey on LilyPond apps for Mac OS X: (1) who would use a simple LilyPond previewer (little more than easy switching between syntax-colored code and PDF output); and (2) who is interested in a fairly simple graphical music editing program that uses LilyPond for final output? --Ed Baskerville ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: font problem lilypond2.3.12 macOSX
BTW, you may have to do a fink selfupdate. I missed that step and kept wondering why the Fink distribution was so far behind the current version. :) On Dec 9, 2004, at 12:41 PM, Graham Percival wrote: On 9-Dec-04, at 6:40 AM, Paul Crabbe wrote: I installed lilypond 2.3.13 on Mac OSX Please upgrade to stable lilypond in fink (it's 2.4.2, IIRC) Cheers, - Graham ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Simple OS X Lily previewer in the works (was getting Lily/mftrace on MacOSX)
Hi all, I've just started work on a simple LilyPond previewer for OS X. It will be similar to TeXShop, but simpler--at the expense, perhaps, of flexibility. The application will be a simple LilyPond text editor with indent balancing, parenthesis balancing, and code completion and "almost live" PDF previewing--a straightforward, one-trick pony. I was mostly silent about this because I hadn't actually written any code until Thursday. Now that I have some basic functionality, I thought I'd gauge interest. I'll try to have a test version available soon, probably without syntax coloring or code completion. A few questions for you all: (1) Would use use this application? (Feel free to just email me directly.) (2) Any other key features you'd like to see? (3) Echoing Han-Wen's inquiry about a binary distribution: what would be a reasonable price? --Ed On Mar 12, 2005, at 12:59 AM, Nicolas Sceaux wrote: Thank you! Now LilyPond is compiling. Soon I'll be able to see if using LilyPond inside TeXShop is doable and interesting. nicolas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Simple OS X Lily previewer in the works (was getting Lily/mftrace on MacOSX)
(1) Would use use this application? (Feel free to just email me
directly.)
That is: would you ("yous"?) use this application?
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Simple OS X Lily previewer in the works (was getting Lily/mftrace on MacOSX)
(2) Any other key features you'd like to see? point and click. I've received a number of requests for "point-and-click." I haven't been following the discourse on the recent "point-and-click" developments in LilyPond carefully enough, so I'm not sure what is being asked for. Do you want a full graphical editor? (I do too.) Something that lets you click on a note and highlight the code? (Even that would be nice.) Or something else? These things are probably beyond my time constraints right now, but I'll keep these requests in mind. firstly, i am very grateful for the work that goes into valuable creations, and feel that nobody should work for nothing. however, as an experimental composer, i often find myself working for little to nothing. I'm a cellist who has been spending a significant amount of time recently on experimental projects that do not, as of yet, provide any financial support--so I understand the conflict between financial and artistic fulfillment. To completely ignore the long and complicated discourse on intellectual property and free software: I need to pay my bills, and cello isn't doing that right now. I could look for contract programming jobs--and I may yet find myself again with a full-time job--but right now I'd much prefer to write software that really interests me, that I myself will use, and that serves a community I personally care about. Unfortunately, to do that, I need to ask for compensation. That said, I plan to release this tool as some flavor of shareware, and I certainly want to make it affordable to the experimental composer or composition student or struggling cellist "slash" programmer*. --Ed *and not the other way around: http://www.imdb.com/title/tt0196229/ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Text encoding
Hi all, I have a few questions/clarifications about text encoding in LilyPond. These are are covered to some extent in the list archives and in the docs, but I wanted to check with the list to get the most accurate information from the horses' mouths... (1) This is what I'm getting from the lilypond-user and lilypond-devel archives: LilyPond 2.4.x and earlier use ISO Latin1 as the native encoding, and 2.5+ are using UTF-8. Therefore, a LilyPond previewer ideally should detect the version of LilyPond being used and output the right encoding accordingly. Is this accurate? (2) Aside from one allusion in section 10.2.2 (perhaps out of date?) the \encoding command has been expunged from the 2.5 documentation, and the section entitled "Text encoding" makes it sound like UTF-8 is the only way to go. Does that mean that \encoding is no longer supported? What about \encoded-simple? (3) Is TeX encoding gone too? If not, how do you access it? (I have no particular use for it; for this one I'm just curious.) Thanks much, Ed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Text encoding
Well, I'd like to have a usable--though not feature-rich--preview version out within a couple weeks. Since 2.4 is still the current "stable" version, I might as well support it--it's a matter of changing a single constant in a method call to output in Latin1 instead of UTF-8. Correct me if I'm wrong, but I'm assuming that the silence means that everything I said was accurate: in 2.5+, we have UTF-8 only, and \encoding and \encoded-simple are no longer supported. --Ed On Apr 24, 2005, at 3:12 PM, Han-Wen Nienhuys wrote: Op zo, 24-04-2005 te 12:06 -0700, schreef Ed Baskerville: Hi all, I have a few questions/clarifications about text encoding in LilyPond. These are are covered to some extent in the list archives and in the docs, but I wanted to check with the list to get the most accurate information from the horses' mouths... (1) This is what I'm getting from the lilypond-user and lilypond-devel archives: LilyPond 2.4.x and earlier use ISO Latin1 as the native encoding, and 2.5+ are using UTF-8. Therefore, a LilyPond previewer ideally should detect the version of LilyPond being used and output the right encoding accordingly. Is this accurate? (2) Aside from one allusion in section 10.2.2 (perhaps out of date?) the \encoding command has been expunged from the 2.5 documentation, and the section entitled "Text encoding" makes it sound like UTF-8 is the only way to go. Does that mean that \encoding is no longer supported? What about \encoded-simple? forget about supporting 2.4. By the time you get you'll get the first version of your tool out, we'll probably be well on our way into 2.7 :-) (3) Is TeX encoding gone too? yup -- Han-Wen Nienhuys - [EMAIL PROTECTED] LilyPond Software Design - http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OS X 10.4 spotlight indexing of .ly files?
If you haven't heard about it on this list, I suspect nobody has done
one yet. I'll take it under advisement that there's a desire for this.
One temporary solution: the easiest way to tell OS X that your .ly
files are text files is to set their HFS metadata type attribute like
so (assuming all your files are in ~/Documents):
find ~/Documents .name '*.ly' -type f -exec /Developer/Tools/SetFile -
t 'TEXT' {} \;
(stolen from a thread on importing log files at:
http://episteme.arstechnica.com/eve/ubb.x/a/tpc/f/8300945231/m/
307008223731
)
Then they'll be searchable, to the extent that these files are
searchable as plain text, by Spotlight. (I ran this with a Spotlight
search window open, and it highlighted the power of that technology--
LilyPond files showed up instantaneously in the existing search
results after I ran the command. Cool.)
Of course, you have to re-run this every time you write out a .ly
file, unless you're using an editor that sets this attribute for you.
Short-term, doing one that simply passes things on to the default
text importer is apparently like 4 lines of code; I'd just have to
research what those lines are.
Long-term, of course, a real metadata importer that understands
LilyPond syntax would be great. Which would be very easy for me to do
if I get around to syntax coloring with this Lily editor I'm writing.
--Ed
On May 11, 2005, at 11:25 AM, Arjan Bos wrote:
Hi there all you Mac OS X Tiger users.
Does anyone of you know of a metadata importer for lilypond files?
Because currently they are not indexed.
The documents from Apple tell how to do it, but since my c classes
are 12 years ago, I'm very rusty in this area. So if someone has
already done an importer I'd be very happy with a copy.
The areas that imho need to be indexed are all commands (those that
start with \command-name), all scheme definitions and all header
information and all lyrics (without the timing and melismata
preferably).
Regards,
Arjan
---
It was funny how people were people everywhere you went, even if
the people concerned weren't the people the people who made up the
phrase "people are people everywhere" had traditionally thought of
as people. And even if you weren't virtuous, as you had been
brought up to understand the term, you did like to see virtue in
other people, provided it didn't cost you anything.
-- (Terry Pratchett, The Fifth Elephant)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OS X 10.4 spotlight indexing of .ly files?
Two things:
(1)
find ~/Documents .name '*.ly' -type f -exec /Developer/Tools/
SetFile -t 'TEXT' {} \;
That should be -name, not .name.
(2)
Short-term, doing one that simply passes things on to the default
text importer is apparently like 4 lines of code; I'd just have to
research what those lines are.
I was sufficiently inspired and figured out what those lines of code
are, and I am happy to share the results. An extremely stupid-simple
LilyPond metadata importer, that simply interprets the contents of
the file as plain text, is at:
http://edbaskerville.com/software/lilypond-importer/
LilyPond.mdimporter.zip
Just put it in /Library/Spotlight/, and your .ly files should be
indexed.
Code if you're interested (it's a pretty minor modification of the
default metadata importer template):
http://www.edbaskerville.com/software/lilypond-importer/
LilyPondImporter-source.zip
--Ed
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OS X 10.4 spotlight indexing of .ly files?
If you haven't heard about it on this list, I suspect nobody has done
one yet. I'll take it under advisement that there's a desire for this.
One temporary solution: the easiest way to tell OS X that your .ly
files are text files is to set their HFS metadata type attribute like
so (assuming all your files are in ~/Documents):
find ~/Documents .name '*.ly' -type f -exec /Developer/Tools/SetFile -
t 'TEXT' {} \;
(stolen from a thread on importing log files at:
http://episteme.arstechnica.com/eve/ubb.x/a/tpc/f/8300945231/m/
307008223731
)
Then they'll be searchable, to the extent that these files are
searchable as plain text, by Spotlight. (I ran this with a Spotlight
search window open, and it highlighted the power of that technology--
LilyPond files showed up instantaneously in the existing search
results after I ran the command. Cool.)
Of course, you have to re-run this every time you write out a .ly
file, unless you're using an editor that sets this attribute for you.
Short-term, doing one that simply passes things on to the default
text importer is apparently like 4 lines of code; I'd just have to
research what those lines are.
Long-term, of course, a real metadata importer that understands
LilyPond syntax would be great. Which would be very easy for me to do
if I get around to syntax coloring with this Lily editor I'm writing.
--Ed
On May 11, 2005, at 11:25 AM, Arjan Bos wrote:
Hi there all you Mac OS X Tiger users.
Does anyone of you know of a metadata importer for lilypond files?
Because currently they are not indexed.
The documents from Apple tell how to do it, but since my c classes
are 12 years ago, I'm very rusty in this area. So if someone has
already done an importer I'd be very happy with a copy.
The areas that imho need to be indexed are all commands (those that
start with \command-name), all scheme definitions and all header
information and all lyrics (without the timing and melismata
preferably).
Regards,
Arjan
---
It was funny how people were people everywhere you went, even if
the people concerned weren't the people the people who made up the
phrase "people are people everywhere" had traditionally thought of
as people. And even if you weren't virtuous, as you had been
brought up to understand the term, you did like to see virtue in
other people, provided it didn't cost you anything.
-- (Terry Pratchett, The Fifth Elephant)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OS X 10.4 spotlight indexing of .ly files?
Two things:
(1)
find ~/Documents .name '*.ly' -type f -exec /Developer/Tools/
SetFile -t 'TEXT' {} \;
That should be -name, not .name.
(2)
Short-term, doing one that simply passes things on to the default
text importer is apparently like 4 lines of code; I'd just have to
research what those lines are.
I was sufficiently inspired and figured out what those lines of code
are, and I am happy to share the results. An extremely stupid-simple
LilyPond metadata importer, that simply interprets the contents of
the file as plain text, is at:
http://edbaskerville.com/software/lilypond-importer/
LilyPond.mdimporter.zip
Just put it in /Library/Spotlight/, and your .ly files should be
indexed.
Code if you're interested (it's a pretty minor modification of the
default metadata importer template):
http://www.edbaskerville.com/software/lilypond-importer/
LilyPondImporter-source.zip
--Ed
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Thick barline connections between staves
Hi all, In all the examples for 2.5.26, the barline connection between staves is thicker than the barline within the staff. Is this a known problem that's being addressed? Should I just hold out for 2.6 final? --Ed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Thick barline connections between staves
I'm on Tiger (10.4.1). So, yeah, could be a problem with Apple's PDF
rendering?
As I zoom in farther and farther it's less and less noticeable. It
almost looks as if the edges of the line between the staves is being
fuzzed ("antialiased", though there's no real possibility of
aliasing) and the lines on the staves are not, making the former look
a little wider.
On May 27, 2005, at 2:44 PM, Sean Reed wrote:
hi ed, han-wen,
i mentioned this today as well, and have seen it since approx.
2.5.18 or so.
stan sanderson also mentioned it in an email from 12.04.2005 with
the subject "2.5.18 bar line thickness error(?)"
what stan and i have in common is macos 10.3.x.
ed: are you also on a mac?
is this maybe a mac-specific problem or is it also on other platforms?
for me, the image in the pdf viewer is thicker, but the printout is
fine.
-sean
Sean Reed
Hamburg, Germany
Web: www.seanreed.de
On 27.05.2005, at 20:31, Han-Wen Nienhuys wrote:
Ed Baskerville wrote:
Hi all,
In all the examples for 2.5.26, the barline connection between
staves is thicker than the barline within the staff. Is this a
known problem that's being addressed? Should I just hold out for
2.6 final?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
