On Wed, 20 Jun 2012 10:14:09 +0100, Phil Holmes wrote:
> - Original Message -
> From: "James Harkins" To: "lily-users"
> Sent: Wednesday, June 20, 2012 9:36 AM Subject:
> Re: "-dshow-available-fonts" vs. UNIX stdout?
>
>
>> On 6/2
Date: Wed, 20 Jun 2012 09:26:10 -0700
From: Tim Roberts
> Most folks with Unix command-line experience, when noticing that the
> output wasn't caught in stdout, would automatically try stderr (2>) next.
Thanks for the helpful suggestions. In fact, my UNIX commandline chops are
mediocre at best.
probably lilypond isn't writing to stdout. maybe stderr?
On Jun 20, 2012 9:20 AM, "James Harkins" wrote:
> I just encountered something curious while trying to get a list of fonts
> on my machine from lilypond. According to the documentation of font
> selection:
>
> lilypond -dshow-available-font
Use &> to redirect both stderr and stdout where you want it.
Great in any case where you're not too sure which std*** pipe youre
looking for, or dont care...
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/li
Tim Roberts writes:
> Ramana Kumar wrote:
>> FWIW I agree that -dshow--available-fonts should write to stdout.
>
> Before this goes much further, please realize that this is a matter of
> opinion. There is no unambiguously correct answer to this issue. The
> fact is that lilypond writes the out
Ramana Kumar wrote:
> FWIW I agree that -dshow--available-fonts should write to stdout.
Before this goes much further, please realize that this is a matter of
opinion. There is no unambiguously correct answer to this issue. The
fact is that lilypond writes the output to stderr, and that's the wa
- Original Message -
From: "David Kastrup"
To:
Sent: Wednesday, June 20, 2012 10:38 AM
Subject: Re: "-dshow-available-fonts" vs. UNIX stdout?
"Phil Holmes" writes:
- Original Message -
From: "James Harkins"
To: "lily-u
- Original Message -
> > From: "James Harkins"
> > To: "lily-users"
> > Sent: Wednesday, June 20, 2012 9:36 AM
> > Subject: Re: "-dshow-available-fonts" vs. UNIX stdout?
> >
> >
> >> On 6/20/12, Ramana Kumar wrot
"Phil Holmes" writes:
> - Original Message -
> From: "James Harkins"
> To: "lily-users"
> Sent: Wednesday, June 20, 2012 9:36 AM
> Subject: Re: "-dshow-available-fonts" vs. UNIX stdout?
>
>
>> On 6/20/12, Ramana Kumar
- Original Message -
From: "James Harkins"
To: "lily-users"
Sent: Wednesday, June 20, 2012 9:36 AM
Subject: Re: "-dshow-available-fonts" vs. UNIX stdout?
On 6/20/12, Ramana Kumar wrote:
probably lilypond isn't writing to stdout. maybe stderr?
At 16:20 on 20 Jun 2012, James Harkins wrote:
>I just encountered something curious while trying to get a list of
>fonts on my machine from lilypond. According to the documentation of
>font selection:
>
>lilypond -dshow-available-fonts x
>
>This does indeed list of fonts, but the terminal doesn't k
On 6/20/12, Ramana Kumar wrote:
> probably lilypond isn't writing to stdout. maybe stderr?
OK, let me refine the question. If it isn't using stdout, is there a
good reason why is it using something else? Or is it just a bug?
hjh
--
James Harkins /// dewdrop world
jamshar...@dewdrop-world.net
James Harkins-2 wrote:
>
> I just encountered something curious while trying to get a list of fonts
> on my machine from lilypond. According to the documentation of font
> selection:
>
>
>
>
it goes to stderr - so you have to use (according to
http://lilypond.org/doc/v2.15/Documentation/usa
I just encountered something curious while trying to get a list of fonts on my
machine from lilypond. According to the documentation of font selection:
lilypond -dshow-available-fonts x
This does indeed list of fonts, but the terminal doesn't keep enough lines to
see the entire list. So I thoug
14 matches
Mail list logo
