• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers

Best practices for LrLogger

Participant ,
Aug 19, 2022 Aug 19, 2022

Copy link to clipboard


I've been surfing around looking for clues about config.lua and also running experiments and I'm stumped.

What I assume LR is trying to provide is a way to have, for example, debug prints (log messages) in your plugin that, when shipped, is turned off but the end user can put something config.lua to enable the debug output go to a file and then that file sent to the plugin implementor.  But, when I play with all the various options and APIs, I end up where if the plugin has foo.enable('logfile') the output will go to the log file and if it does not have it, the output goes nowhere.  To rephrase, I've yet to discover how config.lua can enable or disable the logger's output.


This isn't horribly important but I'm hoping to write some general purpose routines and publish them in a git repo.  I'm trying to make them useful to others beside myself.







Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation