[Geany-Devel] Link to ChangeLog on website still pointing to 1.22.0
Good morning guys! Maybe someone is able to update the link here: http://www.geany.org/Documentation/ChangeLog I'm at work and don't have my password here for the login to the admin interface. ;) Best Regards, Dominic -- Diese E-Mail ist nicht mit GPG signiert, da ich sie vom Webinterface aus geschrieben habe. This mail is not signed with GPG because I wrote it from web interface. ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] Link to ChangeLog on website still pointing to 1.22.0
On 12/03/2013 09:18, Dominic Hopf wrote: Good morning guys! Maybe someone is able to update the link here: http://www.geany.org/Documentation/ChangeLog I'm at work and don't have my password here for the login to the admin interface. ;) Done ;-) ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] Changing terminate signal for stopping executing programs
On 13 March 2013 04:47, Dimitar Zhekov dimitar.zhe...@gmail.com wrote: On Mon, 11 Mar 2013 13:18:10 +1100 Lex Trotman ele...@gmail.com wrote: Geany currently uses SIGQUIT to terminate a running program (using the execute menu item or toolbar button when it shows the stop icon). This has always been the case since the stop button was added. There is a big comment in the code explaining why SIGQUIT is used, and its problems: /* Unix: SIGQUIT is not the best signal to use because it causes a core dump (this should not * perforce necessary for just killing a process). But we must use a signal which we can * ignore because the main process get it too, it is declared to ignore in main.c. */ ... My understanding of Unix/Linux signals is that the comment above is wrong and always has been wrong, a signal sent to a child process by a parent process does not get delivered to the parent. When you execute a gdb -exec-interrupt command in debugger or Scope, a SIGINT is sent to the inferior, and to gdb, and to Geany. But if you start gdb from a terminal, the signal is sent to inferior only. debugger moves gdb/inferior to a new process group, which sometimes fails. Sounds like -exec-interrupt is sending to the process group, (see kill(2) with a negative number) which it would have inherited from Geany and so includes Geany in it. Scope disables SIGINT in Geany while debugging. glib spawn is much more complex than a normal fork/exec... And mysterious, unless you read the source, but then you can't rely on that either. Cheers Lex -- E-gards: Jimmy ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
[Geany-Devel] Setting Windows working directory
Hi Enrico, We have had a report on IRC that running geany on the windows command line will only open files in the Geany install directory unless you use the full path. eg C:\somepath geany somefile.txt will open installpath\somefile.txt not somepath\somefile.txt. And with the Open new documents from the command line option set it creates somefile.txt in the install dir since it doesn't exist there. Suspicion is falling on https://github.com/geany/geany/commit/775ef628688c69de34640e12666aed5762a80dff As the most experienced windowser (and the committer of that change) could you look at it please? Cheers Lex ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
