Uncaught TypeError: Cannot read property 'save' of undefined

[cadeocadu]

[Enter steps to reproduce:]

1. ...
2. ...

Atom: 1.21.0 x64
Electron: 1.6.9
OS: elementary OS
Thrown From: language-nxc package 3.6.1

Stack Trace

Uncaught TypeError: Cannot read property 'save' of undefined

At /home/labrede/.atom/packages/language-nxc/lib/main.coffee:42

TypeError: Cannot read property 'save' of undefined
    at Object.nbc (/packages/language-nxc/lib/main.coffee:42:41)
    at Object.upload (/packages/language-nxc/lib/main.coffee:28:6)
    at /packages/language-nxc/lib/main.coffee:22:25)
    at CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/src/command-registry.js:381:36)
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:621:22)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:412:28)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/usr/share/atom/resources/app/src/window-event-handler.js:100:42)
    at HTMLDocument.<anonymous> (/usr/share/atom/resources/app/src/window-event-handler.js:3:65)

Commands

  2x -8:02.3.0 core:backspace (input.hidden-input)
     -7:58.5.0 core:move-left (input.hidden-input)
     -7:57.8.0 editor:newline (input.hidden-input)
     -7:56.7.0 core:move-up (input.hidden-input)
     -1:48.2.0 nxc:upload (div.tool-panel.tree-view)
     -1:07.3.0 package-generator:generate-package (a.)
     -1:01.8.0 dev-live-reload:reload-all (a.)
     -0:47 window:toggle-menu-bar (a.)
  2x -0:44.3.0 window:toggle-full-screen (a.)
  2x -0:19.5.0 nxc:upload (input.hidden-input)

Non-Core Packages

language-nxc 3.6.1 

[nloomans]

Thanks for reporting the issue! But I'm having trouble reproducing this error. I was, hower, able to reproduce this when opening a non-savable item (for example, the settings menu) and attempting to compile.

That is indeed a bug and should be handled properly, this will be fixed in the next release (probably within one day).

Was this error indeed triggered while in a non-savable item?