alexcorre / git-blame

Plugin for Atom Editor. Toggle git-blame annotations for the current file in the gutter.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Uncaught ReferenceError: path is not defined

JacobEvelyn opened this issue Β· comments

git-blame doesn't seem to be working for me any more. I get this error on any file I try:

Atom Version: 0.199.0
System: Mac OS X 10.9.5
Thrown From: git-blame package, v0.4.3

Stack Trace

Uncaught ReferenceError: path is not defined

At /Users/jacobevelyn/.atom/packages/git-blame/lib/git-blame.js:27

ReferenceError: path is not defined
    at atom-workspace.toggleBlame (/Users/jacobevelyn/.atom/packages/git-blame/lib/git-blame.js:27:60)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:238:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:519:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:354:22)
    at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:178:20)

Commands

  2x -0:09.5.0 core:close (div.release-notes.padded.pane-item.native-key-bindings)
     -0:00.4.0 git-blame:toggle (atom-text-editor.editor.is-focused)

Config

{
  "core": {
    "disabledPackages": [
      "autocomplete"
    ],
    "themes": [
      "atom-dark-ui",
      "monokai"
    ],
    "audioBeep": false
  },
  "git-blame": {}
}

Installed Packages

# User
autoclose-html, v0.16.0
git-blame, v0.4.3
language-haml, v0.20.0
monokai, v0.14.0
pretty-json, v0.3.3
webbox-color, v0.5.6

# Dev
No dev packages

πŸ‘

πŸ‘

πŸ‘

πŸ‘

πŸ‘

πŸ‘

(On Linux)

πŸ‘

πŸ‘

πŸ‘

πŸ‘

πŸ‘

πŸ‘

Just got this πŸ‘

πŸ‘

πŸ‘ git-blame has been broken for me for weeks :(

commented

Also seeing the error on Atom for Windows

I just published git-blame-plus with the fix. It's currently just a fork of git-blame. This is a temporary measure and I'll be happy to unpublish that package when bugs are fixed.

still does not open

On Thu, May 21, 2015 at 12:01 PM Adrian Lee notifications@github.com
wrote:

I just published git-blame-plus https://atom.io/packages/git-blame-plus
with the fix. It's currently just a fork of git-blame. This is a temporary
measure and I'll be happy to unpublish that package when bugs are fixed.

β€”
Reply to this email directly or view it on GitHub
#90 (comment).

There is another bug that is preventing the gutter from showing up. That issue is tracked in #89. Looking into it.

πŸ‘

πŸ‘

@adeitcher, with Atom v0.201.0 and git-blame-plus v0.4.6, I'm able to toggle the pane. Any chance you can test it out?

πŸ‘ Running the issue as well on OS X Yosemite 10.10.3.

πŸ‘
Linux (Elementary OS - Ubuntu 14.04 based)
Atom: 0.201.0
Git Blame version: 0.4.3

commented

v0.4.6 is not opening the gutter on Atom v0.201.0 / Windows 7.

The dev console reports a not-so-useful error when attempting to activate git-blame:

Unhandled promise rejection.
Error: Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings.

@peacechen, I think that issue has to do with #89.

Since reactionary-atom-fork isn't maintained by the core team anymore, i'm thinking maybe it's time to move git-blame out of react completely.

commented

πŸ‘

πŸ‘

πŸ‘

πŸ‘

πŸ‘

hi @adrianlee44 thanks for the PR i'll pull that in and release an update. i also plan to move off of react as its causing lots of people issues. anyone interested in helping out please reach out!

@adrianlee44 i appreciate you're getting the fixes out there, but i'd prefer if we can keep from releasing forks. Apologies for something not getting these fixes out sooner! looking at your PR now.

Merged in #91 and released v0.4.4

@alexcorre, thanks for merging the PR! I released the fork as a quick fix and have no intension of maintaining that or continue updating it if there is active development on this repo.