I think our build instructions are fine now, do we need to keep this task here?

This needs to wait until the resource rewrite, or at least be based on resource rewrite and merged only when the RR is finished.

No, nothing is wrong.

Is there anything that is wrong. I am sorry but I am unable to understand any of your comments.

Probably, but I think it is a work of art. If I could close it, I would.
That is just my opinion.

I think this is going out of hand

Note: it takes 2 minutes for your competitors to suck up this info here. They make money. I am money. I often dislike reading the aftermath, but sometimes it is like tomorrow.

I personally would add the "thank you for nut thing" image, but I should really not be intentionally insulting. So in conclusion: the article you wrote is just fine..

Most people would tell whoever said whatever told you did a good job.

no. live. nothing is wrong. thank you.

I added a link from my collection of links that mentions lldb and how to use it, I think I knew it from someone on IRC but can't say if the instruction is correct or not.

macOS has lldb which is a bit like gdb, but not quite.

• Appimage apparantly needs the debugsymbols to not be stripped according to @rempt , this currently happens to reduce size)
• repositoryversion can have debugsymbols seperate.
• Flatpak, no idea.
• dr. Konqi is the KCrash library and I think it starts up when there's a debugsymbols package available, but I am not privy to it's actual workings.

I added more explanation what I want from the explanation about tablet drivers.

I have been meaning to do something about the crashlog guide, but I just don't have a windows device, so it's been windragon and scott who update it.

Are you testing a bot on the phabricator website???

Conclusion
It is well worded and could be worded better, take very much care in your words, as it is insulting. This is acceptable. Thank You.
AfterMath

re-opening Krita should offer to recover the autosave file

A more detailed guide on how to use the build script.

I have tried building with your script, but it didn't work in the end :(

this MR is now in gitlab https://invent.kde.org/websites/docs-krita-org/merge_requests/33 so closing this

I'm are in my other work! Inspect it, sure.

Aah sorry @Abella I didn't recognise your nick, you last merge request was merged without problem, although the RM was not automatically closed, that is not a problem. I can help you create a fork in your branch if you wish. Are you on IRC?

@kamathraghavendra , I think @Abella is doing this because he is having trouble with figuring out why it didn't work last time. The problem was that he should've tried to commit his changes to a branch. Maybe you can help him with creating a branch in his fork, or otherwise commit locally?

Hi @Abella would it be possible for you to add this diff as a Merge request in our gitlab instance. All the development of Krita is currently shifted to https://invent.kde.org/ and the repository for the manual is https://invent.kde.org/websites/docs-krita-org . you can use your same kde identity to create the Merge request . Here is a guide for creating merge request. If you find any difficulty feel free to ping me on IRC # krita channel