source: trunk/third/gedit/README @ 18815

Revision 18815, 3.9 KB checked in by ghudson, 22 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r18814, which included commits to RCS files with non-trunk default branches.
Line 
1General Information
2===================
3
4This is version 2.2.0.1 of gedit. gedit is a small and lightweight UTF-8 text
5editor for the GNOME environment.
6
7Designed for the X Window System, it uses the GTK+ 2.0 and GNOME 2.0 libraries.
8Complete GNOME integration is featured, with support for Drag and Drop (DnD)
9between Nautilus (the GNOME file manager) and the use of the GNOME help system,
10the GNOME Virtual File System and the GNOME print framework.
11
12gedit uses a Multiple Document Interface (MDI), which lets you edit more than
13one document at the same time.
14
15gedit supports most standard editing features, plus several not found in your
16average text editor (plugins being the most notable of these).
17
18Although new features are always under development, currently gedit has these
19features:
20
21    * Complete support for UTF-8 text
22    * File Revert
23    * Read files using the GNOME VFS
24    * Cut/Copy/Paste and Select All text
25    * Complete integration with the GNOME Environment
26    * Search and Replace
27    * A complete preferences interface
28    * Configurable Plugins system
29    * Accepts input from command line pipes ( i.e. "ls | gedit" )
30    * Printing and Print Previewing Support
31    * Configurable levels of Undo/Redo
32
33Some of the plugins, packaged and installed with gedit include, among others:
34
35    * ASCII table
36    * Compare files
37    * Word count
38    * Tag list
39    * Insert Date/Time
40    * Shell output
41    * Spell checker
42
43gedit is released under the GNU General Public License (GPL) version 2, see
44the file 'COPYING' for more information.
45
46
47The official web site is:
48
49    http://gedit.sourceforge.net
50
51You can dowload the latest gedit tarball from the gnome ftp server:
52
53    ftp://ftp.gnome.org
54
55Information about gedit mailing lists can be found at
56
57    http://sourceforge.net/mail/?group_id=7   
58
59
60Installation
61============
62
63gedit requires GTK+-2.2.x and the GNOME 2.2.x libraries.
64
65Simple install procedure:
66
67  % gzip -cd gedit-2.2.0.1.tar.gz | tar xvf -    # unpack the sources
68  % cd gedit-2.2.0.1                       # change to the toplevel directory
69  % ./configure                            # run the `configure' script
70  % make                                   # build gedit
71  [ Become root if necessary ]
72  % make install                           # install gedit
73
74See the file 'INSTALL' for more detailed information.
75
76
77How to report bugs
78==================
79
80Bugs should be reported to the GNOME bug tracking system.
81(http://bugzilla.gnome.org, product gedit.) You will need to create an
82account for yourself.
83
84You can also report bugs using the GNOME program bug-buddy.
85 
86In the bug report please include:
87 
88* Information about your system. For instance:
89
90   - What operating system and version
91   - What version of X
92   - What version of the gtk+, glib and gnome libraries
93   - For Linux, what version of the C library
94
95  And anything else you think is relevant.
96
97* How to reproduce the bug.
98
99* If the bug was a crash, the exact text that was printed out when the
100  crash occured.
101
102* Further information such as stack traces may be useful, but is not
103  necessary. If you do send a stack trace, and the error is an X error,
104  it will be more useful if the stacktrace is produced running the test
105  program with the --sync command line option.
106
107See the file 'BUGS' for the list of known bugs.
108
109
110Patches
111=======
112
113Patches should also be submitted to bugzilla.gnome.org. If the patch
114fixes an existing bug, add the patch as an attachment to that bug
115report.
116
117Otherwise, enter a new bug report that describes the patch, and attach
118the patch to that bug report.
119
120Bug reports containing patches should include the PATCH keyword in their
121keyword fields.
122 
123Patches should be in unified diff form. (The -u option to GNU diff.)
124
125If you are interested in helping us to develop gedit, please see the
126file 'AUTHOR' for contact information and/or send a message to the gedit
127mailing list. See also the file 'HACKING' for information about our
128CVS guidelines and the file 'TODO' for a list of todos.
129
130
131
132The gedit team.
133
Note: See TracBrowser for help on using the repository browser.