Go to file
Havoc Pennington c6a3df0474 change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it
2002-01-17  Havoc Pennington  <hp@redhat.com>
	* gtk/gtktextview.c (gtk_text_view_move_cursor_internal): change
	GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it
	starts to go up/down paragraphs. This makes Ctrl+Up/Ctrl+Down work
	as in the keynav spec, though it makes the interpretation of
	GTK_MOVEMENT_PARAGRAPHS different from the interpretation of some
	of the other GTK_MOVEMENT_ thingies, maybe, as if that enum makes
	any sense anyhow.
2002-01-18 00:45:50 +00:00
contrib
debian
demos Append EXEEXT to ../gdk-pixbuf/gdk-pixbuf-csource. 2002-01-01 22:17:09 +00:00
docs tiny markup fix 2002-01-17 23:04:19 +00:00
examples
gdk Move here, and save/restore the X error handler to allow people using GTK+ 2002-01-17 20:45:23 +00:00
gdk-pixbuf Credit Michael Hore for last two changes 2002-01-12 00:26:25 +00:00
gtk change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it 2002-01-18 00:45:50 +00:00
m4macros
modules 1.3.12, interface, binary age 0. 2001-12-23 22:59:30 +00:00
po Updated Ukrainian translation 2002-01-16 15:11:21 +00:00
tests allow cancel to happen. 2002-01-14 22:00:26 +00:00
.cvsignore
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it 2002-01-18 00:45:50 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it 2002-01-18 00:45:50 +00:00
ChangeLog.pre-2-2 change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it 2002-01-18 00:45:50 +00:00
ChangeLog.pre-2-4 change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it 2002-01-18 00:45:50 +00:00
ChangeLog.pre-2-6 change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it 2002-01-18 00:45:50 +00:00
ChangeLog.pre-2-8 change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it 2002-01-18 00:45:50 +00:00
ChangeLog.pre-2-10 change GTK_MOVEMENT_PARAGRAPHS to go to start/end of paragraph before it 2002-01-18 00:45:50 +00:00
config.guess
config.h.win32.in
config.sub
configure.in Fix typo in --help output. (Arnaud Charlet). 2002-01-16 15:55:38 +00:00
COPYING
gdk-2.0-uninstalled.pc.in
gdk-2.0.pc.in
gdk-pixbuf-2.0-uninstalled.pc.in
gdk-pixbuf-2.0.pc.in
gtk-config-2.0.in
gtk-zip.sh.in
gtk+-2.0-uninstalled.pc.in
gtk+-2.0.pc.in
gtk+.spec.in
HACKING
INSTALL 1.3.12, interface, binary age 0. 2001-12-24 01:49:19 +00:00
INSTALL.in
makecopyright
Makefile.am
NEWS 1.3.12, interface, binary age 0. 2001-12-23 22:59:30 +00:00
NEWS.pre-1-0
README 1.3.12, interface, binary age 0. 2001-12-24 01:49:19 +00:00
README.cvs-commits
README.in
README.nanox
README.win32
sanity_check
TODO
TODO.xml

General Information
===================

This is GTK+ version 1.3.12. GTK+, which stands for the Gimp ToolKit, 
is a library for creating graphical user interfaces for the X Window 
System. It is designed to be small, efficient, and flexible. GTK+ is 
written in C with a very object-oriented approach.

The official ftp site is:
  ftp://ftp.gtk.org/pub/gtk

The official web site is:
  http://www.gtk.org/

Information about mailing lists can be found at
  http://www.gtk.org/mailinglists.html

Installation
============

See the file 'INSTALL'

How to report bugs
==================

Bugs should be reported to the GNOME bug tracking system. 
(http://bugzilla.gnome.org, product gtk+.) You will need
to create an account for yourself.
  
In the bug report please include:
  
* Information about your system. For instance:

   - What operating system and version
   - What version of X
   - For Linux, what version of the C library

  And anything else you think is relevant.

* How to reproduce the bug. 

  If you can reproduce it with the testgtk program that is built 
  in the gtk/ subdirectory, that will be most convenient.  Otherwise, 
  please include a short test program that exhibits the behavior. 
  As a last resort, you can also provide a pointer to a larger piece 
  of software that can be downloaded.

* If the bug was a crash, the exact text that was printed out
  when the crash occured.

* Further information such as stack traces may be useful, but
  is not necessary. If you do send a stack trace, and the error
  is an X error, it will be more useful if the stacktrace
  is produced running the test program with the --sync command
  line option.

Patches
=======

Patches should also be submitted to bugzilla.gnome.org. If the
patch fixes an existing bug, add the patch as an attachment
to that bug report.

Otherwise, enter a new bug report that describes the patch,
and attach the patch to that bug report.

Bug reports containing patches should include the PATCH keyword
in their keyword fields. If the patch adds to or changes the GTK
programming interface, the API keyword should also be included.
  
Patches should be in unified diff form. (The -u option to GNU
diff.)