Hi, thanks for nice editor, I am working on Belarusian translation now.
Currently I use emacs or scite for my small C,C++,Python projects, Geany looks like a nice replacement to them but I lack several features.
1) Go to tag declaration/definition should use word pointed by mouse not cursor. Example:
foo() ba<cursor is here>r()
If I left click on "foo" and choose go to tag declaration, geany will try to find "bar" (I wish "foo")
2) Ability to jump to error line atfer compilation failed (using hotkey or by clicking on compiler output)
3) Project mangement (I don't require complicated stuff or GUI for editing it)
Project file can look like simple file with few record:
example: PROJECT_SOURCES = foo.c bar/bar.c MAKE_DIR = ~/projects/fooproj
When you load project it simply open all files in PROJECT_SOURCES. Also it would be nice to have MAKE_DIR variable for specifying makefile location because if I have structure like this:
bar/bar.c foo.c makefile
I will get "no makefile error" if I edit "bar.c" and try to hit build key.
5) Ability to call external program for word poined by cursor. (Will use for calling documentation browser)
6) Debuger support (I understand that this one is most complicated and unlikely be implemented)
On Sun, 11 Jun 2006 17:13:36 +0300, Yura Semashko yurand2@gmail.com wrote:
Hi,
- Go to tag declaration/definition should use word pointed by mouse
not cursor. Example:
foo() ba<cursor is here>r()
If I left click on "foo" and choose go to tag declaration, geany will try to find "bar" (I wish "foo")
This is already implemented in the current SVN version.
- Ability to jump to error line atfer compilation failed (using
hotkey or by clicking on compiler output)
As long as the file where the error occurred, it is already possible by double clicking on the appropriate line. How do you want to do this with a hotkey?
- Project mangement (I don't require complicated stuff or GUI for
editing it)
Project management is already on the ToDo list, it will come with 0.9 or so. Please be patient.
bar/bar.c foo.c makefile
I will get "no makefile error" if I edit "bar.c" and try to hit build key.
(I think this point should not belong to the project management item) Yes, this is a problem. Solution: project management ;-). Workaround: use make with own target and specify -f ../makefile as argument, then make will find the makefile. But this will fail if you edit foo.c. Sorry, this can only be solved by a project management. Or perhaps you can create a symlink in bar to ../makefile. But this is not very nice.
- Ability to call external program for word poined by cursor. (Will
use for calling documentation browser)
Ok, this is easy to implement. Nick, what do you think?
- Debuger support (I understand that this one is most complicated
and unlikely be implemented)
Hmm, I'm not sure whether Geany will ever have this. I don't want so big things in Geany. Perhaps after Geany 1.0, but only perhaps. Sorry.
Thanks for your mail.
Regards, Enrico
Hi, thanks for answer.
Here is patch for Belarusian translation I speak before:
ftp://ftp.berlios.de/pub/tw-light/belarusian.patch
On Sunday 11 June 2006 21:14, Enrico Tröger wrote:
- Go to tag declaration/definition should use word pointed by mouse
not cursor. Example:
foo() ba<cursor is here>r()
If I left click on "foo" and choose go to tag declaration, geany will try to find "bar" (I wish "foo")
This is already implemented in the current SVN version.
Just check, works fine ;-), thanks.
- Ability to jump to error line atfer compilation failed (using
hotkey or by clicking on compiler output)
As long as the file where the error occurred, it is already possible by double clicking on the appropriate line. How do you want to do this with a hotkey?
You don't jump if error is not in current file. For example if your curent file foo.c, and you make error in foo.h you won't jump to error.
"Next error" hotkey (F4 in scite), but this is not important from my point of view.
bar/bar.c foo.c makefile
I will get "no makefile error" if I edit "bar.c" and try to hit build key.
(I think this point should not belong to the project management item) Yes, this is a problem. Solution: project management ;-). Workaround: use make with own target and specify -f ../makefile as argument, then make will find the makefile. But this will fail if you edit foo.c. Sorry, this can only be solved by a project management. Or perhaps you can create a symlink in bar to ../makefile. But this is not very nice.
I workaround this problem by specify path to make tool as: "cd ~/projects/foo && /usr/bin/make" still waiting for project management.
- Debuger support (I understand that this one is most complicated
and unlikely be implemented)
Hmm, I'm not sure whether Geany will ever have this. I don't want so big things in Geany. Perhaps after Geany 1.0, but only perhaps. Sorry.
That is not important one.
On Mon, 12 Jun 2006 00:07:25 +0300, Yura Semashko yurand2@gmail.com wrote:
Hi, thanks for answer.
Here is patch for Belarusian translation I speak before:
ftp://ftp.berlios.de/pub/tw-light/belarusian.patch
Thanks a lot. It will be added soon.
- Ability to jump to error line atfer compilation failed (using
hotkey or by clicking on compiler output)
As long as the file where the error occurred, it is already possible by double clicking on the appropriate line. How do you want to do this with a hotkey?
You don't jump if error is not in current file. For example if your curent file foo.c, and you make error in foo.h you won't jump to error.
Ok, this is not yet possible. Be patient. I'll work on this.
"Next error" hotkey (F4 in scite), but this is not important from my point of view.
Will be implemented ;-).
Regards, Enrico
On Mon, 12 Jun 2006 00:07:25 +0300, Yura Semashko yurand2@gmail.com wrote:
- Ability to jump to error line atfer compilation failed (using
hotkey or by clicking on compiler output)
As long as the file where the error occurred, it is already possible by double clicking on the appropriate line. How do you want to do this with a hotkey?
You don't jump if error is not in current file. For example if your curent file foo.c, and you make error in foo.h you won't jump to error.
Works now in the SVN verson, but needs testing. It will jump to foo.h if it is open, if not it will be opened. But it can only be opened if it is found ;-). To be found, it has to be in the same directory like the file which was compiled.
At least with the gcc, the file foo.h can be in another directory, e.g. in a subdirectory, because gcc prints the relative path of foo.h to foo.c and so it also will be opened. Example: /foo.c /includes/foo.h
and you have an error in foo.h which is included in foo.c with #include "includes/foo.h" then Geany will switch/open this file.
Regards, Enrico
On Tuesday 13 June 2006 18:55, Enrico Tröger wrote:
You don't jump if error is not in current file. For example if your curent file foo.c, and you make error in foo.h you won't jump to error.
Works now in the SVN verson, but needs testing. It will jump to foo.h if it is open, if not it will be opened. But it can only be opened if it is found ;-). To be found, it has to be in the same directory like the file which was compiled.
At least with the gcc, the file foo.h can be in another directory, e.g. in a subdirectory, because gcc prints the relative path of foo.h to foo.c and so it also will be opened. Example: /foo.c /includes/foo.h
and you have an error in foo.h which is included in foo.c with #include "includes/foo.h" then Geany will switch/open this file.
Work, but have the following bug:
=========== foo.c ============== #include <stdio.h> #include "foo.h"
int main() { return 0; } =========== foo.h =============== int a(); jgh int b(); ==============================
Geany open foo.h fine, but in status window I see the following: "Could not open file ./In file included from foo.c (No such file or directory)"
That is because error output is: ================================ In file included from foo.c:2: foo.h:3: error: syntax error before "int" make: *** [main] Error 1 ================================
Here is a patch that fix this issue (I tested with gcc) not sure for other compilers error format.
Index: src/utils.c =================================================================== --- src/utils.c (revision 443) +++ src/utils.c (working copy) @@ -2318,7 +2318,7 @@ // empty.h:4: Warnung: type defaults to `int' in declaration of `foo' // empty.c:21: error: conflicting types for `foo' pattern = ":"; - field_min_len = 3; + field_min_len = 4; field_idx_line = 1; field_idx_file = 0; break;
Another feature that will make me happy is ability to show only error summary after compilation (Only strings that can be used for jump to error line).
Syntax error are very simple most time and I don't need to watch full compiler output for them.
so I want only
foo.h:3: error: syntax error before "int"
in previous example.
On Wed, 14 Jun 2006 02:20:23 +0300, Yura Semashko yurand2@gmail.com wrote:
On Tuesday 13 June 2006 18:55, Enrico Tröger wrote:
You don't jump if error is not in current file. For example if your curent file foo.c, and you make error in foo.h you won't jump to error.
Works now in the SVN verson, but needs testing. It will jump to foo.h if it is open, if not it will be opened. But it can only be opened if it is found ;-). To be found, it has to be in the same directory like the file which was compiled.
At least with the gcc, the file foo.h can be in another directory, e.g. in a subdirectory, because gcc prints the relative path of foo.h to foo.c and so it also will be opened. Example: /foo.c /includes/foo.h
and you have an error in foo.h which is included in foo.c with #include "includes/foo.h" then Geany will switch/open this file.
Work, but have the following bug:
[...] Geany open foo.h fine, but in status window I see the following: "Could not open file ./In file included from foo.c (No such file or directory)"
Here is a patch that fix this issue (I tested with gcc) not sure for other compilers error format.
Applied, thank you.
Another feature that will make me happy is ability to show only error summary after compilation (Only strings that can be used for jump to error line). Syntax error are very simple most time and I don't need to watch full compiler output for them.
so I want only
foo.h:3: error: syntax error before "int"
in previous example.
Ok, maybe. But at the moment I want to concentrate on other things. I'll write it down.
regards, Enrico