2022-07-16 22:30:36 +00:00
|
|
|
gedit
|
|
|
|
=====
|
2000-06-06 07:54:55 +00:00
|
|
|
|
2023-04-11 14:00:00 +00:00
|
|
|
gedit is an easy-to-use and general-purpose text editor. Its development started
|
|
|
|
in 1998, at the beginnings of the GNOME project, with a good integration with
|
|
|
|
that desktop environment.
|
2002-05-03 09:40:14 +00:00
|
|
|
|
2023-04-11 14:00:00 +00:00
|
|
|
You can use it to write simple notes and documents, or you can enable more
|
|
|
|
advanced features that are useful for software development.
|
2002-05-03 09:40:14 +00:00
|
|
|
|
2023-10-24 14:00:01 +00:00
|
|
|
See the [gedit website](https://gedit-technology.github.io/apps/gedit/) for more
|
|
|
|
information.
|
2004-08-01 17:41:13 +00:00
|
|
|
|
readme: big update, simplify
Throughout the file: better use the Markdown syntax (GitLab renders it).
In order in the diff:
Intro:
- Take the same description as in the AppData file. There is anyway more
information on the website. To not have many different gedit
descriptions a bit everywhere (more difficult to update at all the
places).
- For the programming languages used, it's explained in
docs/gedit-development-getting-started.md.
Resources:
- all the links are available on the website.
Installation:
- Have a separate Dependencies section, and refer to the meson.build
file, it will simplify the maintenance, to have the list of deps in only
one place, no need to update the version numbers in both places (in the
past the readme file was frequently outdated, so it was worse).
- Simpler install procedure with Meson, with the 3 commands taken from:
https://mesonbuild.com/Quick-guide.html
- Don't explain how to extract the tarball, if someone wants to compile
gedit from source, the person hopefully knows that it's needed to
extract the tarball first (also to be able to read the readme file).
Contributions:
- Don't duplicate infos from the hacking file.
2019-08-26 05:20:24 +00:00
|
|
|
License
|
|
|
|
-------
|
2004-08-01 17:41:13 +00:00
|
|
|
|
2015-08-22 11:29:15 +00:00
|
|
|
gedit is released under the GNU General Public License (GPL) version 2 or
|
2019-08-28 05:16:12 +00:00
|
|
|
later, see the file [COPYING](COPYING) for more information.
|
2002-05-03 09:40:14 +00:00
|
|
|
|
readme: big update, simplify
Throughout the file: better use the Markdown syntax (GitLab renders it).
In order in the diff:
Intro:
- Take the same description as in the AppData file. There is anyway more
information on the website. To not have many different gedit
descriptions a bit everywhere (more difficult to update at all the
places).
- For the programming languages used, it's explained in
docs/gedit-development-getting-started.md.
Resources:
- all the links are available on the website.
Installation:
- Have a separate Dependencies section, and refer to the meson.build
file, it will simplify the maintenance, to have the list of deps in only
one place, no need to update the version numbers in both places (in the
past the readme file was frequently outdated, so it was worse).
- Simpler install procedure with Meson, with the 3 commands taken from:
https://mesonbuild.com/Quick-guide.html
- Don't explain how to extract the tarball, if someone wants to compile
gedit from source, the person hopefully knows that it's needed to
extract the tarball first (also to be able to read the readme file).
Contributions:
- Don't duplicate infos from the hacking file.
2019-08-26 05:20:24 +00:00
|
|
|
Dependencies
|
|
|
|
------------
|
2002-05-03 09:40:14 +00:00
|
|
|
|
2024-06-18 22:07:11 +00:00
|
|
|
gedit depends on GTK 3 and
|
|
|
|
[Gedit Technology](https://gedit-technology.github.io/).
|
2002-05-03 09:40:14 +00:00
|
|
|
|
2023-04-11 14:00:00 +00:00
|
|
|
For a complete list of dependencies, see the [meson.build](meson.build) file.
|
2002-05-03 09:40:14 +00:00
|
|
|
|
|
|
|
Installation
|
readme: big update, simplify
Throughout the file: better use the Markdown syntax (GitLab renders it).
In order in the diff:
Intro:
- Take the same description as in the AppData file. There is anyway more
information on the website. To not have many different gedit
descriptions a bit everywhere (more difficult to update at all the
places).
- For the programming languages used, it's explained in
docs/gedit-development-getting-started.md.
Resources:
- all the links are available on the website.
Installation:
- Have a separate Dependencies section, and refer to the meson.build
file, it will simplify the maintenance, to have the list of deps in only
one place, no need to update the version numbers in both places (in the
past the readme file was frequently outdated, so it was worse).
- Simpler install procedure with Meson, with the 3 commands taken from:
https://mesonbuild.com/Quick-guide.html
- Don't explain how to extract the tarball, if someone wants to compile
gedit from source, the person hopefully knows that it's needed to
extract the tarball first (also to be able to read the readme file).
Contributions:
- Don't duplicate infos from the hacking file.
2019-08-26 05:20:24 +00:00
|
|
|
------------
|
2016-01-19 19:59:22 +00:00
|
|
|
|
2019-08-28 07:00:39 +00:00
|
|
|
To build gedit from source, see the [docs/build.md](docs/build.md) file.
|
2019-08-27 16:55:26 +00:00
|
|
|
|
2002-05-03 09:40:14 +00:00
|
|
|
How to report bugs
|
readme: big update, simplify
Throughout the file: better use the Markdown syntax (GitLab renders it).
In order in the diff:
Intro:
- Take the same description as in the AppData file. There is anyway more
information on the website. To not have many different gedit
descriptions a bit everywhere (more difficult to update at all the
places).
- For the programming languages used, it's explained in
docs/gedit-development-getting-started.md.
Resources:
- all the links are available on the website.
Installation:
- Have a separate Dependencies section, and refer to the meson.build
file, it will simplify the maintenance, to have the list of deps in only
one place, no need to update the version numbers in both places (in the
past the readme file was frequently outdated, so it was worse).
- Simpler install procedure with Meson, with the 3 commands taken from:
https://mesonbuild.com/Quick-guide.html
- Don't explain how to extract the tarball, if someone wants to compile
gedit from source, the person hopefully knows that it's needed to
extract the tarball first (also to be able to read the readme file).
Contributions:
- Don't duplicate infos from the hacking file.
2019-08-26 05:20:24 +00:00
|
|
|
------------------
|
2002-05-03 09:40:14 +00:00
|
|
|
|
readme: big update, simplify
Throughout the file: better use the Markdown syntax (GitLab renders it).
In order in the diff:
Intro:
- Take the same description as in the AppData file. There is anyway more
information on the website. To not have many different gedit
descriptions a bit everywhere (more difficult to update at all the
places).
- For the programming languages used, it's explained in
docs/gedit-development-getting-started.md.
Resources:
- all the links are available on the website.
Installation:
- Have a separate Dependencies section, and refer to the meson.build
file, it will simplify the maintenance, to have the list of deps in only
one place, no need to update the version numbers in both places (in the
past the readme file was frequently outdated, so it was worse).
- Simpler install procedure with Meson, with the 3 commands taken from:
https://mesonbuild.com/Quick-guide.html
- Don't explain how to extract the tarball, if someone wants to compile
gedit from source, the person hopefully knows that it's needed to
extract the tarball first (also to be able to read the readme file).
Contributions:
- Don't duplicate infos from the hacking file.
2019-08-26 05:20:24 +00:00
|
|
|
Please read
|
2023-10-24 14:00:01 +00:00
|
|
|
[the web page on how to report bugs](https://gedit-technology.github.io/apps/gedit/reporting-bugs.html),
|
readme: big update, simplify
Throughout the file: better use the Markdown syntax (GitLab renders it).
In order in the diff:
Intro:
- Take the same description as in the AppData file. There is anyway more
information on the website. To not have many different gedit
descriptions a bit everywhere (more difficult to update at all the
places).
- For the programming languages used, it's explained in
docs/gedit-development-getting-started.md.
Resources:
- all the links are available on the website.
Installation:
- Have a separate Dependencies section, and refer to the meson.build
file, it will simplify the maintenance, to have the list of deps in only
one place, no need to update the version numbers in both places (in the
past the readme file was frequently outdated, so it was worse).
- Simpler install procedure with Meson, with the 3 commands taken from:
https://mesonbuild.com/Quick-guide.html
- Don't explain how to extract the tarball, if someone wants to compile
gedit from source, the person hopefully knows that it's needed to
extract the tarball first (also to be able to read the readme file).
Contributions:
- Don't duplicate infos from the hacking file.
2019-08-26 05:20:24 +00:00
|
|
|
it contains a list of frequently reported bugs and a link to the bug
|
|
|
|
tracker.
|
2002-05-03 09:40:14 +00:00
|
|
|
|
2020-05-04 21:21:02 +00:00
|
|
|
Development resources
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
- [gedit on GitLab](https://gitlab.gnome.org/GNOME/gedit)
|
|
|
|
- [gedit-plugins on GitLab](https://gitlab.gnome.org/GNOME/gedit-plugins)
|
|
|
|
- [Tarballs](https://download.gnome.org/sources/gedit/)
|
|
|
|
|
2018-12-03 10:53:06 +00:00
|
|
|
Contributions
|
readme: big update, simplify
Throughout the file: better use the Markdown syntax (GitLab renders it).
In order in the diff:
Intro:
- Take the same description as in the AppData file. There is anyway more
information on the website. To not have many different gedit
descriptions a bit everywhere (more difficult to update at all the
places).
- For the programming languages used, it's explained in
docs/gedit-development-getting-started.md.
Resources:
- all the links are available on the website.
Installation:
- Have a separate Dependencies section, and refer to the meson.build
file, it will simplify the maintenance, to have the list of deps in only
one place, no need to update the version numbers in both places (in the
past the readme file was frequently outdated, so it was worse).
- Simpler install procedure with Meson, with the 3 commands taken from:
https://mesonbuild.com/Quick-guide.html
- Don't explain how to extract the tarball, if someone wants to compile
gedit from source, the person hopefully knows that it's needed to
extract the tarball first (also to be able to read the readme file).
Contributions:
- Don't duplicate infos from the hacking file.
2019-08-26 05:20:24 +00:00
|
|
|
-------------
|
2002-05-03 09:40:14 +00:00
|
|
|
|
readme: big update, simplify
Throughout the file: better use the Markdown syntax (GitLab renders it).
In order in the diff:
Intro:
- Take the same description as in the AppData file. There is anyway more
information on the website. To not have many different gedit
descriptions a bit everywhere (more difficult to update at all the
places).
- For the programming languages used, it's explained in
docs/gedit-development-getting-started.md.
Resources:
- all the links are available on the website.
Installation:
- Have a separate Dependencies section, and refer to the meson.build
file, it will simplify the maintenance, to have the list of deps in only
one place, no need to update the version numbers in both places (in the
past the readme file was frequently outdated, so it was worse).
- Simpler install procedure with Meson, with the 3 commands taken from:
https://mesonbuild.com/Quick-guide.html
- Don't explain how to extract the tarball, if someone wants to compile
gedit from source, the person hopefully knows that it's needed to
extract the tarball first (also to be able to read the readme file).
Contributions:
- Don't duplicate infos from the hacking file.
2019-08-26 05:20:24 +00:00
|
|
|
gedit development relies on voluntary contributions and everyone is invited
|
|
|
|
to help.
|
2002-05-03 09:40:14 +00:00
|
|
|
|
2023-04-11 14:00:00 +00:00
|
|
|
See the [CONTRIBUTING.md](CONTRIBUTING.md) file for more information.
|