Daeraxa Now • 100%
I saw the thumbnail and thought it was a pic of Joey Jordison from when he was in Murderdolls...
Daeraxa Now • 100%
So you can keep Kitty, just swap the shell you have it start by default (probably not a good idea to swap to this system-wide)
Daeraxa Now • 100%
But Kitty is 'just' the emulator right? It doesn't have a shell by itself.
Daeraxa Now • 100%
Willing to give this a go. My go-to for getting non-repo debs automatically has been deb-get which works well but seems susceptible to issues when changes in the software it lists causes it to break and whilst the fix itself is usually made pretty quickly, it seems to go long periods of time between PR merges and releases (which includes adding new software). If this is a viable replacement for it then i'd love to start using it.
Daeraxa Now • 100%
I knew somebody who used the more British version in a game - Hugh Jarse
Daeraxa Now • 100%
I've just moved to Thunderbird. I was never keen on the old design and found it rather clunky but the new UI I find much better.
I was using Mailspring but it has recently just refused to work on my device and I never even got a response on the community forums so I've just given up on it.
Daeraxa Now • 100%
Might fall foul of your 'not too heavy' politics requirement but I love my Private Eye subscription.
Daeraxa Now • 100%
My favourite cuisines I've had which were not common ones you can just find on any high street here were mostly found during the height of covid when I was working quite a way from home but the hotel's restaurant was closed so I had to order delivery each night.
- Nigerian: Ordered this a few times, peppersoup, moin moin, draw soup, eba amongst the things I had. Soon after a West African section opened in my local supermarket so I could at least get some of the main ingredients to cook some at home.
- Ethiopian: Amazing, not tried cooking any yet, some ingredients seem hard to come by
- Afghan: Had a bunch of times as there was a restaurant in my town
- Sri Lankan: Love it, superficially similar to Indian food but I was surprised just how different it was and has become one of my favourites that I cook at home with regularity.
Daeraxa Now • 100%
Mandatory breath tests at the gate with additional fees to pay for every 0.01% over a certain limit (but if you pay up front you can get as pissed as you like)
Daeraxa Now • 100%
Just straight up scranning some homemade kimchi
Daeraxa Now • 100%
Pulsar is a fork of Atom under active development. We don't publish a flatpak (yet) but there is a community maintained flatpak for it.
Otherwise if you want to look at something else I'd give Lite XL, Lapce or even Zed (it has now been open sourced and looks like it has a flatpak available) a look as interesting alternatives.
github.com
While a smaller release this time around, v1.119.0 still manages to pack a punch. For macOS, we've gone to great lengths to ensure Pulsar should build just fine on macOS 13+, while our Linux users get greater compatibility for DevTools on various platforms. For our programmers, there's been more of the constant incremental improvements to various languages' built-in syntax highlighting and code folding this time around, with a focus on PHP, Python, Javascript, Typescript, Shell script, and C. As always thanks a ton to all of those that support the project and keep it moving forward, we appreciate you all, and look forward to seeing you amongst the stars.
Daeraxa Now • 100%
I'm going to say Space Beast Terror Fright. I really enjoyed it, it is basically a kind of Space Hulk type game - dark and spooky spaceship filled with unknown horrors you have to fight through and survive with friends. Actively developed too.
Daeraxa Now • 100%
Nope, I had Gearheads on my old Windows 95 PC, absolutely loved it. Used to keep spamming the laser robot and bombs.
Daeraxa Now • 100%
What about something like navi - https://github.com/denisidoro/navi. Basically an interactive cheat sheet that has commands pre-loaded (or that you can make yourself).
Daeraxa Now • 100%
Watch this space for the full history, I'm literally putting the final touches on a blog post that will go into details of how Atom started then how it became Pulsar as a little celebration after we hit 3k stars.
Daeraxa Now • 100%
Just to clarify, the Pulsar devs aren't ex-Atom devs. Some of the team are from atom-community but none of the core Pulsar team were part of the official Atom team.
github.com
Get your grills ready, Pulsar v1.118.0 is cooking with gas! With lots of love to syntax highlighting, along with a zesty sprinkling of features and fixes. We've got Tree-sitter fixes and improvements from query tests, better documentation of our Tree-sitter usage, an updated PHP parser, and loads of improvements to Clojure, there should be a little something for everyone. But of course feel free to dive into the changelog for further details.
github.com
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.
github.com
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. Outside of that, we have some big changes to the Pulsar Package Registry backend that give (and document) a bunch of new filters and endpoints to the API, as well as a reminder for \@maurício szabo's blog post detailing our biggest hurdle: the road to modern versions of Electron.
In the beginning, Atom appeared. It created an API to make packages, but together with this API, it also allowed authors to use web APIs together with node.js packages, modules (including "native modules" - more on that later) and, finally, a special API that was used to communicate between the "main module" and the "browser part". That last part, eventually, split from Atom and became Electron. And for a while, the Atom development was tied to the Electron one, meaning that an update on Atom usually meant an update on Electron, and vice-versa. 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.
github.com
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.
github.com
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!
github.com
Welcome to a new Pulsar regular release! 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!
Last time we looked at Tree-sitter’s query system and showed how it can be used to make a syntax highlighting engine in Pulsar. But syntax highlighting is simply the most visible of the various tasks that a language package performs. Today we’ll look at two other systems — indentation hinting and code folding — and I’ll explain how queries can be used to support each one.
github.com
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.
Last time I laid out the case for why we chose to embrace TextMate-style scope names, even in newer Tree-sitter grammars. I set a difficult challenge for Pulsar: make it so that a Tree-sitter grammar can do anything a TextMate grammar can do. Today, I'd like to show you the specific problems that we had to solve in order to pull that off.
This month we announce our new "Pulsar Cooperative" initiative, showcase work being done to modernize the PPM codebase, introduce the new Shields.io badges for the Pulsar Package Repository, show off the new Pulsar integration in GitHub Desktop and talk about an issue we had with signing our macOS binaries.
In the last post, I tried to explain why the new Tree-sitter integration was worth writing about in the first place: because we needed to integrate it into a system defined by TextMate grammars, and we had to solve some challenging problems along the way. Today I’ll try to illustrate what that system looks like and why it’s important.
The last few releases of Pulsar have been bragging about a feature that arguably isn’t even new: our experimental “modern” Tree-sitter implementation. You might’ve read that phrase a few times now without fully understanding what it means, and an explanation is long overdue. This is the first of a series of articles about Pulsar’s ongoing project to migrate its Tree-sitter implementation to a more modern version. Read this first installment now on the [Pulsar Blog](https://pulsar-edit.dev/blog/20230925-savetheclocktower-modern-tree-sitter-part-1.html)