[kdevelop] [Bug 437199] Project tool looks inconsistently across machines
https://bugs.kde.org/show_bug.cgi?id=437199 Fikret Skrgic changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Fikret Skrgic --- I figured out that this is controlled by KDE settings. One can select icon sizes for classes of icons. Settings -> Appearance -> Icons -> Configure Icon Sizes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 460901] New: Update AppImages more frequently
https://bugs.kde.org/show_bug.cgi?id=460901 Bug ID: 460901 Summary: Update AppImages more frequently Classification: Applications Product: kdevelop Version: unspecified Platform: Appimage OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: skr...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** For quite some time I had the luxury to work on any distribution of my choice. At my current job, however, I have to work on a very old distribution and there's no chance that will change. The version of KDevelop available on that distribution is also ancient. The best I can do is to download an AppImage. I am really grateful for having that option. It is a life saver. I am sure there are many other people in the same predicament. It would be absolutely fantastic if these AppImages would be updated a bit more frequently. Even better if they were released regularly for major new versions. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #16 from Fikret Skrgic --- Another problem, which is probably related, and I would also be really happy if it was fixed. If in Settings -> Editor -> Editing -> Indentation, one selects to "adjust indentation of code pasted from the clipboard", it does not follow the source formatting style at all. This problem is also decades old. I have been using KDevelop since not much later than it came into existence and both these problems have always been there. So, there must be some formatting code, which supersedes, overrides, or bypasses the selected source formatting. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #15 from Fikret Skrgic --- (In reply to Igor Kushnir from comment #13) > Is there a Kate Modeline > (https://kate-editor.org/2006/02/09/kate-modelines/) in the file you are > editing? No, there are no modelines. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #14 from Fikret Skrgic --- (In reply to Igor Kushnir from comment #12) > Select the class's code, right click on the selection, trigger the Reformat > Source action. Does the result agree with your formatting configuration? Yes, if I do that, the code gets fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #11 from Fikret Skrgic --- Screenshots 1 and 2 show the difference between selecting and not selecting class in the indentation. When class is selected, access modifiers should be indented. In the third you can see my style. In the fourth there is some code I will try to modify. In the fifth I type "protected" (no colon yet). In the sixth I add a colon and the text immediately gets shifted to the left. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #10 from Fikret Skrgic --- Created attachment 153146 --> https://bugs.kde.org/attachment.cgi?id=153146=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #9 from Fikret Skrgic --- Created attachment 153145 --> https://bugs.kde.org/attachment.cgi?id=153145=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #8 from Fikret Skrgic --- Created attachment 153144 --> https://bugs.kde.org/attachment.cgi?id=153144=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #7 from Fikret Skrgic --- Created attachment 153143 --> https://bugs.kde.org/attachment.cgi?id=153143=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #6 from Fikret Skrgic --- Created attachment 153142 --> https://bugs.kde.org/attachment.cgi?id=153142=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #5 from Fikret Skrgic --- Created attachment 153141 --> https://bugs.kde.org/attachment.cgi?id=153141=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 --- Comment #4 from Fikret Skrgic --- (In reply to Igor Kushnir from comment #3) > Have you tried checking the *Override Kate Indentation Mode* checkbox on the > Source Formatter tab of KDevelop settings? It makes no difference. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352038] Indentation does not work as specified in the source formatter
https://bugs.kde.org/show_bug.cgi?id=352038 Fikret Skrgic changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #2 from Fikret Skrgic --- (In reply to Justin Zobel from comment #1) > Thank you for reporting this bug in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! It is still there and has been there for decades now. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437199] Project tool looks inconsistently across machines
https://bugs.kde.org/show_bug.cgi?id=437199 Fikret Skrgic changed: What|Removed |Added CC||skr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437199] Project tool looks inconsistently across machines
https://bugs.kde.org/show_bug.cgi?id=437199 --- Comment #1 from Fikret Skrgic --- Created attachment 138482 --> https://bugs.kde.org/attachment.cgi?id=138482=edit Large icons -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437199] New: Project tool looks inconsistently across machines
https://bugs.kde.org/show_bug.cgi?id=437199 Bug ID: 437199 Summary: Project tool looks inconsistently across machines Product: kdevelop Version: 5.6.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: skr...@gmail.com Target Milestone: --- Created attachment 138481 --> https://bugs.kde.org/attachment.cgi?id=138481=edit Small icons SUMMARY STEPS TO REPRODUCE 1. Install the same distribution on different machines and update everything. 2. Take some project and copy it both machines. 3. Open it with KDevelop on the two machines. OBSERVED RESULT Look at the Projects tool. It will look randomly one way or the other. EXPECTED RESULT The look of it should be consistent. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 with KDE KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION There might be a setting that controls this, but I haven't been able to stumble upon it. This has also been alternating across versions of KDevelop on the same machine. It looks one way, I update to newer version, it flips to the other look. Later there is a new version and after the update it flips back. After upgrading to Fedora 34, it flipped on one machine. I checked the other, which I also upgraded and updated, and it didn't. The same seems to hold for the Documents tool. Ideally it should behave like the File System tool, where you can change the icons by holding control and rotating the scroll wheel. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437198] Project tool looks inconsistently across machines
https://bugs.kde.org/show_bug.cgi?id=437198 --- Comment #1 from Fikret Skrgic --- I was not done writing the description and accidentally hit enter at the wrong time. The bug was created incomplete. I don't see how I can edit the description or delete it to start over. Can someone delete this since I will create a new one with complete description. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437198] New: Project tool looks inconsistently across machines
https://bugs.kde.org/show_bug.cgi?id=437198 Bug ID: 437198 Summary: Project tool looks inconsistently across machines Product: kdevelop Version: 5.6.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: skr...@gmail.com Target Milestone: --- Created attachment 138480 --> https://bugs.kde.org/attachment.cgi?id=138480=edit Small icons SUMMARY STEPS TO REPRODUCE 1. Install the same distribution on different machines and update everything. 2. Take some project and copy it both machines. 3. Open it with KDevelop on the two machines. OBSERVED RESULT Look at the Projects tool. It will look randomly one way or the other EXPECTED RESULT The look of it should be consistent. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 420998] Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=420998 --- Comment #4 from Fikret Skrgic --- Now I am getting a crash every single time I open a specific project. Nothing helps. It crashes every time here: Thread 21 "Queue(0x55b" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff8da12700 (LWP 5383)] 0x7fff8ddd4bc1 in isSameTemplateParameterList(clang::ASTContext const&, clang::TemplateParameterList const*, clang::TemplateParameterList const*) [clone .cold] () from /lib64/libclang.so.10 (gdb) (gdb) bt #0 0x7fff8ddd4bc1 in isSameTemplateParameterList(clang::ASTContext const&, clang::TemplateParameterList const*, clang::TemplateParameterList const*) [clone .cold] () from /lib64/libclang.so.10 #1 0x7fff8ec2dbaf in clang::ASTDeclReader::findExisting(clang::NamedDecl*) () from /lib64/libclang.so.10 #2 0x7fff8ec37719 in void clang::ASTDeclReader::mergeRedeclarable(clang::Redeclarable*, clang::ASTDeclReader::RedeclarableResult&, unsigned int) () from /lib64/libclang.so.10 #3 0x7fff8ec3781e in clang::ASTDeclReader::VisitRedeclarableTemplateDecl(clang::RedeclarableTemplateDecl*) () from /lib64/libclang.so.10 #4 0x7fff8ec37cc3 in clang::ASTDeclReader::VisitFunctionTemplateDecl(clang::FunctionTemplateDecl*) () from /lib64/libclang.so.10 #5 0x7fff8ec38c66 in clang::ASTDeclReader::Visit(clang::Decl*) () from /lib64/libclang.so.10 #6 0x7fff8ec3909b in clang::ASTReader::ReadDeclRecord(unsigned int) () from /lib64/libclang.so.10 #7 0x7fff8ebd7441 in clang::ASTReader::GetDecl(unsigned int) () from /lib64/libclang.so.10 #8 0x7fff8ebda469 in clang::ASTReader::FindExternalLexicalDecls(clang::DeclContext const*, llvm::function_ref, llvm::SmallVectorImpl&) () from /lib64/libclang.so.10 #9 0x7fff8df4db73 in clang::DeclContext::LoadLexicalDeclsFromExternalStorage() const () from /lib64/libclang.so.10 #10 0x7fff8df4dc4d in clang::DeclContext::decls_begin() const () from /lib64/libclang.so.10 #11 0x7fff8de9806c in clang::cxcursor::CursorVisitor::VisitDeclContext(clang::DeclContext*) () from /lib64/libclang.so.10 #12 0x7fff8de97047 in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) () from /lib64/libclang.so.10 #13 0x7fff8de9eccd in clang_visitChildren () from /lib64/libclang.so.10 #14 0x7fffa4dd6527 in CXChildVisitResult (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)22, KDevelop::Declaration, true>(CXCursor) () from /lib64/libKDevClangPrivate.so.33 #15 0x7fffa4dee33e in (anonymous namespace)::visitCursor(CXCursor, CXCursor, void*) () from /lib64/libKDevClangPrivate.so.33 #16 0x7fff8de97526 in clang::cxcursor::CursorVisitor::Visit(CXCursor, bool) () from /lib64/libclang.so.10 #17 0x7fff8de97eed in clang::cxcursor::CursorVisitor::handleDeclForVisitation(clang::Decl const*) () from /lib64/libclang.so.10 #18 0x7fff8de980e8 in clang::cxcursor::CursorVisitor::VisitDeclContext(clang::DeclContext*) () from /lib64/libclang.so.10 #19 0x7fff8de97047 in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) () from /lib64/libclang.so.10 #20 0x7fff8de9eccd in clang_visitChildren () from /lib64/libclang.so.10 #21 0x7fffa4dd6527 in CXChildVisitResult (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)22, KDevelop::Declaration, true>(CXCursor) () from /lib64/libKDevClangPrivate.so.33 #22 0x7fffa4dee33e in (anonymous namespace)::visitCursor(CXCursor, CXCursor, void*) () from /lib64/libKDevClangPrivate.so.33 #23 0x7fff8de97526 in clang::cxcursor::CursorVisitor::Visit(CXCursor, bool) () from /lib64/libclang.so.10 #24 0x7fff8de97eed in clang::cxcursor::CursorVisitor::handleDeclForVisitation(clang::Decl const*) () from /lib64/libclang.so.10 #25 0x7fff8de980e8 in clang::cxcursor::CursorVisitor::VisitDeclContext(clang::DeclContext*) () from /lib64/libclang.so.10 #26 0x7fff8de9730a in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) () from /lib64/libclang.so.10 #27 0x7fff8de9eccd in clang_visitChildren () from /lib64/libclang.so.10 #28 0x7fffa4dd1b0d in Builder::visit(CXTranslationUnitImpl*, void*, QHash const&, bool) () from /lib64/libKDevClangPrivate.so.33 #29 0x7fffa4df9a3c in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () from /lib64/libKDevClangPrivate.so.33 #30 0x7fffa4df9472 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () from /lib64/libKDevClangPrivate.so.33 #31 0x7fffa4df9472 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () from /lib64/libKDevClangPrivate.so.33 #32 0x7fffa4df9472 in ClangHelpers::buildDUChain(void*, QMultiHash const&a
[kdevelop] [Bug 420998] Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=420998 --- Comment #3 from Fikret Skrgic --- Created attachment 128694 --> https://bugs.kde.org/attachment.cgi?id=128694=edit New crash information added by DrKonqi kdevelop (5.5.1) using Qt 5.13.2 - What I was doing when the application crashed: I started KDevelop and selected a project. It opened it up. I immediatly clicked on build since I knew there was a problem in my code when I stopped working yesterday and wanted to jump to that point by clicking on the compiler warning. It crashed. I restarted, selected the project again and diod nothing else. As soon as it loaded, it crashed again. I repeated this then over and over again. It hasn't stopped yet. At some point it asked me whether I wanted to clear the cache. It didn't help. I have experienced the same behavior before. It would crash in the middle of writing a line of code. If I would agree to recover after a restart and just start typing that line again, it would crash again. The way I would get it top stop is by not recovering and having git reset changes. -- Backtrace (Reduced): #7 0x7f67192e8baf in clang::ASTDeclReader::findExisting(clang::NamedDecl*) () from /lib64/libclang.so.10 #8 0x7f67192f2719 in void clang::ASTDeclReader::mergeRedeclarable(clang::Redeclarable*, clang::ASTDeclReader::RedeclarableResult&, unsigned int) () from /lib64/libclang.so.10 #9 0x7f67192f281e in clang::ASTDeclReader::VisitRedeclarableTemplateDecl(clang::RedeclarableTemplateDecl*) () from /lib64/libclang.so.10 #10 0x7f67192f2cc3 in clang::ASTDeclReader::VisitFunctionTemplateDecl(clang::FunctionTemplateDecl*) () from /lib64/libclang.so.10 #11 0x7f67192f3c66 in clang::ASTDeclReader::Visit(clang::Decl*) () from /lib64/libclang.so.10 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 420998] Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=420998 Fikret Skrgic changed: What|Removed |Added CC||skr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
