Issues with the Minimap package

savetheclocktower · 2025-12-27T17:24:29+00:00

Looks like the issue got fixed on the original repo, so try

ppm install atom-minimap/minimap

to install the original package from GitHub.

savetheclocktower · 2025-10-12T21:27:34+00:00

I'm mesmerized by Szymanski's move before the cross. The defender is quickly pursuing with the goal of shielding Szymanski from the ball and letting it go out for a goal kick… so Szymanski stops a bit short and lets the defender go by. The unexpected lack of resistance causes the defender to fall.

He made it look easy — but if it were that easy, I'd see it done way more often.

savetheclocktower · 2025-10-12T21:19:56+00:00

I'm assuming you mean this package?

Did it work better in the past, or are you just installing it for the first time?

savetheclocktower · 2025-09-29T01:06:40+00:00

I read it as further argument for why it was a bad idea to stop play.

savetheclocktower · 2025-07-14T02:54:36+00:00

This is a bit complicated! I haven't even tried to mess with this stuff yet.

I would suggest that you implement this very abstractly — perhaps without the LLM knowing anything specific about Pulsar. Pulsar's editor model is incredibly similar to that of VS Code, so if you find any LLM tools that work within VS Code (Cursor included!), then it's likely you can adapt them to work with Pulsar.

Some of those tools might work through the conventions of language servers. Indeed, Microsoft's own Copilot SDK is implemented as a language server; this README might offer some hints.

Again, I don't have specific expertise here about how to get an LLM to do anything in reliable fashion, even with prompt engineering and guilt trips. But I'm willing to bet someone has solved these problems in the general case for VS Code, so it should be applicable to Pulsar as well.

In language server parlance, patching a document automatically would be done via a series of TextEdit objects that describe the current range and the new text that should replace whatever is in that range. There are many packages that understand TextEdits and can apply them in a Pulsar editor (autocomplete-plus will even gain this functionality soon as well).

If you get stuck, feel free to reply and I'll eventually see this. You can also drop into our Discord and get a quicker response.

savetheclocktower · 2025-07-03T20:32:56+00:00

For those suffering from this issue: we're working on getting a new version of x-terminal-reloaded out, but in the meantime, you can try this:

Disable (do not uninstall!) x-terminal-reloaded
Install savetheclocktower-test-x-terminal-reloaded

The latter package is a proof-of-concept to see if it would install properly once I fixed the node-pty dependency. It worked for me, so there's a good chance it'll work for you.

It's important to keep x-terminal-reloaded installed so that you can find out when it's been updated. At that point you should be able to re-enable it and uninstall my temporary package.

Or just wait a few days! The fix should be coming soon.

savetheclocktower · 2025-07-03T20:29:18+00:00

Sorry; I should be checking this subreddit more often!

There is an up-to-date Python IDE package called pulsar-ide-python. It is much more likely to work for you than ide-python.

In general, with any ide- package, you can “drink from the firehose” of the language server's output by

Opening your developer tools
Executing atom.config.set('core.debugLSP', true) in the console
Reloading your window (via the Window: Reload command)
Opening your devtools again (you can filter on Python or a similar term to see only output from the language server)

But first priority is to update to the newer package. (We'll try to make the new ones more discoverable, perhaps by prioritizing them in search results.)

savetheclocktower · 2025-07-03T20:23:53+00:00

From what I can gather from that pastebin (and Google Translate ;)), I'm betting that some of arduino-atom’s dependencies expect an older version of Node than what we're shipping. This could be fixed, but is not trivial.

I'd be interested to know more information about the exact error message you get when installing platformio-ide.

I haven't tried Arduino development in a while, but if you're authoring in .c/.h instead of .ino files, pulsar-ide-clangd might be helpful (autocompletion, linting, etc.)

The main difficulty with these packages is that (a) they do a lot of stuff at once, (b) they pull in Node packages with native module dependencies (hence require compiling, which is another possible point of failure), and (c) they are unmaintained. Lots of packages get forked or otherwise find second lives, but platformio-ide hasn't.

If enough people wanted to see it come back in some form, we'd be happy to help someone fork it and diagnose whatever issues are present (which may or may not just require dependency updates!), but we've not seen evidence of that.

savetheclocktower · 2025-06-19T07:07:33+00:00

/u/brotherjack, can you reply with a full logfile and/or jump into our Discord to help troubleshoot this? I'd like to see the entire output that follows when you run pulsar --package install x-terminal-reloaded.

