In message <20090412.081216.173533445...@gnu.org>, Werner LEMBERG
writes
And wait, once we've founded our new group and taken over the world,
they'll have to call themselves ZEBRA Zebra" :-)
This is not uncommon. For example, the common toad is called `Bufo
bufo' in Latin; the human race is
> And wait, once we've founded our new group and taken over the world,
> they'll have to call themselves ZEBRA Zebra" :-)
This is not uncommon. For example, the common toad is called `Bufo
bufo' in Latin; the human race is `Homo sapiens sapiens', etc., etc.
Werner
___
On Tuesday 07 April 2009 03:32:43 pm Mark Polesky wrote:
> I was fiddling around with output-ps.scm (specifically
> the grob-cause procedure on line 159) and was getting
> frustrated with the poor indentation displaying in my
> editor when I realized that this was being caused by
> tab characters
Valentin Villenave wrote:
2009/4/11 Jonathan Kulp :
I want in on this, too! All I've been lacking to have a go at writing an
opera is a libretto. :)
OK, let's start a composers team then, but you'll have to find a good
name for it :-)
As for the need of a libretto, I have to say that this
2009/4/11 Graham Percival :
> ... WTM?! There actually *is* a "GNU Zebra" project?!?! It does
> TCP/IP routing.
And wait, once we've founded our new group and taken over the world,
they'll have to call themselves ZEBRA Zebra" :-)
> Ok, over the summer we'll try to come up with the history of
>
On Sat, Apr 11, 2009 at 06:52:30AM -0500, Jonathan Kulp wrote:
> Graham Percival wrote:
>> Valentin:
>>> Awesome. I'm precisely in search of a new libretto... And Graham
>>> chickened out when I offered him to write something with me :-)
>>
>> Ok, over the summer we'll try to come up with the histo
Graham Percival wrote:
2009/4/9 Jan Nieuwenhuizen :
Brilliant! Let's define the MOOSE/coding standards in an Opera!
Awesome. I'm precisely in search of a new libretto... And Graham
chickened out when I offered him to write something with me :-)
Ok, over the summer we'll try to come up with
On Thu, Apr 09, 2009 at 10:28:00PM +0200, Valentin Villenave wrote:
> 2009/4/9 Graham Percival :
> > On Thu, Apr 09, 2009 at 03:33:06PM +0200, Jan Nieuwenhuizen wrote:
> >> Now how do we prevent that in some far away future,
> >> people will have forgotten this and propose to deviate from
> >> the
In message <20090409143812.ga4...@nagi>, Graham Percival
writes
Oh sweet $DIETY yes. I /hate/ it when people fix bugs in my code.
It's like, guys, I'm perfect, duh! Like, I added those "bugs" for
a reason!
Is that like abstaining from $CHOCOLATE?
Cheers,
Wol
--
Anthony W. Youngman - anth...
On 9 Apr 2009, at 06:04, Han-Wen Nienhuys wrote:
Programming standards for LilyPond call for avoiding the tab
character.
We're free to choose whatever programming conventions we want for
our source
code.
I don't think it is a standard, but I would not mind making it a
standard.
Some ye
2009/4/9 Graham Percival :
> On Thu, Apr 09, 2009 at 03:33:06PM +0200, Jan Nieuwenhuizen wrote:
>> Now how do we prevent that in some far away future,
>> people will have forgotten this and propose to deviate from
>> the Zebra standard? I suggest to prefix all names in our
>> softwares in our to b
Le 7 avr. 09 à 23:28, Carl D. Sorensen a écrit :
LilyPond programming standards call for no tabs in the files.
Wrong. All source files are "C-x h M-x tabify"ed.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/li
On Thu, Apr 09, 2009 at 03:28:29PM -, dem...@suffolk.lib.ny.us wrote:
>
> AHA, we could consider beasts as drawn on old maps, whales, dolphins, lots
> of hoary depictions to choose from there, and all old enough to be PD.
DRAGON/LilyPond !!oneone!
"Here be engravers"
"Meddle not in the affai
On Thu, Apr 9, 2009, Jan Nieuwenhuizen said:
> No, but that's why I propose to first start our Zebra group and
> figure out coding standards. It's about time we got some, no?
coding standards, yes. But as to animals, we probably should contact
O'Reilly publicatinos and ask to be assigned one,
On Thu, Apr 9, 2009, Graham Percival said:
> I can see it now: CARBON-BASED LIFEFORM WITH A RELATIVELY SHORT
> LIFESPAN ON THE COSMIC SCALE/LilyPond.
Apple deprecated Carbon development some years back.
My vote is BBEdit.
Lots of programming editors offer syntax coloration and formatting for
On Thu, Apr 09, 2009 at 04:27:45PM +0200, Jan Nieuwenhuizen wrote:
> Op donderdag 09-04-2009 om 22:14 uur [tijdzone +0800], schreef Graham
> Percival:
>
> > Oh, certainly. But I think it would *also* be stupid to create a
> > programmer's edit, when vim is already perfect. :P
>
> True. Let's j
On Thu, Apr 9, 2009 at 11:14 AM, Graham Percival
wrote:
> Nah; Valentin will keep the legend of the Grumpy Developer alive
> in times to come. Long after humanity has colonized distant
> stars, schoolchildren will be reading about the epic flamewars
> involving Achilles, Trojan Horses, and wheth
Op donderdag 09-04-2009 om 22:14 uur [tijdzone +0800], schreef Graham
Percival:
> Oh, certainly. But I think it would *also* be stupid to create a
> programmer's edit, when vim is already perfect. :P
True. Let's just keep manually formatting everything. I mean,
people's tastes differ for a re
On Thu, Apr 09, 2009 at 03:33:06PM +0200, Jan Nieuwenhuizen wrote:
> However, I think it would be stupid if we created a programmer's
> editor and then *not* have it default to our coding standards?
Oh, certainly. But I think it would *also* be stupid to create a
programmer's edit, when vim is al
Op donderdag 09-04-2009 om 20:01 uur [tijdzone +0800], schreef Graham
Percival:
> See, I was with you until this point. Tying code indentation to a
> particular editor is... not ideal.
No, but that's why I propose to first start our Zebra group and
figure out coding standards. It's about time w
On Thu, Apr 09, 2009 at 11:27:42AM +0200, Jan Nieuwenhuizen wrote:
> We could then maybe sponsor that group to create a programmer's editor
> --that would be something that everyone needs? We could make it
> automatically format the program code so that it adheres to that
> standard while you typ
Op donderdag 09-04-2009 om 09:53 uur [tijdzone +0100], schreef Anthony
W. Youngman:
> Someone else will know more than me, but I think the linux kernel
> standards
What a good idea! But wait, maybe we can start or join join some kind
of "linux software group" and use their standards? Only soft
In message
, Han-Wen
Nienhuys writes
On Tue, Apr 7, 2009 at 8:18 PM, Carl D. Sorensen wrote:
As to LY not accepting tabs, thats a shame, tabs should be treated as
white space, along with and other now-disused
characters from the days of teletypes which sometimes find their way into
ascii
Op donderdag 09-04-2009 om 01:04 uur [tijdzone -0300], schreef Han-Wen
Nienhuys:
> I don't think it is a standard, but I would not mind making it a standard.
Yes, I agree we should first make it a standard. It is is very
annoying if every project uses its own set of petty deviations.
Any takers
On Tue, Apr 7, 2009 at 8:18 PM, Carl D. Sorensen wrote:
>> As to LY not accepting tabs, thats a shame, tabs should be treated as
>> white space, along with and other now-disused
>> characters from the days of teletypes which sometimes find their way into
>> ascii files from odd unix and dos s
Op dinsdag 07-04-2009 om 15:28 uur [tijdzone -0600], schreef Carl D.
Sorensen:
> LilyPond programming standards call for no tabs in the files.
Not so. http://www.gnu.org/prep/standards/html_node/index.html
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~j
Carl D. Sorensen wrote:
> I don't think that it requires programming. It probably requires
> identifying a readily available tool that fixes code up properly. I think
> it's more a finding job than a creating job.
Could we work with this?
http://www.gnu.org/software/guile/manual/html_node/Pret
On Tue, 2009-04-07 at 17:18 -0600, Carl D. Sorensen wrote:
>
>
> On 4/7/09 4:17 PM, "dem...@suffolk.lib.ny.us"
> wrote:
>
>
> >
> > As to LY not accepting tabs, thats a shame, tabs should be treated as
> > white space, along with and other now-disused
> > characters from the days of telet
On 4/7/09 4:17 PM, "dem...@suffolk.lib.ny.us"
wrote:
>
> As to LY not accepting tabs, thats a shame, tabs should be treated as
> white space, along with and other now-disused
> characters from the days of teletypes which sometimes find their way into
> ascii files from odd unix and dos s
On 4/7/09 4:46 PM, "Mark Polesky" wrote:
>
>
>> Carl D. Sorensen wrote:
>
>> What version of LilyPond did you get output-ps.scm from? In
>> order to make a patch, I need both the before and after files.
>
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=scm/output-p
> s.
> Carl D. Sorensen wrote:
> What version of LilyPond did you get output-ps.scm from? In
> order to make a patch, I need both the before and after files.
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=scm/output-ps.scm;hb=HEAD
(about 20 minutes ago)
> An automated way to do th
On 4/7/09 4:23 PM, "Mark Polesky" wrote:
> Carl D. Sorensen wrote:
>> LilyPond programming standards call for no tabs in the files.
>>
>> If you convert all the tabs to an appropriate number of spaces to get the
>> indentation right, please submit a patch so we can fix this.
>
> Here's outpu
Carl D. Sorensen wrote:
> LilyPond programming standards call for no tabs in the files.
>
> If you convert all the tabs to an appropriate number of spaces to get the
> indentation right, please submit a patch so we can fix this.
Here's output-ps.scm with spaces instead of tabs.
Is there a way to
On Tue, Apr 7, 2009, Patrick McCarty said:
>> Is there an easy way to address this?
use a programming editor. tabs were invented at a time when fixed-width
was the norm, high-speed printers and teletypes had no other way to put
ink on paper. back then, the tab stops were 8 chars apart.
Progr
LilyPond programming standards call for no tabs in the files.
If you convert all the tabs to an appropriate number of spaces to get the
indentation right, please submit a patch so we can fix this.
Thanks,
Carl
On 4/7/09 1:32 PM, "Mark Polesky" wrote:
>
>
> I was fiddling around with output
On Tue, Apr 7, 2009 at 12:32 PM, Mark Polesky wrote:
>
> I was fiddling around with output-ps.scm (specifically
> the grob-cause procedure on line 159) and was getting
> frustrated with the poor indentation displaying in my
> editor when I realized that this was being caused by
> tab characters in
I was fiddling around with output-ps.scm (specifically
the grob-cause procedure on line 159) and was getting
frustrated with the poor indentation displaying in my
editor when I realized that this was being caused by
tab characters in the source.
Is there an easy way to address this? I don't know
37 matches
Mail list logo
