Live data from Hacker News

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

forum.sublimetext.com

111–120 of 138 posts

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

#111
post #107
post #97

Earlier quoted context omitted.

Gmail can require 2FA more or less at google's whim, regardless of user preferences (and if you don't have a method set up, you'll be locked out of logging in, at least through that particular device/connection)

It can require it if it is enabled . Which is not mandatory .

If Google detects something strange or is just feeling particularly chaotic that day, they will lock the account and require you to verify it using the phone number. Even if you don't have 2FA enabled.

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

#112
post #44

Thanks Apple for proving yet again why I should never upgrade to the latest macOS/iOS. this company is worth a trillion dollars yet can’t get basic shit right.

I just saw macOS Sequoia 15.0 today on my Mac and thought "gonna skip the .0 version as always on this one". Now I find this thread to just prove my point. iOS is not nearly as bad imho, but with macOS, some stuff like this happens every year.

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

#113
post #100

Earlier quoted context omitted.

Wow. Coming from DOS times, supporting double quotes in a filename is wild. I _still_ tend not to use whitespaces in filenames!

pretty common on UNIXes; you can also have forward slashes in filenames. They just have to be escaped to differentiate.

I don't know of any Unix that allows forward slashes in file names. On macOS you can use : which is displayed as / in Finder, but in exchange you can't put a : in file names...

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

#116
post #53

Earlier quoted context omitted.

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 a…

Oh yeah. For example:

I may have a method in my class:

    straightenCheese(byDegrees: CGFloat)
The "helpful" autofill might give me:

    straightenCheese(by: Double)
If I'm lucky, but it's more likely to give:

    strengthenCheese(by: Double)

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

#117

Earlier quoted context omitted.

> It's just a bug. It's an unforgivable bug. File save dialogs have been around for decades. There's no reason whatsoever to not have very extensive unit and integration tests around it.

Exactly, and when you interview for companies like this you have to basically prove that you are in the top 1% developers in the world, just to find shit like this being released in the wild for millions of devices. It is absurd.

Better never navigate through AOSP source code.

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

#119
post #55
post #41

Earlier quoted context omitted.

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.

Bummer. Agree w/workaround solutions. I've just flipped to other browsers for most situations.

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

#120

Earlier quoted context omitted.

I just pray they never fire whoever maintains the iTunes Classic Visualizer, that thing is a gem and it still gets updates sometimes.

Isn't iTunes already dead and replaced with music?

Replaced is doing some work.

Rebranded is more apt. It’s still iTunes.

Post reply on HN