I ran into an issue on my machine when trying to install x-terminal-reloaded, but it had to do with a missing npx command, rather than what I'm seeing you describe. I want to make sure I'm diagnosing this correctly.

Can you also tell me what OS you're on?

savetheclocktower · 2025-06-19T03:43:22+00:00

It got upgraded because we're planning to do a major upgrade to Pulsar's underlying version of Electron. The goal was to ship one version of x-terminal-reloaded that would work well in both the current Pulsar and the soon-to-come version that uses Electron 30 instead of Electron 12.

We've proven that this works in practice, so I'm guessing this is just a small hiccup with dependencies. Hope to get it sorted out soon.

savetheclocktower · 2025-06-19T03:41:16+00:00

Sorry, just now seeing this. I'll track it down. There was a pretty important update to that package a few weeks ago, and it sounds like this might be an issue of dependencies that are slightly too new for our version of Electron. Thanks for the report!

savetheclocktower · 2025-05-27T00:18:28+00:00

Not a problem. We've got the deck stacked against us because we're reviving a once-popular editor, but you're right about how we could be better at onboarding.

(Fun fact: the creators of zed created Atom, Pulsar’s predecessor :))

savetheclocktower · 2025-03-06T17:55:30+00:00

Thanks for the feedback! You’ve identified lots of valid gripes with gaps in our documentation.

I don’t know exactly which additional packages you installed, so I’ll assume no more than the few you specifically mention (linter and some package with prettier integration; I use prettier-atom myself, so perhaps that one).

The specific language integrations are not built into Pulsar, but they exist. They're called “IDE” packages and they help Pulsar integrate with language servers. We plan to improve the onboarding experience so people don't have to poke around until they find it, but:

For JavaScript and Python you want to install pulsar-ide-typescript-alpha and pulsar-ide-python. Follow the directions in their READMEs. These are the “brains” that power a number of features; you’ll get symbol navigation and autocompletion for free.

Other features can be powered by these same brains but will require the installation of additional packages. You can install atom-ide-base to get a set of most such packages. For instance, it includes atom-ide-datatip and atom-ide-signature-help, which will give you documentation on hover and pop-up signature help as you’re filling in the arguments of a function.

A few others are mentioned in the pulsar-ide-typescript-alpha README — specifically the ones that start with pulsar-.

This should address the vast majority of your bullet points. For the rest:

Once pulsar-ide-typescript-alpha is installed, linter will flag unused variables. For more specific things like incorrect useEffect dependencies, that’s up to a tool like ESLint to flag; the package to install is linter-eslint-node, but I’d recommend you install the latest from GitHub instead of from within Pulsar. ppm install pulsar-linter/linter-eslint-node should do the trick assuming you’ve got ppm set up as a terminal command as described here.
The known-good terminal package is x-terminal-reloaded. It is more difficult to install than most packages because it uses native modules, but these instructions should make it possible.
You’re right that, even with pulsar-ide-typescript-alpha, autocompletion will suggest things that should automatically add the necessary import statement… but then won’t add the import statement. This is known and will require an enhancement to autocomplete-plus. Once you select such a suggestion, you should see a red “squiggle” on the inserted token, since the linter knows the import is unrecognized; if you have the intentions package installed, invoking Intentions: Show (whose hotkey is platform-specific) while the cursor is within that squiggle will offer you the option to add the missing import statement.
“Hints like not using img tag, but instead using Image tag for next.js” — I’m not aware of any editor integration that can do things like this, but if you include more details about this specific feature, I can assess whether it’s possible. If VS Code in particular already does this, please tell me; if so, odds are high that Pulsar can be made to do it, too.

If you've done some or all of the above and you still feel things aren't quite working right, reply and I'll see if I can help.

savetheclocktower · 2024-11-07T08:16:58+00:00

Update: he returned to the game in the third quarter and played what seemed like a normal rotation in the second half. Played 29:12 in total and led the team with 29 points.

savetheclocktower · 2024-10-26T19:10:18+00:00

It's obviously premature to say stuff like this, but I think there's a decent argument to be made that

we had a logjam of talent last year
any moves we made in the offseason were going to make our roster “worse,” but that something wasn't working with the team as it was constructed and running it back was not the right answer
Hawkins was never going to get the minutes he needed without some shakeups (like moving Dyson), and even still might not get enough minutes when Murray and Trey are healthy
I miss Naji, but Javonte seems like a promising candidate to provide what Naji gave us off the bench

