 | | Re: Announcing FTX for discussion groups
|
|
It is summer time, not lego time (= winter time), so I haven't felt this before now. I haven't seen this in my newsreader, but I can imagine that it might look really funny/odd. But leaving that of, here is my first suggestion: I will only post (...) (21 years ago, 10-Jun-03, to lugnet.publish)
|
| |
| | Mo'betta Mo'betta pics of on biomechanicalbricks.com
|
|
Mo'betta pics of me, the Jamocklaquat, and the Little Bots Series. All New Photography! Please have a look. (URL) Brighter Jama Picture:> (URL) 7 Little Sort Bots:> (2 URLs) me:> More goodies soon. e <www.biomechanicalbricks.com> (21 years ago, 3-Jun-03, to lugnet.technic, lugnet.build.mecha, lugnet.robotics, lugnet.publish, FTX)
|
| |
| | Re: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) I see. With extensive modifications, I assume? I'm sure there's a way to link libperl.so to CNews but that could be unweildy to say the least. (...) Sorry I can't view the FTX results of that on my browser. But I assume that's right. (...) I (...) (21 years ago, 3-Jun-03, to lugnet.publish, lugnet.admin.nntp)
|
| |
| | Re: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) CNews. (...) Doesn't that look a bit redundant? /italics/ and *boldface* What do underlined underlines look like? Like this?-- _N_ew _E_ngland _L_EGO _U_sers _G_roup Not sure how either any of those are an improvement. --Todd (21 years ago, 3-Jun-03, to lugnet.publish, lugnet.admin.nntp, FTX)
|
| |
| | Re: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) What NNTP server do you use? I was under the impression that it was written in Perl itself. [...] (...) How about a different interpretation - // and ** (and don't forget __ for underlining) might not be interpreted the same as the {} and [] (...) (21 years ago, 2-Jun-03, to lugnet.publish, lugnet.admin.nntp)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Do you have Lucida Typewriter? Try setting your fixed-width font to default to that...it's a bit easier on the eyes than Courier. (...) Well, the only consolation I can offer today is a promise that we're making movements towards CSS, which (...) (21 years ago, 2-Jun-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) I guess I don't see the advantage of this part, and I can't stand how when reading via the web it makes the listed posts look one way, and the posts themselves a completely different way. Plus, that fixed-width font is a killer on the eyes. (...) (21 years ago, 2-Jun-03, to lugnet.publish, FTX)
|
| |
| | Re: New Gear Boxes and Motor Systems
|
|
Thanks, Todd (...) Actually I didn't noticed I was in FTX mode... BTW, could it be possible to keep a cookie with personnal preference about FTX ? While it can be very useful, I'd prefer to default to plain text for most ordinary messages ! (...) I (...) (21 years ago, 2-Jun-03, to lugnet.technic, lugnet.publish)
|
| |
| | Re: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) Can't speak for Mozilla, but OEQuotefix doesn't react on the above line (or any other of Brian's suggestions), it seems to only process special characters at the beginning, and ending, of a word, and does nothing if special chars overlap, like (...) (21 years ago, 1-Jun-03, to lugnet.publish, lugnet.admin.nntp)
|
| |
| | Re: New Gear Boxes and Motor Systems
|
|
(...) Links in FTX require an opening < and closing >. Todd, perhaps you could turn on the same "www." and "(URL) recognition that plain text uses for FTX? Some sort of hard character return recognition would be nice too...I'm not in the habit of (...) (21 years ago, 31-May-03, to lugnet.technic, lugnet.publish, FTX)
|
