On Dec 12, 2012, at 11:03 AM, Paul Morris wrote:
> I tried to follow those instructions recently (to try the png output) but was
> not able to get it to run.
For future command-line beginners like myself, I figured out the problem:
I needed to change the shell I was using from tcsh to bash.
Hey guys,
thank you so much. I feel stupid now, can't believe I missed that. I guess
my eyes were looking for the word "terminal". Also, I would have maybe
expected that information to also exist under the Manual link and not
Downloads!
either way, big thanks
/Parham
On 13 December 2012 00:25, P
On Dec 12, 2012, at 6:13 PM, Parham Fazelzadeh
wrote:
> I have tried searching for the answer online
[...]
> thank you so much. I feel stupid now, can't believe I missed that. I guess my
> eyes were looking for the word "terminal". Also, I would have maybe expected
> that information to also
On Dec 12, 2012, at 16:57, Hans Aberg wrote:
> On 12 Dec 2012, at 23:50, Eric Pancer wrote:
>
>> On Wed, Dec 12, 2012 at 4:48 PM, Hans Aberg wrote:
>>> On 12 Dec 2012, at 21:16, Eric Pancer wrote:
>>>
On Wed, Dec 12, 2012 at 2:14 PM, David Kastrup wrote:
> The libexec route appears t
On 12 Dec 2012, at 21:16, Eric Pancer wrote:
> On Wed, Dec 12, 2012 at 2:14 PM, David Kastrup wrote:
>> The libexec route appears to cater for all of that. We should use bin
>> just for executables supposed to be entry points of LilyPond.
>
> Please, no!
>
> From man 1 hier
>
On 12 Dec 2012, at 23:50, Eric Pancer wrote:
> On Wed, Dec 12, 2012 at 4:48 PM, Hans Aberg wrote:
>> On 12 Dec 2012, at 21:16, Eric Pancer wrote:
>>
>>> On Wed, Dec 12, 2012 at 2:14 PM, David Kastrup wrote:
The libexec route appears to cater for all of that. We should use bin
just fo
On Wed, Dec 12, 2012 at 4:48 PM, Hans Aberg wrote:
> On 12 Dec 2012, at 21:16, Eric Pancer wrote:
>
>> On Wed, Dec 12, 2012 at 2:14 PM, David Kastrup wrote:
>>> The libexec route appears to cater for all of that. We should use bin
>>> just for executables supposed to be entry points of LilyPond.
On Wed, Dec 12, 2012 at 3:15 PM, David Kastrup wrote:
> The whole point was _not_ to have it added to the PATH as it was
> supposed to _only_ contain binaries used _internally_ in LilyPond.
Ah! Sorry, I'll smack my own forehead :-)
___
lilypond-user ma
Eric Pancer writes:
> On Wed, Dec 12, 2012 at 3:02 PM, David Kastrup wrote:
>> Eric Pancer writes:
>>
>>> On Wed, Dec 12, 2012 at 2:25 PM, David Kastrup wrote:
Which is pretty much what we are talking about. I was not talking about
/libexec but libexec, like the LilyPond executables
On Wed, Dec 12, 2012 at 3:02 PM, David Kastrup wrote:
> Eric Pancer writes:
>
>> On Wed, Dec 12, 2012 at 2:25 PM, David Kastrup wrote:
>>> Which is pretty much what we are talking about. I was not talking about
>>> /libexec but libexec, like the LilyPond executables are not in /bin but
>>> some
Eric Pancer writes:
> On Wed, Dec 12, 2012 at 2:25 PM, David Kastrup wrote:
>> Which is pretty much what we are talking about. I was not talking about
>> /libexec but libexec, like the LilyPond executables are not in /bin but
>> some bin (well, actually out/bin) and, after installation, in some
On Wed, Dec 12, 2012 at 2:25 PM, David Kastrup wrote:
> Which is pretty much what we are talking about. I was not talking about
> /libexec but libexec, like the LilyPond executables are not in /bin but
> some bin (well, actually out/bin) and, after installation, in some
> /usr/local/bin (so the c
Eric Pancer writes:
> On Wed, Dec 12, 2012 at 2:14 PM, David Kastrup wrote:
>> The libexec route appears to cater for all of that. We should use bin
>> just for executables supposed to be entry points of LilyPond.
>
> Please, no!
>
>>From man 1 hier
>
> [..]
> libexec/ system
On Wed, Dec 12, 2012 at 2:14 PM, David Kastrup wrote:
> The libexec route appears to cater for all of that. We should use bin
> just for executables supposed to be entry points of LilyPond.
Please, no!
>From man 1 hier
[..]
libexec/ system daemons & system utilities (execute
On Wed, Dec 12, 2012 at 09:14:12PM +0100, David Kastrup wrote:
> Graham Percival writes:
>
> > The executable shims avoid those problems, while being relatively easy
> > to explain to newbies.
>
> The libexec route appears to cater for all of that. We should use bin
> just for executables suppo
Graham Percival writes:
> On Wed, Dec 12, 2012 at 08:47:27PM +0100, Hans Aberg wrote:
>>
>> On 12 Dec 2012, at 16:32, David Kastrup wrote:
>> > Stupid question: why would one create executable shims to something like
>> > DIR/LilyPond.app/Contents/Resources/bin/* in ~/bin and then add ~/bin to
>
On Wed, Dec 12, 2012 at 08:47:27PM +0100, Hans Aberg wrote:
>
> On 12 Dec 2012, at 16:32, David Kastrup wrote:
> > Stupid question: why would one create executable shims to something like
> > DIR/LilyPond.app/Contents/Resources/bin/* in ~/bin and then add ~/bin to
> > one's PATH when one can just
On 12 Dec 2012, at 16:32, David Kastrup wrote:
> Paul Morris writes:
>
>> On Dec 12, 2012, at 9:31 AM, Parham FH wrote:
>>
>>> I am curious if it is possible to run lilypond from the Mac OS X
>>> (my case: 10.6.8) terminal
>>
>> Instructions are here:
>> http://www.lilypond.org/doc/v2.16/Do
On Dec 12, 2012, at 10:32 AM, David Kastrup wrote:
> Paul Morris writes:
>
>> On Dec 12, 2012, at 9:31 AM, Parham FH wrote:
>>
>>> I am curious if it is possible to run lilypond from the Mac OS X
>>> (my case: 10.6.8) terminal
>>
>> Instructions are here:
>> http://www.lilypond.org/doc/v2.1
On Wed, Dec 12, 2012 at 9:32 AM, David Kastrup wrote:
> Paul Morris writes:
>
>> On Dec 12, 2012, at 9:31 AM, Parham FH wrote:
>>
>>> I am curious if it is possible to run lilypond from the Mac OS X
>>> (my case: 10.6.8) terminal
>>
>> Instructions are here:
>> http://www.lilypond.org/doc/v2.16/
Paul Morris writes:
> On Dec 12, 2012, at 9:31 AM, Parham FH wrote:
>
>> I am curious if it is possible to run lilypond from the Mac OS X
>> (my case: 10.6.8) terminal
>
> Instructions are here:
> http://www.lilypond.org/doc/v2.16/Documentation/web/macos-x
>
> "Running on the command-line"
Stu
On Dec 12, 2012, at 9:31 AM, Parham FH wrote:
> I am curious if it is possible to run lilypond from the Mac OS X
> (my case: 10.6.8) terminal
Instructions are here:
http://www.lilypond.org/doc/v2.16/Documentation/web/macos-x
"Running on the command-line"
Cheers,
-Paul
__
On Wed, Dec 12, 2012 at 8:31 AM, Parham FH wrote:
> I tried asking on IRC but got no replies.
> I am curious if it is possible to run lilypond from the Mac OS X
> (my case: 10.6.8) terminal since I am
> generating the data for lilypond via a python application.
> It would therefor be preferred to
Hello,
I tried asking on IRC but got no replies.
I am curious if it is possible to run lilypond from the Mac OS X
(my case: 10.6.8) terminal since I am
generating the data for lilypond via a python application.
It would therefor be preferred to run lilypond from the terminal in
an automated no
24 matches
Mail list logo
