Search
306 results for “YesJustWolf”
-
Because of the editors I use ( #NeoVim and playing with #HelixEditor ), I use and like a specific change to my keyboard. The CapsLock key is instead Escape when you tap it, or Control when you hold it with any other key.
It’s easy to make my #KinesisAdvantage360 do this. So it’s frustrating when I have to use the built-in keyboard on my Windows laptop. But I found this:
-
Published my port of the Alabaster theme family for Helix.
Alabaster is a minimal syntax highlighting approach by Nikita Prokopov (tonsky) - only 4 semantic colors: strings, constants, comments, and definitions. Everything else stays plain text because code structure is already clear from formatting.
I've ported all 6 variants (light/dark × standard/BG/mono) from the original Sublime theme (staying as close as possible to the original). Also submitted a PR to ship these with Helix upstream!
Original theme: https://github.com/tonsky/sublime-scheme-alabaster
Read tonsky's essay: https://tonsky.me/blog/syntax-highlighting/
My port: https://github.com/wolf/alabaster-for-helixI tried to duplicate the original exactly, however Helix has multiple selections so I made the colors distinct between "selection" and "primary-selection".
#HelixEditor #Helix #Alabaster #MinimalDesign #SyntaxHighlighting #TextEditor #Rust
-
Published my port of the Alabaster theme family for Helix.
Alabaster is a minimal syntax highlighting approach by Nikita Prokopov (tonsky) - only 4 semantic colors: strings, constants, comments, and definitions. Everything else stays plain text because code structure is already clear from formatting.
I've ported all 6 variants (light/dark × standard/BG/mono) from the original Sublime theme (staying as close as possible to the original). Also submitted a PR to ship these with Helix upstream!
Original theme: https://github.com/tonsky/sublime-scheme-alabaster
Read tonsky's essay: https://tonsky.me/blog/syntax-highlighting/
My port: https://github.com/wolf/alabaster-for-helixI tried to duplicate the original exactly, however Helix has multiple selections so I made the colors distinct between "selection" and "primary-selection".
#HelixEditor #Helix #Alabaster #MinimalDesign #SyntaxHighlighting #TextEditor #Rust
-
Published my port of the Alabaster theme family for Helix.
Alabaster is a minimal syntax highlighting approach by Nikita Prokopov (tonsky) - only 4 semantic colors: strings, constants, comments, and definitions. Everything else stays plain text because code structure is already clear from formatting.
I've ported all 6 variants (light/dark × standard/BG/mono) from the original Sublime theme (staying as close as possible to the original). Also submitted a PR to ship these with Helix upstream!
Original theme: https://github.com/tonsky/sublime-scheme-alabaster
Read tonsky's essay: https://tonsky.me/blog/syntax-highlighting/
My port: https://github.com/wolf/alabaster-for-helixI tried to duplicate the original exactly, however Helix has multiple selections so I made the colors distinct between "selection" and "primary-selection".
#HelixEditor #Helix #Alabaster #MinimalDesign #SyntaxHighlighting #TextEditor #Rust
-
Published my port of the Alabaster theme family for Helix.
Alabaster is a minimal syntax highlighting approach by Nikita Prokopov (tonsky) - only 4 semantic colors: strings, constants, comments, and definitions. Everything else stays plain text because code structure is already clear from formatting.
I've ported all 6 variants (light/dark × standard/BG/mono) from the original Sublime theme (staying as close as possible to the original). Also submitted a PR to ship these with Helix upstream!
Original theme: https://github.com/tonsky/sublime-scheme-alabaster
Read tonsky's essay: https://tonsky.me/blog/syntax-highlighting/
My port: https://github.com/wolf/alabaster-for-helixI tried to duplicate the original exactly, however Helix has multiple selections so I made the colors distinct between "selection" and "primary-selection".
#HelixEditor #Helix #Alabaster #MinimalDesign #SyntaxHighlighting #TextEditor #Rust
-
I love #tombihn bags. I’ve been buying them since 1998 (I think). I started with messenger bags. I’ve got the ID and the Super Ego. I’ve got a zillion backpacks and travel bags. My messenger bags are still as good as new. All his bags are unbelievable quality. But the phone pockets on the ID, my favorite, are too small. I find myself buying a #timbuk2 classic messenger. Please Tom: make new messenger bags that can hold a 16” MacBook Pro.
-
It seems like my #Pyrefly problem isn’t related to my #AdventOfCode project. Before pyrefly, I could rename a symbol throughout the project. With pyrefly, I can’t. More investigation needed.
-
It seems like my #Pyrefly problem isn’t related to my #AdventOfCode project. Before pyrefly, I could rename a symbol throughout the project. With pyrefly, I can’t. More investigation needed.
-
It seems like my #Pyrefly problem isn’t related to my #AdventOfCode project. Before pyrefly, I could rename a symbol throughout the project. With pyrefly, I can’t. More investigation needed.
-
Working on #AdventOfCode. My plan was to solve each day in both #Python and #RustLang. I thought I would be further by now. Yes, my Python answer to day 1 solves both parts, but I'm trying to be exemplary: good names, docstrings, comments-where-needed, tests, project structure, all the things.
For some reason, #HelixEditor keeps complaining about the #LSP (using both #Pyrefly and #Ruff, as usual). I'm concerned I haven't set things up right somehow, but I don't yet see where I've gone wrong.
Once this is working, further days will be easy. At least ... I hope!
-
Working on #AdventOfCode. My plan was to solve each day in both #Python and #RustLang. I thought I would be further by now. Yes, my Python answer to day 1 solves both parts, but I'm trying to be exemplary: good names, docstrings, comments-where-needed, tests, project structure, all the things.
For some reason, #HelixEditor keeps complaining about the #LSP (using both #Pyrefly and #Ruff, as usual). I'm concerned I haven't set things up right somehow, but I don't yet see where I've gone wrong.
Once this is working, further days will be easy. At least ... I hope!
-
Working on #AdventOfCode. My plan was to solve each day in both #Python and #RustLang. I thought I would be further by now. Yes, my Python answer to day 1 solves both parts, but I'm trying to be exemplary: good names, docstrings, comments-where-needed, tests, project structure, all the things.
For some reason, #HelixEditor keeps complaining about the #LSP (using both #Pyrefly and #Ruff, as usual). I'm concerned I haven't set things up right somehow, but I don't yet see where I've gone wrong.
Once this is working, further days will be easy. At least ... I hope!
-
Working on #AdventOfCode. My plan was to solve each day in both #Python and #RustLang. I thought I would be further by now. Yes, my Python answer to day 1 solves both parts, but I'm trying to be exemplary: good names, docstrings, comments-where-needed, tests, project structure, all the things.
For some reason, #HelixEditor keeps complaining about the #LSP (using both #Pyrefly and #Ruff, as usual). I'm concerned I haven't set things up right somehow, but I don't yet see where I've gone wrong.
Once this is working, further days will be easy. At least ... I hope!
-
Yes, I carry a bag (a #TomBihn #MakersBag). Yes, it’s heavy. Heavy enough that every single person who touches it has to comment. Yes, I hang things from my belt, too: like a #Leatherman #Arc, and a #Modlite PLHv2-18650. I admit: I probably carry too much stuff. You and I are different! I’m happy with this stuff. I don’t want or need to carry less.
And also: I love my name! I don’t want or need to change that, either! So quit suggesting it!
-
Yes, I carry a bag (a #TomBihn #MakersBag). Yes, it’s heavy. Heavy enough that every single person who touches it has to comment. Yes, I hang things from my belt, too: like a #Leatherman #Arc, and a #Modlite PLHv2-18650. I admit: I probably carry too much stuff. You and I are different! I’m happy with this stuff. I don’t want or need to carry less.
And also: I love my name! I don’t want or need to change that, either! So quit suggesting it!
-
Yes, I carry a bag (a #TomBihn #MakersBag). Yes, it’s heavy. Heavy enough that every single person who touches it has to comment. Yes, I hang things from my belt, too: like a #Leatherman #Arc, and a #Modlite PLHv2-18650. I admit: I probably carry too much stuff. You and I are different! I’m happy with this stuff. I don’t want or need to carry less.
And also: I love my name! I don’t want or need to change that, either! So quit suggesting it!
-
@CGM I see good in this: new and useful powers for #Python.
I see bad in this: a thing we knew about for a long time, present elsewhere, why so long coming?
I see neutral in this: things that can be provided by libraries instead of directly in the language should absolutely start in a library. If they earn a spot in the language itself, great.
I see sad in this: these words make it sound like #TCL is ahead and Python is behind overall. That doesn’t match my opinion or personal experience. Absolutely agree on this particular feature. And also I have stated many times "there is no best language", just choices more or less cost-effective for the problem at hand.
For the problems I’ve faced, with the tools I’ve had available, Python has been a more cost-effective choice than TCL the majority of the time. From your words, I took that you prefer TCL. Nothing wrong with that!
-
@CGM I see good in this: new and useful powers for #Python.
I see bad in this: a thing we knew about for a long time, present elsewhere, why so long coming?
I see neutral in this: things that can be provided by libraries instead of directly in the language should absolutely start in a library. If they earn a spot in the language itself, great.
I see sad in this: these words make it sound like #TCL is ahead and Python is behind overall. That doesn’t match my opinion or personal experience. Absolutely agree on this particular feature. And also I have stated many times "there is no best language", just choices more or less cost-effective for the problem at hand.
For the problems I’ve faced, with the tools I’ve had available, Python has been a more cost-effective choice than TCL the majority of the time. From your words, I took that you prefer TCL. Nothing wrong with that!
-
@CGM I see good in this: new and useful powers for #Python.
I see bad in this: a thing we knew about for a long time, present elsewhere, why so long coming?
I see neutral in this: things that can be provided by libraries instead of directly in the language should absolutely start in a library. If they earn a spot in the language itself, great.
I see sad in this: these words make it sound like #TCL is ahead and Python is behind overall. That doesn’t match my opinion or personal experience. Absolutely agree on this particular feature. And also I have stated many times "there is no best language", just choices more or less cost-effective for the problem at hand.
For the problems I’ve faced, with the tools I’ve had available, Python has been a more cost-effective choice than TCL the majority of the time. From your words, I took that you prefer TCL. Nothing wrong with that!
-
@CGM I see good in this: new and useful powers for #Python.
I see bad in this: a thing we knew about for a long time, present elsewhere, why so long coming?
I see neutral in this: things that can be provided by libraries instead of directly in the language should absolutely start in a library. If they earn a spot in the language itself, great.
I see sad in this: these words make it sound like #TCL is ahead and Python is behind overall. That doesn’t match my opinion or personal experience. Absolutely agree on this particular feature. And also I have stated many times "there is no best language", just choices more or less cost-effective for the problem at hand.
For the problems I’ve faced, with the tools I’ve had available, Python has been a more cost-effective choice than TCL the majority of the time. From your words, I took that you prefer TCL. Nothing wrong with that!
-
After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:
* If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
* If you’re walking down a long uncertain chain, I have two arguments:
* Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
* Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.
-
After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:
* If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
* If you’re walking down a long uncertain chain, I have two arguments:
* Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
* Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.
-
After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:
* If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
* If you’re walking down a long uncertain chain, I have two arguments:
* Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
* Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.
-
After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:
* If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
* If you’re walking down a long uncertain chain, I have two arguments:
* Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
* Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.
-
I’ve been using #difftastic as my primary diff tool in #git. Plainly, side-by-side display is the best, but my monitors are too small. I don’t see enough width in this view. So I’m using inline and I’m just not getting enough out of the tool. Difftastic is great, it just may not be for me.
-
I just switched from #Comcast to #Metronet. Fiber instead of coax. Still 1G down, but now symmetric. One third the price. And the people are all nice. Of course Comcast didn’t want me to go! I couldn’t cancel through customer service, I had to speak to a "retention specialist". She tried to get me to stay by offering exactly what Metronet is giving me for exactly the same price, but adding in a mobile line (why would I need that?)
I was kind, but I pretty much ended the discussion with this: if you give me twice the bandwidth, symmetric, at half the cost of Metronet, I’ll consider whether that makes it worth putting up with your poor reliability and customer service.
They had their monopoly, and now they don’t.
-
I just switched from #Comcast to #Metronet. Fiber instead of coax. Still 1G down, but now symmetric. One third the price. And the people are all nice. Of course Comcast didn’t want me to go! I couldn’t cancel through customer service, I had to speak to a "retention specialist". She tried to get me to stay by offering exactly what Metronet is giving me for exactly the same price, but adding in a mobile line (why would I need that?)
I was kind, but I pretty much ended the discussion with this: if you give me twice the bandwidth, symmetric, at half the cost of Metronet, I’ll consider whether that makes it worth putting up with your poor reliability and customer service.
They had their monopoly, and now they don’t.
-
I just switched from #Comcast to #Metronet. Fiber instead of coax. Still 1G down, but now symmetric. One third the price. And the people are all nice. Of course Comcast didn’t want me to go! I couldn’t cancel through customer service, I had to speak to a "retention specialist". She tried to get me to stay by offering exactly what Metronet is giving me for exactly the same price, but adding in a mobile line (why would I need that?)
I was kind, but I pretty much ended the discussion with this: if you give me twice the bandwidth, symmetric, at half the cost of Metronet, I’ll consider whether that makes it worth putting up with your poor reliability and customer service.
They had their monopoly, and now they don’t.
-
Got #Fiber installed. Still have #Comcast until I’m sure of everything. #Metronet Is my new provider. Everyone there great so far. Installation: A1. One hiccup: they are Carrier Grade NAT. That means I don’t get to control anything on the ONT (the fiber equivalent to a cable modem). Therefore, no port forwarding. Therefore, I can’t just SSH in like I’ve been doing. Just learned about other options from @jammcq research for our latest episode of @RuntimeArguments all about VPNs (and related). Installing Tailscale on my Mac was nothing. Maybe three minutes total. Tried at least three different ways to get it running on my 24.04 Kubuntu system but I still don’t have it. Jim said it was easy for him but the two of us couldn’t find any meaningful difference between our two systems. I’ll try more tonight maybe.
-
Got #Fiber installed. Still have #Comcast until I’m sure of everything. #Metronet Is my new provider. Everyone there great so far. Installation: A1. One hiccup: they are Carrier Grade NAT. That means I don’t get to control anything on the ONT (the fiber equivalent to a cable modem). Therefore, no port forwarding. Therefore, I can’t just SSH in like I’ve been doing. Just learned about other options from @jammcq research for our latest episode of @RuntimeArguments all about VPNs (and related). Installing Tailscale on my Mac was nothing. Maybe three minutes total. Tried at least three different ways to get it running on my 24.04 Kubuntu system but I still don’t have it. Jim said it was easy for him but the two of us couldn’t find any meaningful difference between our two systems. I’ll try more tonight maybe.