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

21–30 of 138 posts

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

#21

Post by firecall »

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 the Sequoia release like they often do!

Edit:

These sorts of ridiculous issues are not doing anything to stop me considering moving my dev environment to Linux full time :-/

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

#22

Post by firecall »

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.

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. Which it isnt on the full size keyboard.

And I assume the developers at Apple use the big Magic Keyboard?

So did anyone of them even think for a minute about how useless it is to bind the window tiling feature to the FN key?

Plus, you can't fully disable Sequoia's tiling, so it interferes with my 3rd party tiling tool :-/

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

#23

Post by corytheboyd »

xahrepap wrote: post #14
nox101 wrote: post #11

apple also failed at using autocorrect for emoji. Type: "sorry I was late. I ran" and you want to put :sweat: but I assume you want :running: Put "I hope tomorrow is sunny" and want :pray: but it puts :sun: I guesses wrong 4 out of 5 times for me and ab unpredictable ux is a shit ux

It’s actually not _predicting_ what emoji you want. There’s aliases assigned to each emoji and you are presented with the options based on the last word you typed. You might know this already, but how Apple has coded it is it’ll replace the last word with an emoji unless you put a trailing space. But if you put down a space first it’ll add the emoji. So in your examples you would write “I hope tomorrow is sunny pray”…

This is a very reasonable way for it to work IMO. OP wants it to.. guess based on context? That’s going to be wrong more often than right.. Reasonable ask if they want it to auto-suggest emoji based on message history though.

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

#24

Post by thought_alarm »

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 to allow any file type/extension, which means it's supposed to just accept whatever the user types.

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

#26

Post by snapetom »

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.

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's a massive pain in the ass.

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

#27

Post by replete »

DavidWoof wrote: post #10
PlunderBunny wrote: post #9

In the Save File As dialog of most Windows apps, you can enclose the filename in double-quotes to force it to not add an extension. I wonder if that will help with the issue in macOS?

No, macOS will just put quotes in the name. I just saved file from vscode as "testfile.sql", including the quotes, and wound up with a file named "testfile.sql".s.

Did you upgrade to Sequoia?

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

#28

Post by chris37879 »

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

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.

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

#29

Post by ben-schaaf »

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.

In my original comment I put "feature" in quotes. I do think a change was intended, it's just not working as it should.

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

#30

Post by js2 »

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…

That issue apparently goes back a couple years.

https://osxdaily.com/2022/01/28/fix-safari-cant-open-page-ns...

https://old.reddit.com/r/MacOS/comments/qna5js/safari_issue_...

Post reply on HN