Subject:
|
Re: Please consider fixing FTX...
|
Newsgroups:
|
lugnet.admin.suggestions
|
Date:
|
Wed, 1 Jun 2005 16:22:19 GMT
|
Viewed:
|
5527 times
|
| |
|
|
In lugnet.admin.suggestions, David Eaton wrote:
| |
In lugnet.admin.suggestions, Dave Schuler wrote:
| |
Ah, yes--now I see. I manually numbered my list of sage suggestions without
realizing that an FTX option was available.
|
Out of curiosity, when you wrote the post, how did you add in the newlines?
That is, when I’m writing a post in FTX, I almost NEVER use the ¬ character
for newlines. Instead, I forget. This causes problems like this:
Pieces That Are Awesome:
- 2x4 Chrome Bricks
- Pitchforks
- White Garage Doors
- Classic Space Torsos
So, that was SUPPOSED to be a list. But I forgot to add ¬ after each line.
So FTX just puts it all onto one line. This would work just great for plain
text viewers, but NOT for FTX. For both FTX and plain text to look ok, I
SHOULD have written:
Pieces That Are Awesome:
- 2x4 Chrome Bricks
- Pitchforks
- White Garage Doors
- Classic Space Torsos
Now, THAT shows up relatively as I intended (minus the leading space before
each minus sign, which is also what makes that not recognized as a decreasing
FTX list). But the way that you wrote your earlier post appears to have been:
Pieces That Are Awesome:
- 2x4 Chrome Bricks
- Pitchforks
- White Garage
Doors
- Classic Space Torsos
Which still looks fine in FTX, but is now rather unreadable in plain text,
since it’s now on ONE line of plain text. However, did you actually write
your whole post like that? IE, without “normal” newlines? Just asking since
it would seem that writing that post without ever hitting the “enter” button
seems oddly difficult-- and if you used some other method that’s doing some
sort of conversion, maybe that conversion should be modified to include both
an FTX and a normal newline, for the sake of readability.
|
Like I said, I’m not playing to the cheap seats. Newsreaders Be Darned!
Honestly, it never even occurred to me. I’ve accessed LUGNET via the web ever
since I started reading it, and the foibles of the newsreader interface have
been, at best, abstractions to me.
In adding the newlines, I simply typed ALT-172. But now that I think of it, I
inserted them at the beginning of each line, rather than at the end of the
preceding. Might this be the problem?
Dave!
|
|
Message has 1 Reply:
 | | Re: Please consider fixing FTX...
|
| Hmm, it seems more and more folks are creating FTX posts with FTX hard new lines without a real new line. If these are being created in the web editor, could it reasonably force a real new line? It's slowly getting to the point that NNTP access to (...) (19 years ago, 6-Jun-05, to lugnet.admin.suggestions)
|
Message is in Reply To:
| | Re: Please consider fixing FTX...
|
| (...) Out of curiosity, when you wrote the post, how did you add in the newlines? That is, when I'm writing a post in FTX, I almost NEVER use the character for newlines. Instead, I forget. This causes problems like this: Pieces That Are Awesome: - (...) (19 years ago, 31-May-05, to lugnet.admin.suggestions, FTX)
|
13 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
