@MSGID: 2:460/58 00000211
@PID: tg_BBS_v0.6.3
@CHRS: CP866 2
@TGUID: 1223717052
@REPLYTO 2:460/58 1223717052
@RealName: August Abolins 2:221/1.58
Ooops, I mistyped the the Subj command in the previous test.
Just testing (again) to see if Subj command works within body of a message *AFTER* the first (this) sentence.
The Subj command was *ABOVE* this sentence.
--- tg BBS v0.6.3
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58)
SEEN-BY: 124/5016 203/0 221/0 6 280/464 396/45 460/25 58 777 1124 5858 SEEN-BY: 5015/46 5054/30
@PATH: 460/58 280/464
Just testing (again) to see if Subj command works within body of a message *AFTER* the first (this) sentence.
The Subj command was *ABOVE* this sentence.
It worked! :)
It worked! :)
Neat, eh? I'm not sure if that is a bug or a feature. :D
Neat, eh? I'm not sure if that is a bug or a feature.
:D
I haven't decided yet either. ;)
Hello Stas Mishchenkov!
** On Sunday 07.02.21 - 08:12, Stas Mishchenkov wrote to August Abolins:
Neat, eh? I'm not sure if that is a bug or a feature.
:D
I haven't decided yet either. ;)
Of course I don't know your approach for detecting and
processing the bookended double command symbols around a
command, but why not start the parsing at the very beginning of
the message and only assume all of them are done only when you
detect the last pair (with the mandatory <CR>) and no start of
the next "--command:--" ?
That way, you can ignore a "--command:--" if it happens to
appear later in the body of the message.
Although I like the way "--command:--" works when the command is
CC, so that the carbon copies can all be listed at the end of a
message, when the command is SUBJ in the middle of the body,
that is not so good. :/ I have to re-write the Fidonet/
Telegram Guide so that the example usage of SUBJ doesn't
disappear! :D
--
../|ug
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 369 |
Nodes: | 16 (2 / 14) |
Uptime: | 87:52:16 |
Calls: | 7,896 |
Calls today: | 2 |
Files: | 12,968 |
Messages: | 5,792,266 |