[kfile] [Bug 166696] Support multiple columns in places menu

2018-06-14 Thread Nach
https://bugs.kde.org/show_bug.cgi?id=166696 --- Comment #2 from Nach --- I don't know why it implies a super wide panel. With smaller icons, it would be possible to lay them out in a grid. -- You are receiving this mail because: You are watching all bug changes.

[kfile] [Bug 166697] KDE4 file dialogs is missing seperate folders view

2018-04-11 Thread Nach
https://bugs.kde.org/show_bug.cgi?id=166697 --- Comment #7 from Nach <nac...@gmail.com> --- I agree with you the default should be what people see elsewhere so KDE doesn't seem alien. However I think KDE would be better with having this feature as an option (which is not the default) as it

[kfile] [Bug 166694] Drag and drop from one places menu to another needs a smart context menu

2018-04-11 Thread Nach
https://bugs.kde.org/show_bug.cgi?id=166694 --- Comment #2 from Nach <nac...@gmail.com> --- I'm not entirely convinced some kind of context menu when dragging and dropping these isn't helpful, but I do agree that since the early KDE 4, things are much better now. The ability to edit an

[kfile] [Bug 166697] KDE4 file dialogs is missing seperate folders view

2018-04-11 Thread Nach
https://bugs.kde.org/show_bug.cgi?id=166697 --- Comment #5 from Nach <nac...@gmail.com> --- >If you want folders separate in your open/save panels, they can be sorted that >way: click the settings icon in the top-right corner of the window, then go to >Sorting, then check

[kfile] [Bug 166697] KDE4 file dialogs is missing seperate folders view

2018-04-11 Thread Nach
https://bugs.kde.org/show_bug.cgi?id=166697 --- Comment #3 from Nach <nac...@gmail.com> --- If you don't want to add the feature, that's fine, but your reason doesn't add up. >where the primary purpose is to navigate to a specific window, folder, or file It's easier to navi

[valgrind] [Bug 342040] Valgrind mishandles clone with CLONE_VFORK | CLONE_VM that clones to a different stack

2016-12-13 Thread Nach
https://bugs.kde.org/show_bug.cgi?id=342040 --- Comment #7 from Nach <nac...@gmail.com> --- I ran a bunch more tests to ensure stability with the stack in the child. It's not using the exact stack the parent is specifying to use (beyond setting some a few bytes at the top of it), whi

[valgrind] [Bug 342040] Valgrind mishandles clone with CLONE_VFORK | CLONE_VM that clones to a different stack

2016-12-08 Thread Nach
https://bugs.kde.org/show_bug.cgi?id=342040 --- Comment #4 from Nach <nac...@gmail.com> --- Hello Philippe, I double checked with Valgrind 3.12.0 to ensure the bug was still occuring (it was), and then applied your patch. The basic code I was testing no longer crashes and seems to be

[valgrind] [Bug 342040] Valgrind mishandles clone with CLONE_VFORK | CLONE_VM that clones to a different stack

2016-08-28 Thread Nach via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=342040 Nach <nac...@gmail.com> changed: What|Removed |Added CC||nac...@gmail.com --- Comment #