TinTin++ Mud Client The TinTin++ message board

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
TinTin++ Mud Client

#config {log level} low; #config {log} plain;

 
Post new topic   Reply to topic    The TinTin++ message board Forum Index -> Bug Reports
View previous topic :: View next topic  
Author Message
Shaiith



Joined: 11 Jul 2009
Posts: 64

PostPosted: Tue Aug 04, 2009 7:14 am    Post subject: #config {log level} low; #config {log} plain; Reply with quote

Code:
#config {log level} low


ignores the setting of

Code:
#config {log} plain


I end up with a low level raw log file. (It's ignoring #config log plain basically) This seems like a bug to me. I'd like to have full content log files that don't contain ansi. What settings should I use.
Back to top
View user's profile Send private message
Shaiith



Joined: 11 Jul 2009
Posts: 64

PostPosted: Tue Aug 04, 2009 7:34 am    Post subject: Reply with quote

Based on a quick code read, why doesn't translate_telopts call logit? That way it'd gain the logic of #config og.
Back to top
View user's profile Send private message
Shaiith



Joined: 11 Jul 2009
Posts: 64

PostPosted: Sat Aug 15, 2009 9:13 am    Post subject: Reply with quote

Followup: Is there any way to achieve a complete (everything sent/received) log file without ansi?

Other than running tintin inside tintin that is. I can run a session inside tintin that just logs things and keep all my gags/what not in the enclosing session. However, that workaround seems like overkill when

Code:
#config {log level} low
#config {log} plain


would seem like the right way to do it. Instead that config setup ignores the value of #config log plain as #config {log level} low doesn't look at what type of log is requested, just assumes raw.
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3796

PostPosted: Sat Aug 15, 2009 9:29 am    Post subject: Reply with quote

Strings at that stage of input aren't NUL terminated, so tunneling it through logit() would result in a crash. Not to mention that logit doesn't strip telnet data.

What you'd probably want to do is:

Code:

#event {RECEIVED LINE} {#line logverbatim filename %1}
#event {RECEIVED INPUT} {#line log filename %0}
Back to top
View user's profile Send private message Send e-mail
stb



Joined: 16 Sep 2009
Posts: 3

PostPosted: Sat Sep 19, 2009 4:08 pm    Post subject: Reply with quote

The following preserves leading spaces in received lines

Code:

#event {RECEIVED LINE} {#line logverbatim filename {%1}}
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    The TinTin++ message board Forum Index -> Bug Reports All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Get TinTin++ Mud Client at SourceForge.net. Fast, secure and Free Open Source software downloads Get TinTin++ Mud Client at SourceForge.net. Fast, secure and Free Open Source software downloads
TinTin++ Homepage

Powered by phpBB © 2001, 2002 phpBB Group