mirror of https://github.com/GNOME/gimp.git
![]() 2000-05-10 Michael Natterer <mitch@gimp.org> Another try to get the signal/dead child recovery stuff right. Could the brave signal crew (TM) (Austin, Garry, Raphael, Tim) please do bad tests to the new code? I removed all strange constants (SA_NODEFER etc.) and used only glib and POSIX stuff. * app/main.c * libgimp/gimp.c: - Call gimp_signal_private() with no flags to enforce a proper sigaction() behaviour (block signals while handler is active). - Removed the reentrancy guards from the handlers. - Renamed the handlers. - Ignore SIGPIPE in the app and in plugins. - Re-introduced the SIGCHLD handler because it should work now. Also added a SIGCHLD handler to libgimp/gimp.c. * app/errors.c * libgimp/gimp.c: in the signal handler, unblock all signals with sigprocmask() before calling g_on_error_query() because gdb otherwise inherits the blocked signals and does nothing. Wrapped the statements with "if (TRUE) { }" blocks so it's easy to make the stack trace a command line option. * app/plug_in.c * libgimp/gimp.c: listen for G_IO_ERR and G_IO_HUP on the read channels. In the app, pop up an error message and clean up the plugin. In plugins, clean up and exit. * libgimp/gimpwire.c: removed the "plug-in chrashed?" message and print the program's name with all error messages. * plug-ins/helpbrowser/helpbrowser.c: typo. |
||
---|---|---|
RPM | ||
app | ||
cursors | ||
data | ||
debian | ||
devel-docs | ||
docs | ||
etc | ||
help | ||
libgimp | ||
libgimpbase | ||
libgimpwidgets | ||
modules | ||
pixmaps | ||
plug-ins | ||
po | ||
po-libgimp | ||
po-plug-ins | ||
po-script-fu | ||
tips | ||
tools | ||
.cvsignore | ||
AUTHORS | ||
COPYING | ||
ChangeLog | ||
ChangeLog.plug-ins | ||
ChangeLog.pre-1-0 | ||
HACKING | ||
INSTALL | ||
MAINTAINERS | ||
Makefile.am | ||
NEWS | ||
PLUGIN_CVS | ||
PLUGIN_MAINTAINERS | ||
README | ||
README.i18n | ||
README.patch_xinput_airbrush | ||
README.perl | ||
README.win32 | ||
TODO | ||
acconfig.h | ||
acinclude.m4 | ||
autogen.sh | ||
config.guess | ||
config.h.in | ||
config.h.win32 | ||
config.sub | ||
configure.in | ||
gimp.1 | ||
gimp.m4 | ||
gimp.spec | ||
gimp1_0_splash.ppm | ||
gimp_logo.ppm | ||
gimp_splash.ppm | ||
gimprc-1.2.5.in | ||
gimprc.5.in | ||
gimprc.in | ||
gimprc.win32 | ||
gimprc_user.in | ||
gimptool-1.2.in | ||
gimptool.1 | ||
gimptool.in | ||
gtkrc | ||
ltconfig | ||
ltmain.sh | ||
patch_xinput_airbrush | ||
ps-menurc | ||
rmshm | ||
unitrc | ||
user_install | ||
user_install.bat |
README
The GIMP: The GNU Image Manipulation Program ============================================ This is an unstable release of the GIMP, intended for developers only. For production use, please use the 1.0.x series. The GIMP is designed to be a professional image manipulation program for both print and on-line based outputs. For installation instructions, see the file INSTALL. 1. Web Resources ================ The GIMP's home page is at: http://www.gimp.org/ Please be sure to visit this site for information, documentation, tutorials, news, etc. All things GIMP-ish are available from there. The automated plug-in registry is located at: http://registry.gimp.org/ There you can get the latest versions of plug-ins using a convenient forms-based interface. The latest version of The GIMP can be found at: http://www.gimp.org/download/ 2. Mailing Lists ================ We have several mailing lists dedicated to GIMP user and development discussion. To subscribe, send an empty message to <listname>-subscribe@xcf.berkeley.edu substituting <listname> for "gimp-user", "gimp-announce" or "gimp-developer" (without the quotes, of course) depending on the list you want to subscribe to. The mailing list archives can be found at: http://www.egroups.com/messages/gimp-developer/ http://www.egroups.com/messages/gimp-user/ Gimp-user is a mailing list dedicated to user problems, hints and tips, discussion of cool effects, etc. Gimp-announce is a low-traffic list with announcements about new releases of GIMP and plug-ins. Gimp-developer is oriented to GIMP core and plug-in developers. Most people will only want to be subscribed to gimp-user. If you want to help develop The GIMP, the gimp-developer mailing list is a good starting point. There are two mailing lists dedicated to the Win32 port, "gimpwin-users" and "gimpwin-dev". Especially the latter also carries traffic about the GTk+ port to Win32 in general. To subscribe, send an empty message to gimpwin-users-subscribe@egroups.com or gimpwin-dev-subscribe@egroups.com respectively. You can also use the web interface at http://www.egroups.com/group/gimpwin-users/ and http://www.egroups.com/group/gimpwin-dev/ . Note that as these mailing lists are hosted on egroups.com, the messages from the list contain relatively unintrusive and easily ignored advertisements at the end. But if you are absolutely allergic to ads, don't subscribe. 3. IRC ====== And finally, for the real junkies, there is an IRC channel devoted to the GIMP. On Byxnet (a private mostly-GIMP network) there is #gimp. Many of the developers hang out there. One of the Byxnet servers are: irc.gimp.org:6667 4. Customizing ============== The look of GIMP's interface can be customized like any other GTK app by editing the ~/.gtkrc file or by using "themes" (ready-made customizations). For downloadable themes and further details, see http://gtk.themes.org. Additionally GIMP reads ~/.gimp-1.1/gtkrc so you can have settings that only apply to The GIMP. Included is a set of keybindings similar to those in Adobe Photoshop (tm). You can find them in the ps-menurc file. To use them, copy this file to ~/.gimp-1.1/menurc. You can also manually change the keybindings to any of your choice by editing ~/.gimp-1.1/menurc. 5. Bugs ======= We sincerely hope you enjoy the program. Please report problems to bugs@gimp.org. Before reporting a problem, you may want to see if someone else did already - check http://bugs.gnome.org/db/pa/lgimp.html for this. Have fun, Spencer Kimball Peter Mattis Federico Mena Manish Singh