Title here should be "Sublime text started adding a “.s” to new files. Very annoying".
I understand the urge to remove editorializing but I don't think that extends to incorrectly blaming Sublime text in the title when we know better.
Sublime text started adding a “.s” to new files
51–60 of 138 posts
Re: Sublime text started adding a “.s” to new files
#52Earlier quoted context omitted.
Maybe I’m getting old, but my long time preference for Arch is slowly being overtaken by my appreciation for Debian. It’s not the usual complaint about stability — I’ve had one issue in a dozen years with Arch — I just reached a point where I feel like I’m living in the future running Linux software from five years ago, so maybe I don’t need to upgrade quite so relentlessly. Anything I don’t have, I can compile.
What Debian has nailed in the last 10 years is the package management situation that is so smooth. This is why I’m leaving Arch, everything breaks sometimes or a dep won’t upgrade for this or that reason. Debian you install and the package probably has a pretty good initial config and works. Any packages that aren’t recent enough can be built usually because the toolchain versions are probably recent enough. So it re…
Aren’t Debian and Arch philosophic opposites though?
Arch is bleeding edge yet permanently issue prone, Debian is stable and conservative/slow in updating?
Seems odd to jump from one end of the spectrum to another (I use Debian and Mint mostly but have respect for the Arch project’s aims)
Re: Sublime text started adding a “.s” to new files
#53Xcode's new autocomplete is pretty awful. It tries to be smart, but keeps hallucinating nonexistent API methods, and makes up stuff from my own codebase.
Is it actually making stuff up or is it falsely believing that some type conforms to a protocol it doesn't?
It fully makes things up, like nonexistent parameters to real functions. In the areas where it's accurate it's barely better than the existing autocomplete, though I have noticed it seems to deal a bit better with broken code (which also breaks Swift's compiler-based tooling). It can also generate larger things like type definitions a bit better, but Apple never really invested into autocomplete, so it's not really anything better than what other IDEs already had.
Re: Sublime text started adding a “.s” to new files
#54I've recently come across a spectacular number of regressions on my M3 Max MacBook Pro, Sequoia as well as previous versions included. The most workflow breaking one (which really tempts me to throw the computer out of the closest window I can find in the room) is a Safari bug that basically randomly fails to open any website with a > Safari can't open the page. The error is: "The operation couldn't be completed. No…
I get this too
Re: Sublime text started adding a “.s” to new files
#55I've recently come across a spectacular number of regressions on my M3 Max MacBook Pro, Sequoia as well as previous versions included. The most workflow breaking one (which really tempts me to throw the computer out of the closest window I can find in the room) is a Safari bug that basically randomly fails to open any website with a > Safari can't open the page. The error is: "The operation couldn't be completed. No…
I (think) I have a fix for you. 1. Open Activity Monitor 2. Find "Safari Networking" 3. Force quit 4. Refresh Safari tab (that didn't work) Works on M1 MBP w/Sonoma 14.5
Have same issue. The above solution did not resolve the issue. It doesn't bother me much because I mostly use Firefox, but it causes problems when I'm testing front-end stuff on Safari.
Re: Sublime text started adding a “.s” to new files
#56I've recently come across a spectacular number of regressions on my M3 Max MacBook Pro, Sequoia as well as previous versions included. The most workflow breaking one (which really tempts me to throw the computer out of the closest window I can find in the room) is a Safari bug that basically randomly fails to open any website with a > Safari can't open the page. The error is: "The operation couldn't be completed. No…
[deleted]
Re: Sublime text started adding a “.s” to new files
#57I will never understand how a bunch of technically-inclined people can look at an obvious bug and think it was put in intentionally.
I don't understand why and how does Apple keep breaking stuff that has worked perfectly fine for the previous 24 years. Like, just don't touch it maybe if it already works?
Also yearly major OS updates are beyond stupid.
Re: Sublime text started adding a “.s” to new files
#58I will never understand how a bunch of technically-inclined people can look at an obvious bug and think it was put in intentionally.
It bonkers isnt it! Do none of Apple's developer team use any other editor at anytime other than XCode! How was this not picked up in beta testing!? Here's another gripe: The tiling feature maddens me! You cant disable it completely or remap the key bindings. Did anyone at Apple even test this using a full size Magic Keyboard? Using the FN key to move windows is fine when the key is down next to the Control key. Whic…
Are you sure you can't remap the keyboard shortcuts?
I believe you can change them in System Settings -> Keyboard -> Keyboard Shortcuts
Re: Sublime text started adding a “.s” to new files
#59I will never understand how a bunch of technically-inclined people can look at an obvious bug and think it was put in intentionally.
I will never understand how Apple doesn't have automated testing that catches all these basic bugs before shipping.
Re: Sublime text started adding a “.s” to new files
#60:w ~/my/path/thing.txt
Works every time.