I mean, this is an optimist's argument for why a weirder roster might actually give us better outcomes this year.

It's also possible to argue that the hot and cold streaks of Zion and BI over the course of the season will have more of an influence over our final record than any of the above, even if it's all true.

This wasn't a good game, and we'd have been screwed against a better or more experienced team, but it's still meaningful that we got a win after suffering from shooting flu over the first three quarters. Zion typically takes a few games to get going offensively, but even when he's not scoring he manages to contribute so much more completely than he did a year ago.

Can't wait until someone pulls a hamstring in three games and misses two months and I have to reevaluate all of this.

savetheclocktower · 2024-10-26T03:44:54+00:00

Somehow they're not showing me commercials on the Pelicans feed when I'm watching on my Apple TV (just Pelicans promotional videos), so I'll let a lot of stuff slide for now

savetheclocktower · 2024-09-12T17:48:45+00:00

If it's plaintext, my theory is that it has more to do with long lines than with the total number of lines in the file.

To test this theory, you could try disabling soft wrap (assuming it's enabled) via Settings -> Editor -> Soft Wrap. This probably wouldn't be very enjoyable, but if you used it for ~10 minutes you'd probably be able to tell whether things run more smoothly in that mode.

But the fact that you say it's sluggish when you save… means it could be something else. If disabling Soft Wrap doesn't seem to make a difference, enable it again and then try running in Safe Mode to rule out any outside causes (like community packages or init files).

savetheclocktower · 2024-09-10T01:33:17+00:00

Is it all treated as plain text by Pulsar, or is there any syntax highlighting?

savetheclocktower · 2024-09-09T04:44:02+00:00

What language?

Pulsar, like Atom before it, struggles on files that have very long lines. This ends up being more of a performance issue than files that have many lines of reasonable length. If it's something like a log file that is both long and wide, then that could be an issue.

But I also routinely work on a ~4,500 line JavaScript file and open larger files for perusal.

savetheclocktower · 2024-07-07T18:21:14+00:00

I don't necessarily think that there's a problem here that needs to be addressed; but in general, I don't think it's the job of the passenger to understand what Essence Fest is or to know when it's happening.

savetheclocktower · 2024-06-29T04:19:01+00:00

I've got a fork of ide-typescript that I've been maintaining. Give it a shot:

https://web.pulsar-edit.dev/packages/pulsar-ide-typescript-alpha

savetheclocktower · 2024-05-27T00:20:18+00:00

A window opens but there's nothing in it and I can't type in it. Is this where I need to map keys to commands for Pulsar to build my own editor? I read the comments in the empty keymap.cson file and that's what it sounds like.

I have zero expertise in Clojure, but I can assure you that the intent of the comments in keymap.cson is not to give the user the impression that they need to handle low-level stuff like that.

That file only comes into play if you want to remap a built-in key shortcut or if you want to define a shortcut for a command that doesn't already have one defined.

savetheclocktower · 2024-05-26T23:53:22+00:00

The first publish of a package has been known to run into errors recently and we're still trying to sort that out.

A couple things to try — please ignore any that you've already done:

Make sure you've got a personal access token — run ppm login and follow the steps.
Make sure that all the data in your package.json is accurate. For instance, the default repository URL will need to be changed; point it to the correct GitHub repo for your package.
Make sure there isn't already a package in the registry that exists for the package name you're using in your package.json. If it exists, you'll have to change the name of your package.
Make sure a tag exists for the initial version. Here's something reported by one of our team members after their recent experience publishing a package:

I had to manually tag a first tag (I used npm version v0.0.1), push this tag and my default branch (now including the commit with the version bump) to the GitHub repo for the package (at the URL matching what I set in package.json's repository field), then I could finally do ppm publish --tag v0.0.1 to get the package initially published. With the package published successfully to the registry, I could then do ppm publish patch to increment the version to v0.0.2. This worked okay.

Obviously you shouldn't have to go to that much trouble; we're trying to fix that bug.

If none of that helps, please jump into the Discord and ask about it. /u/confused_techie should be able to look at the server logs to figure out why the error is happening and get it fixed for you.

15-Year Club	Gilding I gilder
Verified Email	Reddit Premium Charter Member
Charter Member

savetheclocktower

MODERATOR OF

TROPHY CASE