On Fri, 23 Sep 2011 19:52:24 +0200
Thomas Martitz thomas.mart...@student.htw-berlin.de wrote:
Am 21.09.2011 18:01, schrieb Dimitar Zhekov:
What you need is debug sessions, and they depend on the executable being
debugged. It doesn't make sense to use the same breakpoints, watches
etc.
Am 21.09.2011 18:01, schrieb Dimitar Zhekov:
On Wed, 21 Sep 2011 17:18:14 +0400
Alexander Petukhovde...@apetukhov.ru wrote:
What I wanted was to have debug settings loaded at the same time I open
files I worked with last time. [...] but now I realize that I can store
debug settings for a
I agree that user doesn't have to open a project to be able to use
debugging and
settings are better be saved between geany startups.
What I wanted was to have debug settings loaded at the same time I open
files I worked with last time.
And I kept in mind that there can be several
On Wed, 21 Sep 2011 17:18:14 +0400
Alexander Petukhov de...@apetukhov.ru wrote:
What I wanted was to have debug settings loaded at the same time I open
files I worked with last time. [...] but now I realize that I can store
debug settings for a session in plugins own config, where all other
Am 19.09.2011 11:13, schrieb Lex Trotman:
On 19 September 2011 18:38, Alexander Petukhovde...@apetukhov.ru wrote:
I would like to store debugger settings such as watches, breaks, target etc
in a project file.
These are not the settings that apply to a plugin in a whole but look like
being
On 19 September 2011 18:38, Alexander Petukhov de...@apetukhov.ru wrote:
I would like to store debugger settings such as watches, breaks, target etc
in a project file.
These are not the settings that apply to a plugin in a whole but look like
being related to files
user is working with, i.e.
