More like, no true scotsman

The beatings will continue until the demand for AI improves

✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨
it has a fucking ✨glitter✨ icon too
✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨ ✨

You know I’m talking about the Start & Stop system and not the Start & Keep Rolling Slowly, right?

I’d still like to be able to engage S&S with a button without shutting of the oil pump and whatnot, tbh.

I guess the part of Italy I live in stop signs are best described by your second paragraph, but they’re pretty frequent. These roads get wild sometimes.

You mention stop signs so that sounds like the US

Wait hold on… why’s that? Is there any juristiction where there are traffic laws, but no stop signs?

Sounds insane […]

This is in Italy, it IS insane, and admittedly I don’t know how much my grievances against S&S are mitigated by automatic transmissions (never used in tests).
Tests do not require you to disable S&S, instructors simply tell you not to let out the clutch while in neutral to avoid it, but the strictest examiners see engine shutdowns as “failure to correctly operate the vehicle”, like stalling - if it happens once, we all make mistakes, if it happens twice, come on man, if it happens three times k gg bb, it doesn’t matter whether it’s a feature of the car.

There are arguments that having your engine off on the road is unsafe, I guess those examiners are just being zealous? If they even exist, I’m trusting my instructor’s tales on this factoid, but drivers’ ed here is very strict so I’m inclined to believe him.

Most of the people who turn S&S off do so because they find it annoying, I myself try to use it effectively but I prefer driving responsibly rather than playing chess with a half-metric-ton deadly weapon.

I do know that S&S systems require better starters, but that just means they cost more, right? And even if the increased cost is marginal, the increased fuel consumption on short stops is still a problem.

As far as I’ve read around, S&S mainly wears out the starter, not the engine itself.

I don’t understand how the system could cause problems on slippery roads, but if it works on OP’s car like it does in mine, the way it’s designed to kick in is dumb, infuriating and counterproductive.

I have to disable it every time I start the car, because otherwise it would just stop the engine and restart it immediately whenever I get to a stop sign (which burns more fuel than just staying on).
BUT, if I want S&S to work, I need to re-enable it BEFORE I slow down, otherwise it just doesn’t - but I can’t predict how long I have to wait when I stop before I get to the sign, if I could they wouldn’t have put a stop sign there in the first place!

So I either:

• keep S&S enabled and disable it at every busy junction before I put it in neutral, then enable it again;
• forget about it and always keep it on, wasting fuel, increasing emissions, prematurely having my starter replaced to prevent failures in the middle of busy roads;
• forget about it and always keep it off or just never put the car in neutral, which is what all driving schools in my country teach drivers to do by the way (people have failed their tests by not preventing the engine shutdown), and possibly fully shut the engine off at my not-taking-drivers-license-test discretion.

And my car isn’t even a KIA, I can’t imagine how bad the S&S system would be on a KIA!

Spaces behave like this because markdown was designed to be like HTML but quicker to write and easier to read without formatting;
most web services that use markdown translate it to HTML rather than parsing it directly, and in HTML whitespaces are supposed to work like you demonstrated in your comment.

The reason for this behavior in HTML is “because someone in the 90s said so”, I’m afraid.

Discord does markdown differently than intended: it’s better for non-techies because hitting enter once is more intuitive than the alternative, but the standard way to insert line breaks in markdown is to type two spaces at the end of the line you want to break.

One even recommended I take a prompt engineering boot camp

Answer: Why don’t you try searching for the question first?

Me (confused face): How tf do you think I found this page?

That’s just the average stackoverflow comment

Your description of the problem has words I’ve heard before, like “a” and “even”; marked as duplicate.

Not OP, but:

• Not indexable (can’t use web search engines on its content, not even forums);
• Like Deep Rock Galactic, Discord is full of cave-dwelling creatures that abduct miners;
• The built-in search feature (the only way you can search things on it, mind you) has less filters than my uncle at thanksgiving;
• @everyone
• @everyone
• @everyone
• @everyone
• @everyone
• @everyone
• @everyone
• @everyone
• @everyone
• @everyone
• @everyone
• Can’t mute the entire server because you want notifications for mentions on a few specific channels;
• Said server creates a new channel;
• @everyone
• @everyone
• @everyone
• @everyone
• Can’t use browser bookmarks to manage and enter servers, you have to use THIS fucking thing
  
