Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught ReferenceError: range is not defined #969

Open
5 tasks done
lwlsn opened this issue Apr 4, 2024 · 4 comments
Open
5 tasks done

Uncaught ReferenceError: range is not defined #969

lwlsn opened this issue Apr 4, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@lwlsn
Copy link

lwlsn commented Apr 4, 2024

Thanks in advance for your bug report!

  • Have you reproduced issue in safe mode?
  • Have you used the debugging guide to try to resolve the issue?
  • Have you checked our FAQs to make sure your question isn't answered there?
  • Have you checked to make sure your issue does not already exist?
  • Have you checked you are on the latest release of Pulsar?

What happened?

Uncaught ReferenceError: range is not defined error is occurring, when running a package (https://github.com/hydra-synth/atom-hydra) that used to function correctly on previous versions of Pulsar

This is the eval-code is keymapped and producing the error

evalCode() {
let editor
if (editor = atom.workspace.getActiveTextEditor()) {
range = {
start: { row: 0, column: 0 },
end: { row: editor.getLastScreenRow() + 1, column: 0 }
}
this.evalFlash(range);
this._eval(editor.getText());
}
}

Pulsar version

1.115.0

Which OS does this happen on?

🍎 macOS

OS details

Ventura 13.15

Which CPU architecture are you running this on?

Apple M1/M2

What steps are needed to reproduce this?

  1. Install atom-hydra package
  2. Toggle package on
  3. Eval any line of code in pulsar editor

Additional Information:

n/a

@lwlsn lwlsn added the bug Something isn't working label Apr 4, 2024
@savetheclocktower
Copy link
Sponsor Contributor

Did you follow the instructions in the package's README about installation on Pulsar?

@lwlsn
Copy link
Author

lwlsn commented Apr 7, 2024

yes

@savetheclocktower
Copy link
Sponsor Contributor

I can only say that I followed those directions nearly exactly (used npm install instead of ppm install) and the package appeared to work for me. Might be worth trying it again.

Since the maintainer cared enough to update the README to explain how the package can be installed on Pulsar, maybe they'd be willing to publish an updated version to the package repository.

@lwlsn
Copy link
Author

lwlsn commented Apr 14, 2024

Sounds like it might be package specific- I've opened up an issue there- thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants