And that is why you don’t use JS on your backend.

Because you don’t want to be losing 5 BTC

Helping them out in court would be the main string.

I believe that’s the main reason they are paying Mozilla. To make them look kinda good.

The x86 CPU will be 2 additional layers

“But I want it to do something other than that!”

If those project managers could read, they would actually be able to use Jira.

I regret what I wrote.
I realised, just being able to read, doesn’t make sure they can actually use Jira

Make sure to convert 1/2 to February

They change it because they need more money. (talking about Excel here)
And soon you’ll see ads in the fn suggestions drop down
and ads in unused cells
and ads while the Solver is running (made in VisualBasic, running on top of WebAssembly, running on interpreted Python, using a Java Interpreter on your Web Browser to make sure you watch the ad for as long as possible)

And that’s why we need to make our own spreadsheet software.

No need for tinnitus when you can hear coil whine.

Bonus point for making me feel like it is going to start burning any time soon.

I can make a few, using a chalk-piece and a bottle of blue ink

They are using the Declaration of Independence font.

If that’s supposed to be a pun, I didn’t get it.

That looks nice and easy to understand.
I would go one step further and according to my preferences:
(starting from line5)

FileCompareWorker::FileComparisonParams
{
	FileComparisonParams::FileNameMatch,
	(ckFile.size() > otherFile.size())
		? FileComparisonParams::File1IsLarger
		: FileComparisonParams::File2IsLarger
}

Break before the curly as I do for most.

Honestly, I’d prefer all curly’s in a new line, indented according to the previous one and in some cases, even parentheses in new lines.

But if I had a problem with that, I would just go ahead and break the line down (that’s a single statement, I consider it 1 line of code) into multiple, with the arguments put into variables.

You can fix the problem of gay men marrying gay women by letting gay men marry gay men and letting gay women marry gay women.

Go to:
/media/ulterno/Data/code/website

and run /opt/jekyllrb/jekyll/bin/jekyll serve.

Worked for me that way.

1. I am using tabs for INDENTATION. I don’t want alignment.

• I have tried my best to remove all alignment operations of clang-format

2. What do you use tabs for?

I am noone to say no to your preferences. and you can set your config that way.
I want the “before” in my project.

Also, consider the case where the thing after the : were longer and it would be using another line.

I think I’d rather go with the ? being on the same line as the ‘condition’ and the rest can go on the other line.

Otherwise, I’d be looking one line downwards and then coming back up after realising that it is a (cond)?ex:ex operator.

And I get that it’s not random, just that I asked for it at as many places as possible to not do alignment.
And from what I can recall, I had managed to make stuff work with the older clang-formats…
Or maybe not. Maybe this kind of code never went through it.

Your alt text formatting is way different from the pic by the way

Hmm.
I really just copied the stuff directly. Let me try again.

pretty common standard

I get it. But I set all available “Align” flags to false and am still getting this.
I just want a simple thing that only does continuation indents. If there is a space added, it should be something according to the coder (Is what I mean by indents only). though not even that, because all spaces before the first character in the line are to be removed.

Not random

Well, I guess I’ll go put a better word in there

BTW, I changed my code to avoid the formatting:

{
	if (ckFile.size() > otherFile.size())
	{
		emit differentFiles (ckFile.absoluteFilePath(),
			otherFile.absoluteFilePath(),
			FileCompareWorker::FileComparisonParams{
				FileComparisonParams::FileNameMatch, FileComparisonParams::File1IsLarger});
	}
	else
	{
		emit differentFiles (ckFile.absoluteFilePath(),
			otherFile.absoluteFilePath(),
			FileCompareWorker::FileComparisonParams{
				FileComparisonParams::FileNameMatch, FileComparisonParams::File2IsLarger});
	}
}

BTW, here is my .clang-format in case you are interested