#JWST is often cited for its amazing work with galaxies, BUT LOOK AT IT DISSECTING UP THE CRAB NEBULA AND SHOWING US STAR GUTS FROM A 1000-YEAR OLD STELLAR DETONATION.
Wow! Look at the pulsar!
So epic that we can see this detail, the different structures, elements, velocities, energies, etc. from an event that Chinese and Japanese astronomers witnessed and documented 1000 years back.
We're connected through time with this event to them!
Gibt’s hier jemanden mit #TypeScript-Kenntnissen und Langeweile?
Mein #ConTeXt-Plugin für #Pulsar könnte deutlich besser sein (ich kann kein TS und pflege nur die Befehlsliste), es gibt einen Tree-Sitter-Parser, der integriert werden könnte, und das Plugin pdfjs-viewer müsste aktualisiert werden (Maintainy wird gesucht).
Hello @pulsaredit, I’d like to publish my plugin from https://codeberg.org/fiee/language-context-lmtx, but "ppm publish" gives only "Internal Server Error".
How can I debug this, or don’t you accept new plugins?
Documentation is lacking…
A week later than you’re accustomed to — but worth the wait! Pulsar 1.115.0 is available now!
Last month’s 1.114.0 release was full of fixes related to the recent migration to modern Tree-sitter. This month’s release is much smaller, but still dominated by Tree-sitter fixes affecting syntax highlighting, code folding, and indentation.
However, a secondary paper from a few days back, which also used JWST MIRI, found no evidence of the compact remnant in their data: https://arxiv.org/html/2402.14014v1
Almost 2 years ago I wrote a feature article looking at the evidence for this, so these new papers and findings are exciting!
A Valentine's release bursting with love, Pulsar 1.114.0 is available now!
Welcome to a brand new Pulsar release!This release features a lot of updates and fixes for our modern Tree-sitter implementation, an assorted bag of bug fixes and some new features to introduce, such as restoring compatibility with older Linux distributions and a new ppm command.
Last month was our biggest update to Pulsar we have had in quite a while, so in this blog we will be addressing some of the issues people have seen and what you can expect in terms of fixes and updates. We also have some big changes to the Pulsar Package Registry backend for a bunch of new filters and endpoints to the API.
In the beginning, Atom appeared. It created an API to make packages, allowed authors to use web APIs together with node.js and a special API that was used to communicate between the "main module" and the "browser part".
That last part split from Atom and became Electron. And for a while, the Atom development was tied to the Electron one meaning updates for one meant updates for the other.
Unfortunately that wasn't the case for a long time...
We’ve been telling a series of stories about all the different ways that Tree-sitter can improve the editing experience in Pulsar. Today’s story about symbols-view starts a bit slowly, but it’s got a great ending: the addition of a major new feature to Pulsar 1.113.
Unlucky for some, but not us. Our 13th release, Pulsar 1.113.0, is available now!
Welcome to the release of Pulsar 1.113.0, our first release of 2024. For this release we have enabled our modern Tree-sitter implementation by default, a new Tree-sitter PHP grammar, a huge update to our 'symbols-view' package, a bunch of bug fixes and an issue where we banish 😡 to the Netherrealm.
Welcome to our first community update of 2024! We have a reminder about our upcoming tree-sitter change, a resolution to our annoying website issues, a brand new PPR API endpoint so you can find packages by your favourite authors, a statement on our commitment to our long-term projects and a very special new year community spotlight.
Christmas has come early: Pulsar 1.112.0 is available now!
Welcome to our 12th regular release! It has been exactly a year since we put out our first tagged release and development continues. This month we have some new soft-wrapping options, some long overdue updates to PPM, improvements to our "GitHub" package, a new fuzzyMatcher API and our usual slew of bug fixes.
This month we have a big update on our plans to move to a new version of electron and what that might mean for our releases, some better error handling on our package website and our usual community spotlight to say thank you to those community members contributing to Pulsar's development!
This time we have a brand new API, a reduction in Pulsar's installed size, a fix for a really tricky and annoying bug, and some fixes from the community.
One annoying thing that software developers do is insist on writing in more than one language at once. Web developers are espeically obnoxious about this — routinely, for instance, putting CSS inside their HTML, or HTML inside their JavaScript, or CSS inside their HTML inside their JavaScript.
Code editors like Pulsar need to roll with this, so today we’ll talk about how the modern Tree-sitter system handles what we call injections.
This month we have a couple of really significant changes to how Pulsar works internally by creating a couple of new APIs that can be used throughout the application, a new package to help you run code directly within Pulsar and our usual community spotlight to say thank you to those community members contributing to Pulsar's development!
Hello! I was a big fan of Atom editor, and I’m very glad that Pulsar is continuing the legacy of Atom. My concern/question is, how in the heck do I install plugins? Specifically, plugins for python? And also, is there a terminal/space to run Python code like there is in VSCodium? In VSCodium, there’s a play button and code...
There are a couple of ways to install packages on Pulsar, we have a lot of it in the existing documentation (pulsar-edit.dev/docs/…/using-pulsar/#pulsar-packa…). The most common way is just to go to the package manager (Packages > Open Package Manager > Install (on left panel of the package manager)) where you can search for packages. Alternatively you can browse packages via the PPR (Pulsar Package Registry) at web.pulsar-edit.dev and use ppm to install (pulsar-edit.dev/docs/…/using-pulsar/#command-line).
As for the second part there are a few answers. You can install the x-terminal-reloaded if you simply want to get a terminal pane within Pulsar. However this won’t help run things like Python code “interactively” with a console, it is “just” a terminal. Unfortunately this is where I run out of knowledge a bit, I’ve never been one for trying to run code directly in the editor, I’ve always just used terminal commands, which seems to echo the experience of a lot of the Pulsar team. However I do know somebody a few people have asked this before so we might need to look into this, if for nothing other than to have a good answer.
There is a package called script-runner which sounds like it would do what you are after and another called script you might also like to have a look at.
Generally if you are after info about how to “make Pulsar do x” then you can probably find still relevant info using “make Atom do x” but obviously any links or apm commands won’t work and would need to reference the new Pulsar commands and links instead.
Oh wow! Just saw the new JWST image of the Crab Nebula! 😍😍😍
That wispy white stuff - that’s synchrotron radiation … emissions produced by electrons being accelerated around magnetic field lines at relativistic speeds by the 33 Hz pulsar at the centre.
Fun science:
Your microwave at home uses wavelengths of ~12-30cm range which cause water and other molecules to spin/vibrate thus heating them up.
Crab Pulsar's magnetic dipole radiation wavelength is about 10^7m & it heats up the surrounding nebula too!
Here we are with another Pulsar release, and this month we have quite a number of fixes and improvements. This time the focus has really been on bug fixes in order to improve the overall experience.
We have updates to PPM for newer toolchain compatibility, a new Autocomplete API, better error handling for a crash at launch with invalid config and a fix for PHP snippets.
How to install and run python plugins?
Hello! I was a big fan of Atom editor, and I’m very glad that Pulsar is continuing the legacy of Atom. My concern/question is, how in the heck do I install plugins? Specifically, plugins for python? And also, is there a terminal/space to run Python code like there is in VSCodium? In VSCodium, there’s a play button and code...