11–20 of 138 posts
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
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
I don't understand. What adding ".s" to the file name is supposed to correct?
And it affects their code that they run to validate when you change an extension. Normally if you open a file with an extension already (like say `test.txt`) and try to save it with a new extension (like `test.asm`), it prompts you asking something like "you've entered the extension ".asm" but the standard extension for this file type is ".txt" and gives you the options to change to the original extension or use the one you typed. If you try to change `test.txt` to `test.asm` with this bug, it tells you you've entered the ".as" extension, and not ".asm" like you actually entered.
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
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” and choose the emoji and it will be “I hope tomorrow is sunny :pray:”
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…
Personally, I’m putting good money on someone “fixing” some regex constant while doing another bug by either disabling full-match or taking off the “useless” $ at the end. This is why you don’t do unrelated fixes!! Otherwise, I don’t see any way this would get past ticket review as an intentional change in any half-awake dev team.
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
Obviously this is only two datapoints, but it seems like it's overweighting the last word instead of basing it off of the full content
I don't understand. What adding ".s" to the file name is supposed to correct?
I'm not convinced it's ".s". Of the two examples (2nd is the GitHub link in TFA), both file name extensions start with "s". Ergo, the OS dialog is doing file_name_extension.substring(0,1), perhaps? Still on Sonoma, or I would answer this question myself.
This is what happens. I'm sorry you can't reproduce it. Are you using mac for this?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 space left on device" (NSPOSIXErrorDomain:28).
Which is embarrassing, as this is a clear regression and it breaks all functionality in the browser - restarting it doesn't fix it, and I need to restart the whole machine for it to _maybe_ get fixed (and it's not really a space issue, both RAM and disk I'm nowhere near their limits).