TUNES

[Brian P Templeton]

Bj=F6rnke von Gierke <bvg@mac.com> writes:

>> Should be a Cc: - and usually the sender doesn't mind receiving a copy
>> (he might be unsubscribed to the list), plus you can remove him manually
>> from the destinations, if you know for sure he's subscribed.
> Err... thats on purpose? Well, thats the reason why most people hate
> computers :(
>=20
> the originator sends a mail to the list, is subscribed, and I reply:
> as is "reply":
> Header:(to:originator)
> mails received: originator: 1 list member: 0 myself: 0
> as i suggest "reply to: list"
> Header:(to:list)
> mails received: originator: 1 list member: 1 myself: 1
>=20
> the originator sends a mail to the list, is NOT subscribed, and I reply:
> as is: mails received: originator: 1 list member: 0 myself: 0
> as i suggest: mails received: originator: 0 list member: 1 myself: 1
>=20
> Now we have the same causes when users rearrange and uses the "reply
> to all" feature:
> as is: mails received: originator: 2 list member: 1 myself: 1
> as I suggest: mails received: originator:1 list member:1 myself:1
>=20
> I think that you would like that the originator always get's a
> response, but hes only one, and thus i think the list members are
> first priority here. Also if he want's a response, why doesn't he
> subscribe to the list?
>=20
>>>> if you're willing to write a system that adds features for other
>>>> browsers without sacrificing compatibility [with CLI browsers] *snip*
>>> Well, thats quiet simple with an intro-page, which has a link for [...]
>> Just do it - you seem to know better about it than I, anyway.
>> If you don't have write access to the CVS yet, just fill in the
>> membership form and ask an account to root@bespin.org.
> Is that a Joke? I mean you don't know me, and I didn't even tell you
> that im here to overtake the project and cripple it, by order of his
> billyness ;-)
> Also I don't really know anything about programming and what exactly
> is a CVS?
CVS is the Concurrent Version Control system. Although IMHO PRCS is a
better VC system, CVS is more common. Other versioning systems include
PRCS, RCS, Aegis, SCCS, etc. From FOLDOC (following some references
from the definition for CVS):
     __________________________
____/ `dict "code management"' \______________________________________
| 1 definition found
|=20
| From The Free On-line Dictionary of Computing (07Oct99) [foldoc]:
|=20
|   code management
|=20=20=20
|           A source code management system helps program developers keep
|           track of version history, releases, parallel versions etc.
|           There are several in popular use.
|=20=20=20
|           (1994-12-23)
|_____________________________________________________________________

> May I now add my own homepage to the project?
>=20
No. When you join the project, you'll get a Bespin account. After
placing your WWW files in ~/html on the bespin.org machine (using SCP
or SSH), you can reach ~/html/foo with the URLs (assuming you select
the username bvg):

    http://www.bespin.org/~bvg/foo
    http://www.tunes.org/~bvg/foo

and, if you ask Tril to (if I'm guessing right) set up a new Apache
virtual host (it's required if you want to use CGI, and otherwise
optional):

    http://bvg.tunes.org/foo

Your homepage is separate from the actual TUNES Project pages.

>> The problem being here that we lack coherent documentation outside of
>> the FAQ, that the FAQ could point to. In absence of it, a two-sized FAQ
>> might do. If linuxdoc-sgml can't handle it, we might migrate to HeVeA
>> or to TeX2page.
> well I would write a new faq, and put it into the introduction/welcome
> part of the homepage, and then use the old faq as a base to grow from
> in the documentation.
>=20
>>> Listener? well ok it crunches strings... does it understand sentences?
>> Not unless you teach it too.
>> Begin simple, elaborate as you go, refactor the simple thing afterwards.
>> Be ready to see your code refactored, knowing that since the code AND
>> the execution environment in which it was successfully run are
>> versioned,
>> so that you will be able to run your old code despite incompatible new
>> refactorings, evolutions, modifications.
>>
>>> Or do you mean string as in "long" ?
>> I mean "string" as in source code that you can evaluate incrementally,
>> input from primitive but standard means of communication such as
>> text file editors, line editors, raw terminal input, etc.
>>
> I still don't get the diffrence between a runtime compiler and your
> approach... but its 4:20 at night, and il go to sleep now, maybe i'l
> understand tomorrow.
>=20
> have a nice day
> bj=F6rnke
>=20

--=20
BPT <bpt@tunes.org>	    		/"\ ASCII Ribbon Campaign
backronym for Linux:			\ / No HTML or RTF in mail
	Linux Is Not Unix			 X  No MS-Word in mail
Meme plague ;)   --------->		/ \ Respect Open Standards