Environment Variables

Edit page on GitHub

MonoDevelop allows its behavior the be changed by several Environment variables. Some of those will come in handy when developing new MonoDevelop addins or when using a parallel MonoDevelop install.

Logging

  • MONODEVELOP_CONSOLE_LOG_LEVEL
    • Default value: UpToWarn
    • Possible Values
      • None
      • All
      • Fatal
      • Error
      • Warn
      • Debug
      • UpToFatal
      • UpToError
      • UpToWarn
      • UpToInfo
      • UpToDebug

This variable allows to change the level of details that are logged into the console.

  • MONODEVELOP_CONSOLE_LOG_USE_COLOUR
    • Default value: false
    • Possible Values
      • true
      • false

If true, messages logged in the console will be colored according to their severity.

  • MONODEVELOP_LOG_FILE
    • Default value: not set
    • Possible Value: a filename

If set, all log messages will be appended to the specified file.

  • MONODEVELOP_FILE_LOG_LEVEL
    • Default value: UpToInfo
    • Possible Values
      • See MONODEVELOP_CONSOLE_LOG_LEVEL

This variable allows to change the level of details that are logged using the file logger.

  • MONODEVELOP_LOGGING_PAD_LEVEL
    • Default value: UpToInfo
    • Possible Values
      • See MONODEVELOP_CONSOLE_LOG_LEVEL

This variable allows to change the level of details that are shown inside the “Internal Message Log” pad.

Additional Debug Information

  • MONODEVELOP_DISPATCH_DEBUG
    • Default value: not set
    • Possible Value: anything (doesn’t matter), eg: “true”

When this variable is set, exceptions generated inside a dispatched method will also log their stacktrace.

Other

  • MONO_ADDINS_REGISTRY
    • Default value: ~/.config/MonoDevelop

This variable allows to override the location of the addin repository. This is especially useful when working with a parallel MonoDevelop install, to completely seperate all addins so they can’t override each other.