RE: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Jay West
Emergency Moderation Mode On, topic closed.

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Mike Stein
- Original Message - From: "Dave Woyciesjes" To: "General Discussion: On-Topic and Off-Topic Posts" Sent: Monday, April 04, 2016 2:07 PM Subject: Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD > ...Who reads an email

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Dave Woyciesjes
On 04/04/2016 02:13 PM, Guy Sotomayor wrote: On Apr 4, 2016, at 11:07 AM, Dave Woyciesjes wrote: -- ... nor would I ever expect you to ;D IMO the reason that flowed text and top posting have become the norm is that many people (myself included) find them more efficient and clearer, bot

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Dale H. Cook
At 04:00 PM 4/4/2016, Maciej W. Rozycki wrote: >I think bottom-posting without trimming is actually more evil than top-posting >... I think that any posting without trimming is a sign of a lazy and inconsiderate poster. Dale H. Cook, Roanoke/Lynchburg, VA Osborne 1 / Kaypro 4-84 / Kaypro 1 / A

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Maciej W. Rozycki
On Mon, 4 Apr 2016, Guy Sotomayor wrote: > > How so? Who reads an email message from the bottom up? > > > Because I’ve already read all of the other messages in the thread and it’s > a pain when folks bottom post and include the complete text of all of the > previous emails. I think bottom-

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread william degnan
The thing is, it's just too hard to follow a thread unless everyone posts in the same direction. If the thread, for whatever reason, flows by top post, then I follow that pattern, if it's bottom then I go that way...*this* message board has been around for a while, and the precedent is to bottom

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Guy Sotomayor
> On Apr 4, 2016, at 11:07 AM, Dave Woyciesjes wrote: > >> >> -- >> ... nor would I ever expect you to ;D >> >> IMO the reason that flowed text and top posting have become the norm >> is that many people (myself included) find them more efficient and clearer, >> both reading and writing; >

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Dave Woyciesjes
On 04/04/2016 12:30 PM, Mike Stein wrote: - Original Message - From: "Mouse" To: Sent: Monday, April 04, 2016 10:48 AM Subject: Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD Flowed text and top-posting have become the norm

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Mike Stein
- Original Message - From: "Robert Jarratt" To: "'General Discussion: On-Topic and Off-Topic Posts'" Sent: Monday, April 04, 2016 12:44 PM > I really do think that the endian-ness of posting is a matter of personal > preference. I happen to prefer top posting, but on this list I make a

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Warner Losh
On Mon, Apr 4, 2016 at 10:30 AM, Mike Stein wrote: > > Mainstream popularity is not just the much-maligned Windows on PCs, > but also iOS and Android on smart phones and tablets, and the web-based > email... I for one am glad to see the PC finally get its comeuppance from iOS, Android and the We

RE: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Robert Jarratt
> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Mouse > Sent: 04 April 2016 15:49 > To: cctalk@classiccmp.org > Subject: Re: The Right Way to Email - was Re: C & undefined behaviour - was > Re: tumble under BSD > > &

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Mike Stein
- Original Message - From: "Mouse" To: Sent: Monday, April 04, 2016 10:48 AM Subject: Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD >> Flowed text and top-posting have become the norm in mainstream email > > So ha

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Mouse
> Flowed text and top-posting have become the norm in mainstream email So have a lot of other horrible things, such as spam. Popularity, especially mainstream popularity, is no measure of goodness, or we should all immediately switch to Windows on peecees. I have no problem with flowed text - wh

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Mike Stein
folks expressing them. 'Nuff said. mike - Original Message - From: "Peter Coghlan" To: "General Discussion: On-Topic and Off-Topic Posts" Sent: Monday, April 04, 2016 5:36 AM Subject: Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tum

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Dale H. Cook
ll messages using the changed subject line will continue to be archived under the original subject line. If you look at the list archives you will see that the thread "tumble under BSD" has been hijacked several times, by people who have changed the subject line instead of stating

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-04 Thread Peter Coghlan
Mouse made a perfectly reasonable request that we make a small effort to ensure our emails are formatted appropriately. The response was that people demanded their inherent right to continue to generate improperly formatted emails, complained about grudgingly having to having to make configuration

Re: The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread ben
On 4/3/2016 8:19 PM, Toby Thain wrote: If we're doing 'the right way to email' AGAIN, at least have the courtesy of changing THE SUBJECT LINE. What and have the subject line longer than the email? --Toby Ben. BTW what do you do when your email server thinks your message is spam for a reply.

Wrap or not (was C & undefined behaviour - was Re: tumble under BSD)

2016-04-03 Thread Mike Stein
- Original Message - From: "Mouse" To: Sent: Sunday, April 03, 2016 9:48 PM Subject: Re: C & undefined behaviour - was Re: tumble under BSD ... >> But I'll be happy to comply to the wishes for preformatted text; just >> tell me how. > > I&#x

Wrap or not - was C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Mike Stein
- Original Message - From: "Mouse" To: Sent: Sunday, April 03, 2016 9:32 PM Subject: Re: C & undefined behaviour - was Re: tumble under BSD >>> (Please don't use paragraph-length lines.) >> Why not? Is your email client incapable of wrapping text?

The Right Way to Email - was Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Toby Thain
On 2016-04-03 9:48 PM, Mouse wrote: Why not? Is your email client incapable of wrapping text? Well, paragraph/lines is the way most email clients function nowadays. Windows is the way most computers function nowadays. ... Maybe there's a setting in Thunderbird that wraps the lines on writing

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Fred Cisin
I'd say, for running text, wrap somewhere before 80 characters per line (preferably before about 78, since some programs lose a column or two on display - personally, I wrap at column 72). I'm sure others will differ in various details, but I suspect most will probably be somewhere close to that.

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Mouse
>> Why not? Is your email client incapable of wrapping text? > Well, paragraph/lines is the way most email clients function > nowadays. Windows is the way most computers function nowadays. Shall we therefore reject any suggestion that Windows is not the way everyone should work? :-) (My point is

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Mouse
>> (Please don't use paragraph-length lines.) > Why not? Is your email client incapable of wrapping text? No; it just assumes that - if the text is not marked as reflowable - that it shouldn't mangle it by inserting line breaks that weren't there in the original. It is obnoxious to have a long l

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Noel Chiappa
> From: Mouse > A pity pdos.csail.mit.edu is willing to impair its accessibility for > the sake of..I'm not sure what..by refusing to serve it over HTTP. It's the latest cretinous-lemming craze in the world of high tech - we _MUST_ hide all our bits in encryption, because otherwise so

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Maciej W. Rozycki
On Sun, 3 Apr 2016, Chuck Guzis wrote: > > Why not? Is your email client incapable of wrapping text? > > Well, paragraph/lines is the way most email clients function nowadays. Maybe > there's a setting in Thunderbird that wraps the lines on writing a new email, > but most clients are perfectly ha

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Chuck Guzis
On 04/03/2016 01:31 PM, Mike Stein wrote: Why not? Is your email client incapable of wrapping text? Well, paragraph/lines is the way most email clients function nowadays. Maybe there's a setting in Thunderbird that wraps the lines on writing a new email, but most clients are perfectly happy

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Mike Stein
- Original Message - From: "Mouse" To: Sent: Sunday, April 03, 2016 3:53 PM > (Please don't use paragraph-length lines.) Why not? Is your email client incapable of wrapping text? m

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Mouse
>> Indeed, intel segmented memory model was weird. [...] >> Far pointers were insanity-inducing, though. Since there were >> multiple ways to represent the same address as a far pointer, [...] >> Thankfully, huge pointers behaved exactly as one would expect, [...] > There we have the issue. Oft

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-03 Thread Paul Koning
> On Apr 3, 2016, at 12:19 AM, Tomasz Konojacki wrote: > > On Sat, 2 Apr 2016 18:58:10 -0400 (EDT) > Mouse wrote: > >> He's assuming the "the entire address space is a single >> array of bytes (perhaps with holes)" memory model is the only possible >> one. He needs to talk with someone who wr

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-02 Thread Tomasz Konojacki
On Sat, 2 Apr 2016 18:58:10 -0400 (EDT) Mouse wrote: > He's assuming the "the entire address space is a single > array of bytes (perhaps with holes)" memory model is the only possible > one. He needs to talk with someone who wrote large-model 8086 code - > or someone who's used the Lisp Machine

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-02 Thread Toby Thain
On 2016-04-02 6:58 PM, Mouse wrote: Anyone interested in C and UB will want to read most of John Regehr's http://blog.regehr.org/ - it hosts some of the best material on UB. Unfortunately Mr. (I'm assuing this is appropriate given "John") Regehr There's a lot more on the topic; he wrote these

Re: C & undefined behaviour - was Re: tumble under BSD

2016-04-02 Thread Mouse
> Anyone interested in C and UB will want to read most of John Regehr's > http://blog.regehr.org/ - it hosts some of the best material on UB. Unfortunately Mr. (I'm assuing this is appropriate given "John") Regehr is falling into the same trap he's trying to warn against: basically, assuming that

C & undefined behaviour - was Re: tumble under BSD

2016-04-02 Thread Toby Thain
On 2016-04-02 5:22 PM, Paul Koning wrote: On Apr 2, 2016, at 5:09 PM, Mouse wrote: It appears that the stdio that I'm linking against on OS X 10.9.5 does not keep the file pointers synchronized between the system and stdio. Actually, I would say that any supposedly-portable software that d

Re: tumble under BSD

2016-04-02 Thread Paul Koning
> On Apr 2, 2016, at 5:09 PM, Mouse wrote: > >> It appears that the stdio that I'm linking against on OS X 10.9.5 >> does not keep the file pointers synchronized between the system and >> stdio. > > Actually, I would say that any supposedly-portable software that > depends on either behaviour i

Re: tumble under BSD

2016-04-02 Thread Mouse
> It appears that the stdio that I'm linking against on OS X 10.9.5 > does not keep the file pointers synchronized between the system and > stdio. Actually, I would say that any supposedly-portable software that depends on either behaviour is broken; AFAICT stdio has never promised either way. >

Re: tumble under BSD

2016-04-02 Thread Al Kossow
On 4/1/16 12:21 PM, Diane Bruce wrote: It's in ports /usr/ports/graphics/tumble Not sure if it is up to date or not. Thanks. It appears that the stdio that I'm linking against on OS X 10.9.5 does not keep the file pointers synchronized between the system and stdio. Tumble opens a file, a

Re: tumble under BSD

2016-04-01 Thread Diane Bruce
On Fri, Apr 01, 2016 at 11:55:50AM -0700, Al Kossow wrote: > Out of curiosity, has anyone ever gotten Eric Smith's tumble pdf > creation program running under any version of BSD? > > I ran into a problem porting it to OS X, in the way it used rewind() > and was wondering if anyone else ran into t

tumble under BSD

2016-04-01 Thread Al Kossow
Out of curiosity, has anyone ever gotten Eric Smith's tumble pdf creation program running under any version of BSD? I ran into a problem porting it to OS X, in the way it used rewind() and was wondering if anyone else ran into that on other BSDs