- DocumentID: fileref
  Title: >-
    FileRef
  CategoryID: user-guide
  Summary: >-
    How to track what code was loaded and from where
  Description: |-
    Every function, event, autocompletion and even variable is stored with which
    file it was sourced, when it was loaded and what module it was loaded from.
    This makes it trivial to identify buggy 3rd party code, malicious libraries, or
    even just bugs in your own profiles and/or modules.
    
    ```
    » runtime: --functions -> [[ /agent/FileRef/ ]]
    {
        "Column": 5,
        "Line": 5,
        "Source": {
            "DateTime": "2021-03-28T09:10:53.572197+01:00",
            "Filename": "/home/lmorg/.murex_modules/murex-dev/murex-dev.mx",
            "Module": "murex-dev/murex-dev"
        }
    }

    » runtime --globals -> [[ /DEVOPSBIN/FileRef ]]
    {
        "Column": 1,
        "Line": 0,
        "Source": {
            "DateTime": "2021-03-28T09:10:53.541952+01:00",
            "Filename": "/home/lmorg/.murex_modules/devops/global.mx",
            "Module": "devops/global"
        }
    }
    ```

    {{ include "gen/includes/fileref-module-strings.inc.md" }}
  Synonyms:
    - fileref
    - FileRef
  Related:
  - commands/murex-package
  - modules
  - commands/runtime
  - commands/element
  - commands/source
