How about $project.geany.d?
;)
On 18/11/2013 10:12, Lex Trotman wrote:
2. various names were suggested, but no clear winner emerged,
suggestions included $project.geany, geany.$project and $project.conf.d.
Objections included $project.geany is the existing name and may be
confused or overwrit
not such a big deal IMHO..
Thomas
On 23/01/13 11:17, Lex Trotman wrote:
On 23 January 2013 20:14, Thomas Young wrote:
Hi Lex,
For myself, yes, I'd definitely say that missing keywords is worse than
extras.
And just including all of these as keywords seems fine.
As an aside note that I q
Hi Lex,
For myself, yes, I'd definitely say that missing keywords is worse than
extras.
And just including all of these as keywords seems fine.
As an aside note that I quite often find myself getting stuff like local
variables and parameters coloured as keywords in wing, not because of
diffe
wrote:
On 13-01-22 12:15 AM, Thomas Young wrote:
(As an aside, for myself, I'm managed to hack something up that uses
libClang to lookup references, that doesn't need know about the whole
set of project files in order to work. It actually just executes the
corresponding compile comm
eturn result;
}
#include "base/Header.h"
#include "externalDependant/Clang/LookupReference.h"
#include "base/Container/ReplacementVector.h"
#include "base/Container/String.h"
#include
#include
#include
#include
#include
GeanyPlugin *geany
Hi all,
> One thing that's different from Geany from other IDEs I've used is that
> it doesn't have "files in the project" but rather just stores "where are
> the project's files" (ie. base path).
Right.
Speaking for myself, and the build setup I'm working with right now,
this actually suits me
ck_output(["geany", "--print-location"])
pos = output.rfind(':')
if not pos == -1:
command = "b " + output[:pos]
gdb.execute(command)
BreakPointAtEditorLocationCommand() #required to register command
Thomas
On 18/01/13 10:5
(doc->editor->sci, pos);
g_string_append_printf(location, "%s:%d:%d\n", filename, line +
1, col);
On 18/01/13 09:10, Thomas Young wrote:
Cheers Steve.
Ok, I changed spaces to tabs, and a patch from diff output is attached.
Will try and do things more properly next ti
Hi Lex,
> Don't forget to update the manual to include your new cl
> option.
How to do this?
I can see references to --list-documents in doc/geany.html and
doc/geany.txt, so I suppose we add a similar entry for the new option,
but I guess one of those files is generated from the other?
I at
On 17/01/13 21:13, Lex Trotman wrote:
On 18 January 2013 00:17, Thomas Young wrote:
Hello,
I've hacked a small change into Geany locally, to help with integration with
gdb.
Hi Thomas,
Have you tried the debugger plugin, it runs gdb and provides a GUI
interface in Geany. Its still rela
e doesn't do anything that geany didn't do already, since it just
mimics the existing code path and logic for the --list-documents command).
Best regards,
Thomas
On 17/01/13 21:13, Lex Trotman wrote:
On 18 January 2013 00:17, Thomas Young wrote:
Hello,
I've hacked a small ch
.org/Contribute/Developers
So far I've found the people on this project have been helpful and
friendly compared to my minor previous experiences with open source
projects.
Welcome :-)
Steven Blatnick
On 01/17/2013 06:17 AM, Thomas Young wrote:
Hello,
I've hacked a small change in
Hello,
I've hacked a small change into Geany locally, to help with integration
with gdb.
Basically, what I've done is to add a '--print-location' command line
option, which essentially just duplicates the functionality of the
existing '--list-documents' option (through main.c/h and socket.c/
13 matches
Mail list logo
