Sublime text started adding a “.s” to new files • Hacker News Board

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

#31

Post by righthand » Mon, Sep 23, 2024, 12:26 AM UTC

firecall wrote: post #21

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.

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

#32

Post by firecall » Mon, Sep 23, 2024, 12:26 AM UTC

chris37879 wrote: post #28

firecall wrote: post #22

Earlier quoted context omitted.

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…

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

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

#33

Post by [deleted] » Mon, Sep 23, 2024, 12:35 AM UTC

crooked-v wrote: post #20

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

[deleted]

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

#34

Post by paveworld » Mon, Sep 23, 2024, 12:37 AM UTC

I wonder if this also happens if a partition is formatted case-sensitive?

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

#35

Post by fragmede » Mon, Sep 23, 2024, 12:48 AM UTC

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…

What's your particular use case to keep using Safari if it's not working for you and there are alternatives available?

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

#36

Post by inetknght » Mon, Sep 23, 2024, 1:16 AM UTC

thought_alarm wrote: post #24

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…

It's just a bug. The system save panel (NSSavePanel) is only supposed to infer the file extension when it has been given a list of supported file types/extensions. If the user does not specify a file extension, NSSavePanel will use the first extension in the supported list. If the user specifies an unsupported extension, they see an error message. Text editors like VSCode and Sublime Text would configure NSSavePanel…

> 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.

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

#37

Post by dannyw » Mon, Sep 23, 2024, 1:33 AM UTC

fragmede wrote: post #35

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…

What's your particular use case to keep using Safari if it's not working for you and there are alternatives available?

Not GP, but:

iOS Safari dev tools

Testing for compatibility

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

#38

Post by [deleted] » Mon, Sep 23, 2024, 1:45 AM UTC

echoangle wrote: post #8

loktarogar wrote: post #2

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.

[deleted]

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

#39

Post by ezfe » Mon, Sep 23, 2024, 1:48 AM UTC

Has anyone in any of these threads filed a feedback report with Apple? It takes 30 seconds to do and since this seems to be new in macOS Sequoia it would definitely be worth it.

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

#40

Post by 3836293648 » Mon, Sep 23, 2024, 1:49 AM UTC

ChrisMarshallNY wrote: post #15

Xcode'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?