Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

forum.sublimetext.com

Post reply on HN
Print view View original

71–80 of 138 posts

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

#71

Post by QasimK »

lmpdev wrote: post #52
righthand wrote: post #45

Earlier quoted context omitted.

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)

In the five years I have used Arch, I have not had a single issue.

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

#72

Post by nikisweeting »

Ukv wrote: post #7

My guess, having never used OSX: 1. In the save dialog, filetype can determined in multiple ways (maybe selected from a dropdown, or be set by the program opening the dialog) and not necessarily just inferred from user-entered filename 2. So when returning the path to the program, it appends the filetype's extension to the path iff it doesn't already end in it (so user can enter just `notes` and file gets saved as `n…

I iTunes had a very similar "autocomplete tries to be helpful but causes chaos" bug a few years back. If you clicked to edit the artist column it would autocomplete from the list of other artists in your library. However, if your desired artist name was shorter than one it's trying to autocomplete, it would forcibly append the rest of the name from the longer artist.

e.g. if you typed "Ross" and wanted it to just be "Ross", but you have any track by "Ross from Friends" in your library, it would always append " from Friends" no matter how many times you tried deleting it.

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

#73

Post by nikisweeting »

avazhi wrote: post #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.

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

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

#74

Post by drawnwren »

whiterknight wrote: post #70
concinds wrote: post #62

Earlier quoted context omitted.

Some other things that devs should know about Sequoia: - If you're sticking to Sonoma for stability, be aware Apple doesn't backport all security patches. Apple's release notes show 79 security issues fixed in Sequoia, and only 37 fixed in Sonoma 14.7. Maybe some vulns were only introduced in the Sequoia betas, but based on previous years, that's mostly not the case. Apple only keeps you safe on the latest version. -…

I promise, you will be just fine without the security updates.

This is probably misguided. Apple includes the OS version number in the user agent, so an attacker can actually pay to have code delivered only to users with vulnerable versions of MacOS. (advertising marketplaces allow bidding by user agent)

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

#75

Post by xlii »

NlightNFotis wrote: post #19

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 had a very similar issue some time back that was caused by LSP.

Long story short I had multiple long running LSPs (fragmented projects) in Emacs that would open many handlers and keep them open. At some point same error started happening and I thought only restart could resolve it.

But then I was at the hotel where merely switching network made this issue to appear (I suppose binding was somewhat related to and switch made pool exhaust pool quicker) so I decided to debug it.

It turned out that restarting Emacs was enough to close file handlers and resume operations.

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

#76

Post by petre »

firecall wrote: post #32
chris37879 wrote: post #28

Earlier quoted context omitted.

To answer your questions, no, they do not use an editor that isn't Xcode. And I would also suspect none of them use desktop macs daily and instead use macbooks.

But surely they must tether their MacBooks to external displays and desktop Mouse’s and Keyboards! I didn’t think they’d be using Mac minis, Studios or Pros as such. They can’t all be using the little mini Magic Keyboard or working directly on their laptops? Can they…. :-O

The MacBook keyboard is atrocious. I always mess up the passwords a bunch of times.

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

#77

Post by threeseed »

drawnwren wrote: post #74
whiterknight wrote: post #70

Earlier quoted context omitted.

I promise, you will be just fine without the security updates.

This is probably misguided. Apple includes the OS version number in the user agent, so an attacker can actually pay to have code delivered only to users with vulnerable versions of MacOS. (advertising marketplaces allow bidding by user agent)

The user agent is defined by the browser.

And it only contains: Intel Mac OS X 10_15_7 irrespective of what Mac you are using.

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

#78

Post by concinds »

LtWorf wrote: post #69
concinds wrote: post #49

Earlier quoted context omitted.

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

And entering my password in a different kind of text box is more secure how?

2FA support. Gmail requires 2FA.

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

#79

Post by threeseed »

LtWorf wrote: post #69
concinds wrote: post #49

Earlier quoted context omitted.

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

And entering my password in a different kind of text box is more secure how?

Because you are entering it into a Google login flow.

Which usually will have MFA and sometimes not a text box at all (passkey).

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

#80

Post by drawnwren »

threeseed wrote: post #77
drawnwren wrote: post #74

Earlier quoted context omitted.

This is probably misguided. Apple includes the OS version number in the user agent, so an attacker can actually pay to have code delivered only to users with vulnerable versions of MacOS. (advertising marketplaces allow bidding by user agent)

The user agent is defined by the browser. And it only contains: Intel Mac OS X 10_15_7 irrespective of what Mac you are using.

I’m seeing Mozilla/5.0 (Macintosh; Intel Mac OS X 14_7). What do you think the 14_7 stands for on MacOS 14.7?
Post reply on HN