Live data from Hacker News

Sublime text started adding a “.s” to new files

forum.sublimetext.com

41–50 of 138 posts

Re: Sublime text started adding a “.s” to new files

#41

I'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

Re: Sublime text started adding a “.s” to new files

#42
Python does something similarly annoying with shelve files. I will never use that module again.

> The shelve module is implemented on top of the dbm module. This module acts as a facade for 3(* different specific DBM implementations, and it will pick the first module available when creating a new database, in the following order:

> It is this range of choices that makes shelve files appear to grow extra extensions on different platforms.

https://stackoverflow.com/questions/16171833/why-does-the-sh...

Re: Sublime text started adding a “.s” to new files

#43

Hot Damn! Is that what is happening! I've been experiencing this with SublimeText and VSCode! I've taken screenshots, and a video, but had not submitted any bug reports yet. Whenever I make a new file, say 'foo.html.haml' the system will append .h to the file. I'd guessed it was a system wide issue, and uninstalled the new XCode just on the off chance, but that made no difference. Maybe Apple should have held back th…

It’s great over here in the Linux world, I run Debian and Arch. Arch may give you regressions, but Debian is pretty smooth sailing functionally.

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.

Re: Sublime text started adding a “.s” to new files

#45

Earlier quoted context omitted.

It’s great over here in the Linux world, I run Debian and Arch. Arch may give you regressions, but Debian is pretty smooth sailing functionally.

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 really is a nice experience.

Not even Apple products have that solid of a package situation.

Re: Sublime text started adding a “.s” to new files

#46

Who thought this was a good idea? Is there any actual documentation on this or is it just a thing they added?

Isn’t this almost certainly a bug? I’m pretty sure the MacOS developers don’t really want to add a .s extension to files.

I can understand people thinking it’s a misguided feature considering my own experiences.

Re: Sublime text started adding a “.s” to new files

#48
post #47

Title here should be "Sublime text started adding a “.s” to new files. Very annoying".

Strangely, it’s not doing this to me, at all, with the non-beta Sequoia and using Nova. I’ve been happily coding away without that happening.

Not saying this isn’t happening for other people, of course! But it must be some odd interaction between Sublime or Zed and Sequoia, not a new intentional feature affecting everyone or every editor.

Re: Sublime text started adding a “.s” to new files

#49

I will never understand how a bunch of technically-inclined people can look at an obvious bug and think it was put in intentionally.

This happens everywhere in Apple products. It thinks it knows better than you, and completely screws power users. Try manually adding IMAP/POP/SMTP servers in Mail in both iOS and MacOS. First off the process is nowhere near consistent. Second, they both try to be clever if they detect supported hosts like gmail. It'll kick off different flows because it thinks gmail is gmail. So for things like custom reply-to's, it…

Gmail requires a different login flow, because they're dropping password authentication in favor of OAuth, for pretty reasonable security reasons.

Re: Sublime text started adding a “.s” to new files

#50
Holy shit Sequoia is the biggest dumpster fire OS I think I've ever seen Apple release on the Mac.

They would have been better off just skipping a year instead of releasing... whatever the hell this even is.

Every time Apple shits the software bed hard like this I hope it will be something of a Vista moment for them and they'll clean house with the MacOS software team, but it never happens and things just get worse.

Post reply on HN