Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    JAMNNTPD    |    Support for the JAMNNTPD software client    |    2,630 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,557 of 2,630    |
|    Nicholas Boel to Carlos Navarro    |
|    space oddity (fixes)    |
|    23 Apr 24 19:10:34    |
      MSGID: 1:154/10 66284df6       REPLY: 2:341/234.1 6627cb9a       PID: SmapiNNTPd/Linux 2.4.1       CHRS: UTF-8 4       TZUTC: -0500       TID: hpt/lnx 1.9 2024-02-05       Hello Carlos,              On Tue, Apr 23 2024 19:46:04 +0000, you wrote:               CN> No. It's just that it doesn't support f=f's soft wraps. A "real" long        CN> line is wrapped at screen width.              Yes, and then ends up with only one quote character before the first line of       the paragraph?               NB>> I tested tin on the tin nntp server that contained very old messages.        NB>> However, this was the only time I saw paragraphs adjusted to the        NB>> screen width. Anything that has come through jam/smapinntpd has been        NB>> wrapped at 72-79 characters.               CN> So it has partial f=f support, as it seems it doesn't recognize soft       wraps.              Yes, this is true for both tin and slrn. However, there is an option in both       to remove trailing spaces at the end of lines. So, it seems it may have been       known about, however, there is no function to re-flow the lines.               NB>> Some clients probably don't understand the 'soft-wrapping trailing        NB>> spaces', or don't care to put them back together to re-form long        NB>> lines, but can handle long lines themselves just fine. Am I        NB>> understanding what you are describing here, now?               CN> Yes!        CN> Thunderbird and Seamonkey do, but most others don't.              I've been noticing this, also. This has become kind of a pain in the arse. 2       nntp servers and 4 clients, and everything acts differently in combination. :(              So, I think the real way nntp servers handle it is to not mess with the       paragraph at all. One long line. However, there is (or used to be) nntp       "etiquette". Slrn and tin both warn you that what you wrote is too long, and       that it should be shortened with your editor to <80 columns. Basically they're       telling you to hard wrap with your editor (which is something I won't do). ;)              Jam/Smapinntpd has helped this quite a bit, so that most any editor can be       used and not really affect the outcome.              So if HotdogEd is your only current worry, maybe you could add some kind of       user option to change WRAP_WIDTH to 50 and LINE_WIDTH to 58 or something in       order to fit on your phone screen. But then again, it's abandonware. lol              Regards,       Nick              ... Take my advice, I don't use it anyway.       --- slrn/pre1.0.4-9 (Linux)        * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)       SEEN-BY: 15/0 90/1 103/705 105/81 106/201 120/616 123/10 124/5016       SEEN-BY: 128/260 135/220 225 153/757 7715 154/10 30 40 50 700 203/0       SEEN-BY: 218/700 220/90 221/0 6 226/30 227/114 229/110 112 113 206       SEEN-BY: 229/307 317 426 428 470 664 700 240/1120 5832 266/512 280/464       SEEN-BY: 280/5003 5555 282/1038 291/111 292/8125 301/1 310/31 320/219       SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124       SEEN-BY: 467/888 633/280 712/848 770/1 2320/105 3634/12 5020/400 5054/30       PATH: 154/10 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca