Author Topic: @MCV: separate log for debugging  (Read 1938 times)

Offline 325xi

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1101
  • Karma: +0/-0
  • V1, V2, still V2...
@MCV: separate log for debugging
« on: September 26, 2009, 10:25:19 pm »
From my experience luup.log() isn't well suited for plugin debugging, as it sends everything into the general pile that gets hundreds of messages from everywhere. Working with that log file for while debugging is... doable, but time consuming and inconvenient.
Would it be possible to add a function luup.debug() or luup.debug(filename) exclusively for temporary debug prints that would send those prints into a separate file to ease the debugging process?