Started by Lizzie, February 01, 2019, 11:47:47 PM
Quote from: Vyoko on February 02, 2019, 11:22:33 AMOr just get into the relatively easy habit of hitting the "Log" button on the Mushclient toolbar when you start your session. You are then prompted to save to a specified file (or you can choose to append the the log to an existing file).You are then free to grep your text files at a later date for whatever it is you are looking for.After a few days of focusing on doing it, it will become automatic, and takes less than 30 seconds.
Quote from: KittenLicks on February 02, 2019, 02:07:26 AMYou could do what I do, and just write everything to one file, then delete it every few days, when it becomes too big to open. I'm no Mushclient expert, but what I'd do is have your mushclient log to a file, say, templog.txt, then add 'quit' as a trigger to rename that file. Eg. "quit mudsex_session_69" renames "templog.txt" to "mudsex_session_69.txt".That should be as easy as telling mushclient to log to templog.txt, then adding a trigger with:Code Select ExpandCloseLog()os.rename('templog.txt','%1.html')Send('quit')If it has to work when you close mushclient, then it becomes a bit more complicated. I guess you could manually just rename templog.txt if you closed mushclient.
Quote from: cnemus on February 02, 2019, 12:58:43 PMSorry to double post, but using the 'automatically log to' function automatically starts logging every session. You don't ever have to mess with the files unless you want to delete or rename them. You could use this in conjunction with the script trigger above to rename those 'special' sessions.
Page created in 0.045 seconds with 19 queries.