Dear All,
I am always using geany, but now this is the first time I prepare to look at geany source code. I have one question about memory allocation. When we open one new file, there will be one new tag in geany. How could I track all memory allocation(g_malloc) related with this tag? Or would it be possible to track all related functions with this tag?
Thank you very much!
Best Regards,
Pengfei
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/682
It saves a lot of time if the right click context menu on a misspelt word has the spelling suggestions right up top of the context menu (like I see right now with Firefox and SublimeText and other editors.)
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/681
Really libraries should not display errors, they should return error messages to the caller so the caller can decorate it with whatever more information they have.
So spawn_* would return the generic "Failed to find the executable" and the grep caller would combine to make a message like "Failed to execute 'grep': Failed to find executable".
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/541#issuecomment-146689159
The last part, "CreateProcess() failed: The system cannot find the file specified.", is generated by spawn_*(). Normally it would be the error text only, but spawn_*() is a complex call, with several other (though unlikely) points of failure, thus the function name.
As of the executable name, only the caller really knows whether it's locale or UTF-8 (having a locale names does not guarantee that all names are locale, that's a basic error in Geany). So spawn_*() is encoding-agnostic, but a GError message must be in UTF-8, and thus the executable is not included.
That is not to say that I'm against more sensible messages - we even discussed it while polishing spawn, but could not reach any sensible conclusion. Perhaps it would be best to display user-friendly messages based on the most likely error, and put the full details in the Status tab, or Debug -> Messages.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/541#issuecomment-146603760
Especially under Windows, there are 32-bit and 64-bit stat, and
g_[l]stat may use the non-default one.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/677
-- Commit Summary --
* g_[l]stat require a GStatBuf argument, not struct stat
-- File Changes --
M src/dialogs.c (2)
M src/document.c (6)
M src/socket.c (2)
M tagmanager/ctags/ctags.c (18)
M tagmanager/src/tm_source_file.c (4)
M tagmanager/src/tm_workspace.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/677.patchhttps://github.com/geany/geany/pull/677.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/677
Copied from #677, @codebrainz said:
"If anyone remembers, we should probably cleanup that part that was guarded out before and the other blocks mentioned, as well the mixed use of guarded and non-guarded includes of sys/types.h and such, which probably could be replaced by GLib types as well (ex. goffset, etc)."
This issue created as a reminder.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/680
Copied from [SourceForge](http://sourceforge.net/p/geany/bugs/835/):
When I have both auto-save and also strip trailing spaces turned on, I find a couple of problems if I am typing when auto-save triggers (i.e. quite often).
* If I am just about to type at the start of a new line when the auto save triggers then the current indent disappears and my cursor is left at the beginning of the line.
* If auto-save triggers while typing and I have just typed a space that space will disappear and my typing will continue, error included.
I can see this is consequence of my choice of preferences, but I still think there is a case for improvement here. The simple solution (without knowing the codebase at all) would seem to be to turn off the stripping temporarily for auto-saves. Is this possible?
And yes, I know it is 2012 but I have found myself in a situation where auto-save is a necessity :(
Geany 0.21.
Today it is 2015, Geany 1.25, everything is in place.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/678
Unless I'm forgetting something, all arguments in all spawn_*() functions are used.
Perhaps you mean utils_spawn()? These were wrappers to g_spawn/win32_spawn with some unused parameters, and are now wrappers for spawn_*() with even more unused parameters. We should deprecate them at some point...
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/440#issuecomment-146270115