Alain Laporte authored Jun 17, 2022 and Christoph Cullmann committed Jun 18, 2022

Problematic case:

class class1

Alain Laporte authored Jun 08, 2022 and Christoph Cullmann committed Jun 18, 2022

To know where the method must be in the tree

alter config key, too, to swap value for existing configs

ATM if you start kate via

kate -n -s sjdfjskljfklsjdlf

and the session doesn't exist, even the default plugin
loading state is lost

CCBUG: 436085

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"

CCBUG: 454864

Alain Laporte authored May 29, 2022 and Christoph Cullmann committed Jun 11, 2022

Use only regexp to:
* extract name and parameters
* detect if function is a method or not

BUG: 454582

Héctor Mesa Jiménez authored May 01, 2022 and Christoph Cullmann committed Jun 10, 2022

Profiles for:
- delve (go)
- debugpy (python)
- perl language server

Profiles are defined in a resource json file, but can be overriden in a
user config file (<user config>/gdbplugin/dap.json).

A profile allows to define variables, which will be shown at the GUI
panel. The format variable is:

	${variable}
	${variable.name}
	${#variable.name}

A variable is considered as a string, but can be transformed using
filters:

	${variable|list} -> transform to a string list (parsed as a list
of arguments)
	${variable|int} -> transform to integer
	${variable|bool} -> transform to boolean
	${variable|base} -> consider the variable a file, and return a
basename
	${variable|dir} -> consider the variable a file, and return the
parent directory

There are 6 special variables:

- ${file}: use the GDB profile widget for the executable path.
- ${workdir}: use the GDB profile widget for the working directory.
- ${args}: use the GDB profile widget for the arguments.
- ${pid}: use an integer input widget.
- ${#run.host} -> reference to the json attribute "run.host"
- ${#run.port} -> reference to the json attribute "run.port"

The bottom-panel allows to choose the backend (GDB or a DAP server).
The input widgets are adapted to match the variables in the selected
profile.

In the lateral panel, variables a grouped by scopes (provided by the
client).

Debugging actions are enabled only if the client supports them.

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"

Alain Laporte authored Jun 02, 2022 and Christoph Cullmann committed Jun 06, 2022

Currently, some cases are not well handled

Alain Laporte authored May 29, 2022 and Christoph Cullmann committed Jun 06, 2022

Other types can be add to the class enum according to parsers which will use it

Alain Laporte authored May 30, 2022 and Christoph Cullmann committed Jun 06, 2022

To avoid a cast

Alain Laporte authored May 29, 2022 and Christoph Cullmann committed Jun 06, 2022

Tested class declarations:

class Philosopher:
class AustralianPhilosopher(Philosopher, default_name="Bruce"):
class Meta():
class MyClass(metaclass=Meta):
class MySubclass(MyClass):

Fix case where AustralianPhilosopher is not detected

ISSUE: #75

BUG: 454545

Mark Nauwelaerts authored Jun 04, 2022 and Christoph Cullmann committed Jun 06, 2022

... now that server manager lifetime is handled at higher plugin level