GitLab

BUG: 443618

It's KF5Bookmarks, not KF5KBookmarks

Waqar Ahmed authored Nov 01, 2021 and Christoph Cullmann committed Nov 02, 2021

Very annoying to change the command every time if you are in a
non-github-like git workflow (e.g., gerrit).

Also, use mono font in the dialog since thats what is normally used for
commands and is more readable.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

(cherry picked from commit 7618d41f)

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Currently we ignore anything that is not a word. This makes
ctrl-clicking on a user defined operator or jumping to a destructor.

Instead, just check for a valid wordRange at the current position and
let lsp tell us what's right and wrong.

David Edmundson authored Oct 25, 2021 and Christoph Cullmann committed Oct 26, 2021

Kate has it's own version of org.freedesktop.Application spec and
KDBusAddons handling. It needs to pass the activation token explicitly.

The launched (second) instance will have an environment variable
XDG_ACTIVATION_TOKEN set, we need to pass this value to the existing
application before it can set the window to activate.

Testing done: clicked on a file in dolphin, kate got focus

David Edmundson authored Oct 25, 2021 and Christoph Cullmann committed Oct 25, 2021

On wayland this is uneeded as the popups are always kept on screen using
a semantic positioning system.

It's also wrong as the client considers itself at 0,0, even if it's not.
So any attempts to help only make things worse.

David Edmundson authored Oct 25, 2021 and Christoph Cullmann committed Oct 25, 2021

Otherwise we are slightly wasteful on all platforms. On wayland it is
problematic as QtWayland does not currently support popup repositioning.

It looks like show() code was moved early so that we would have the size
ahead of positioning, but there is another way to achieve that. This is
the method that QMenu uses internally.

BUG: 443895

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

avoid that after initial triggering this repaint and
more of main window is destroyed

BUG: 440583

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Waqar Ahmed authored Oct 11, 2021 and Christoph Cullmann committed Oct 23, 2021

This change is a proposal to replace viewing the commit diff in a
tooltip with a treeview. Currently, you click on a commit and it opens
up a tooltip with the whole commit diff. This makes it a little bit
harder to use if your commit touched a lot of files or was large in
general.

With this change, once you click on a commit a temporary toolview  will be
created with list of all files from the commit. A user can then click on
a file to view the diff for that particular file in the commit.

This is a quickly done implementation so likely needs a lot of
refinements and tuning. Also, a lot of code is copied from the
CompareBranchView so we should probably find a way to remove this
duplication.

To make sure the relevant codepaths have CI coverage

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

For e.g., flto, fsanitize

Much better than working with focus.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Most of the warning fixes are about range-for usage.

Fabian Kosmale authored Sep 18, 2021 and Christoph Cullmann committed Oct 09, 2021

This adds a custom menu entry to the diagnostics' context menu, which
simply copies the diagnostic message to the clipboard.

The targeted use cases are to ease the "make mistake → search for
mistake → find (wrong) solution online" workflow, as well as being able
to copy wrong warnings when reporting bugs against a LSP server
implementation.

Waqar Ahmed authored Sep 19, 2021 and Christoph Cullmann committed Oct 09, 2021

This change introduces a new plugin: Compiler Explorer. The main purpose
of this plugin is to allow you to view the generated code of any file
in your project easily. You can do that in Compiler-Explorer but it
takes a lot more effort and you have to copy over flags etc.

Besides the plugin itself, there is a major change packed in i.e., the
ability to allow *any* QWidget in Kate's tabs.

Ahmad Samir authored Oct 07, 2021 and Christoph Cullmann committed Oct 09, 2021

Less explicit new/delete.