Hi Rob
Is there a reason that empty lines at the end of a message are stripped?
If
I do not enter some CR and then insert either a period or some sort of signature, the sbbsecho id is appended quite often to the end of the last line. If I do give at least one CR, it will appear as the last line.
Is there a reason that empty lines at the end of a message are
stripped?
Because they serve no purpose.
If
I do not enter some CR and then insert either a period or some sort of
signature, the sbbsecho id is appended quite often to the end of the
last line. If I do give at least one CR, it will appear as the last
line.
Can you elaborate or provide an example? That doesn't sound like normal behavior.
Re: Line stripping
By: Digital Man to Joe Delahaye on Wed Mar 01 2017 22:40:45
Is there a reason that empty lines at the end of a message are
stripped?
Because they serve no purpose.
If
I do not enter some CR and then insert either a period or some sort of
signature, the sbbsecho id is appended quite often to the end of the
last line. If I do give at least one CR, it will appear as the last
line.
Can you elaborate or provide an example? That doesn't sound like normal behavior.
Something like this.
this is a sample text. ...SBBSecho ver3.x
Or,
This is a sample text.
...SBBSecho.ver3.x
When I would like it to be thusly
Sample Text
...SBBSecho ver3.x
Have a nice day.
When I would like it to be thusly
Sample Text
...SBBSecho ver3.x
Have a nice day.
I'm not seeing that. Here's an example:
Have a nice day.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
Looks fine to me.
Hello Digital,
On Thu Mar 02 2017 08:10:58, Digital Man wrote to Joe Delahaye:
When I would like it to be thusly
Sample Text
...SBBSecho ver3.x
Have a nice day.
I'm not seeing that. Here's an example:
Have a nice day.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
Looks fine to me.
He wants a blank line between "Have a nice day." and "---SBBSecho 3.00-Win32", which is currently impossible unless you setup a signature.
He wants a blank line between "Have a nice day." and "---SBBSecho
3.00-Win32", which is currently impossible unless you setup a
signature.
But that's not what he said. He said the SBBSecho version was appended to the last line of text. <shrug>
Have a nice day. --- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
He wants a blank line between "Have a nice day." and "---SBBSecho
3.00-Win32", which is currently impossible unless you setup a
signature.
But that's not what he said. He said the SBBSecho version was appended
to the last line of text. <shrug>
On 2017 Mar 03 00:26:58, you wrote to Accession:
He wants a blank line between "Have a nice day." and "---SBBSecho
3.00-Win32", which is currently impossible unless you setup a
signature.
But that's not what he said. He said the SBBSecho version was appended to the last line of text. <shrug>
a lot of times his text ends up looking like this... i don't recall if it comes
in like that or if it gets wrapped like that when quoted, though...
Have a nice day. --- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
he was trying to say tear line but...
I'm not seeing that. Here's an example:
Have a nice day.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
Looks fine to me.
He wants a blank line between "Have a nice day." and "---SBBSecho
3.00-Win32", which is currently impossible unless you setup a
signature.
But that's not what he said. He said the SBBSecho version was appended to the last line of text. <shrug>
a lot of times his text ends up looking like this... i don't recall
if it comes in like that or if it gets wrapped like that when quoted,
though...
Have a nice day. --- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
he was trying to say tear line but...
If it's a quoting issue, there's really nothing to be done about that.
If it's a quoting issue, there's really nothing to be done about that.
leaving that last blank line before adding the tear and origin line might do the trick... or strip'em all out as is currently done and then add one blank line before the tear line is added ;) O:)
leaving that last blank line before adding the tear and origin line
might do the trick... or strip'em all out as is currently done and then
add one blank line before the tear line is added ;) O:)
But some people might *not* want a blank line before their tear line:
Hi,
On 2017-03-06 09:55:57, Digital Man wrote to mark lewis:
about: "Line stripping":
leaving that last blank line before adding the tear and origin line
might do the trick... or strip'em all out as is currently done and then
add one blank line before the tear line is added ;) O:)
But some people might *not* want a blank line before their tear line:
Why not just leave the linefeeds at the end of a message as the user put them there? If he didn't intend that, he shouldn't have typed them! ;)
Why not just leave the linefeeds at the end of a message as the user
put them there? If he didn't intend that, he shouldn't have typed
them! ;)
I think that decision goes way back (1990ish): new BBS users wouldn't know how to save the message in the editor they were using, so they would just hold down the enter key until they ran out of available lines or got a message telling them how to save and quit. These kinds of messages are pretty irritating in your new-msg-scan, so I decided that trailing white-space should be removed automatically in all saved messages. It's been that way ever since without complaint.
Hi,
On 2017-03-06 13:04:32, Digital Man wrote to Wilfred van Velzen:
about: "Re: Line stripping":
Why not just leave the linefeeds at the end of a message as the user
put them there? If he didn't intend that, he shouldn't have typed
them! ;)
I think that decision goes way back (1990ish): new BBS users wouldn't know how to save the message in the editor they were using, so they would just hold down the enter key until they ran out of available lines or got a message telling them how to save and quit. These kinds of messages are pretty irritating in your new-msg-scan, so I decided that trailing white-space should be removed automatically in all saved messages. It's been that way ever since without complaint.
Ok...
What about removing linefeeds, except 1?
So there will be 1 empty line
between the message text and the tearline, if the user entered 1 or more linefeeds? I think that would make messages more readable.
These kinds of messages are pretty irritating in your new-msg-scan,
so I decided that trailing white-space should be removed
automatically in all saved messages. It's been that way ever since
without complaint.
What about removing linefeeds, except 1? So there will be 1 empty line between the message text and the tearline, if the user entered 1 or more linefeeds? I think that would make messages more readable.
But some people might *not* want a blank line before their tear
line:
Why not just leave the linefeeds at the end of a message as the user put them there? If he didn't intend that, he shouldn't have typed them! ;)
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495937:14:41 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,955 |