| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | new! improved! |
Hi Gerald.
22-Dec-03 11:57:24, Gerald Miller wrote to Jasen Betts
GM> Hello Jasen,
I'm going away for a few days so this is just a quiuck reply
GM> :: what the head of each log line looks like
GM> :: set LOGHEAD=%%_TIME%% %{at}UPPER[%{at}NAME[%0]]:
GM> :: [changed by GBM - Monday, December 22, 2003]<<
GM> set LOGHEAD=%%_TIME%%ÿ
GM> :: NOTE: There is a "hard space" character (Alt 255 - on
my system) at
GM> the
GM>: end of %%_TIME%%
Mark's the expert on the format...
I wonder if there'a a way to do loghead setting in an option...
(hmm, seems expressions don't work in the data file)
I don't like the use of non-ascii characters
I don't like the hard space, manbe instead use %%{at}CHAR[32]
(with two % signs) or use ` ` (a space with back-quotes)
GM> The above change eliminates some redundancy within the log file:
mark was pretty adamamt that the format was important.
GM> :: if "%1"=="HELP" .or.
"/HELP"=="%1" .or. "%1"=="-HELP" %=
GM> :: [changed by GBM - Monday, December 22, 2003]
GM> if "%{at}UPPER[%1]" =="HELP" .or.
"/HELP"=="%{at}UPPER[%1]" .or. %=
GM> "%{at}UPPER[%1]"=="-HELP" %=
but what does that change do?
GM> :: echo ! %LOGHEEAD% Nothing to do [...]
GM> echo ! %LOGHEAD% Nothing to do [...]
oops!
GM> ---------- Mon 22 Dec, SCHED Process
oops no year! I missed that too. i prefer
%{at}SUBSTR[%{at}YEAR[%_DATE],1,-2]
for debugging reeasons.
-=> Bye <=-
---
* Origin: Keyboard not connected, press to continue. (3:640/1042)SEEN-BY: 633/267 270 @PATH: 640/1042 531 954 774/605 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.