• 
  • “but they have to pay for uptime somehow”
    confirmshaming, plus they got the monopoly on this type of social services by undercutting their competition through venture capital so they could go under tomorrow for all I care
• Irrelevant for most people, but the garbage uncollapsible UI makes it painful to make it share screenspace with other windows on a FHD screen (which is a tragedy for tiling WM users);
• The markdown implementation is a bit janky IME
• “By reading the first 9 words of this notice you accept that you may not sue us and have to arbitrate your disputes”
• Third-party clients are against TOS, as you noted below

Windows 10 and 11 really dislike HDDs, that’s probably why you can’t admit to using HDDs online without getting stones thrown at you (I’ve been there before).

I’ve disabled paging files (= swap) for one of my Windows VMs, unfortunately - to my surprise - that only had a small performance boost, and I still need to let the VM chug for a few mintes before it even lets me open File Explorer.

… but it does improve performance, definitely consider doing it if you don’t need swap/paging/whatever they call it now.

I use Zsh too, though at this point is becoming detrimental to my (already limited) Bash skills because of features like the ${^array}{1,2,3} syntax which I use in some scripts of mine, which in turn I wouldn’t dare try to translate to Bash.

If the path to the dir is longer than $HOME, say, $HOME/Tools/modding/hd2-audio-modder/wwise/v123456789_idr_but_its_a_long_one/random file name with spaces, it makes more sense.

I’ll try using the braces syntax, if it does prevent word splitting I wasn’t aware of it, though it’s still slightly inconvenient (3 key inputs for each brace on my kb) and I’d probably still use quotes instead if I had to use Bash and had the file path in a variable for some reason.

… though at this point I’m probably overthinking it, atm I don’t recall better examples of my distaste for Bash expansion shenanigans.

Did some testing, here’s what I found.
Beware, it devolves into a rant against Bash and has little to do with the original topic - I just needed to scream into the void a little.

# Zsh
function argn { echo $#; }

var='spaced string'
argn $var
# Prints 1: makes sense, no word splitting here

var=(array 'of strings')
argn $var
# Prints 2: makes sense, I'm using a 2-wide array where I would
#           want 2 arguments (the second one happens to have
#           a whitespace in it)

# Bash
function argn { echo $#; }

var='spaced string'
argn $var
# Prints 2: non-array variable gets split in 2 with this simple reference;
#           I hate it, but hey, it is what it is

argn ${var}
# Prints 2: no, braces do not prevent word splitting as I think you suggested

var=(array 'of strings')
argn $var
# Prints 1: ... what?

echo $var
# Prints array: ... what?!?
#               It implicitly takes the first element?
#               At least it doesn't word-split said first element, right?

var=('array of' strings)
argn $var
# Prints 2:

Upon further investigation:

# Bash
mkdir /tmp/bashtest ; cd /tmp/bashtest
touch 'file 1'
touch 'file 2'

stat file*
# Prints the expected output of 'stat' called on both files;
# no quotes or anything, globbing just expands into
# 2 arguments without *word* splitting

files=('file 1' 'file 2')
stat $files
# stat: cannot statx 'file'
# stat: cannot statx '1'
# WHY? WHY DOES GLOBBING ACT SENSIBLY WHEN ARRAYS DO NOT?

I get that the Bash equivalent to Zsh’s $array is ${array[@]}, but making $array behave like it does in Bash has no advantage whatsoever.
… IS WHAT I WOULD SAY IF THAT WERE TRUE! YOU ALSO HAVE TO QUOTE "${array[@]}" BECAUSE WE LOVE QUOTES HERE AT BASH HQ!

# ... continued from before
stat "prefix ${files[@]}"
# stat: cannot statx 'prefix file 1'
# (regular 'stat' output for 'file 2')

While this behavior doesn’t make much sense to me, it also doesn’t make sense for me to write that “prefix” within the quotes in the first place, right?
YES. BECAUSE SPLITTING IS NOT WHAT YOU EXPECT WHEN YOU PUT STUFF IN QUOTES.

Sorry, I’ll stop.

o7, probably worth a shot