Branch: refs/heads/master
Author: Colomban Wendling <ban(a)herbesfolles.org>
Committer: Colomban Wendling <ban(a)herbesfolles.org>
Date: Thu, 31 May 2012 21:28:46
Commit: 67ff99b1124594bd846be7a547558fe84837b9dd
https://github.com/geany/geany/commit/67ff99b1124594bd846be7a547558fe84837b…
Log Message:
-----------
Add a few missing NEWS entries
Modified Paths:
--------------
NEWS
Modified: NEWS
2 files changed, 2 insertions(+), 0 deletions(-)
===================================================================
@@ -21,6 +21,7 @@ Geany 1.22 (unreleased)
* Fix very slow regex tag parsing on Windows (e.g. for HTML).
* Fix detecting a changed file on disk when opening from
the command-line (Windows).
+ * Fix quick search entry behavior on Windows.
* Add missing Windows mio makefile.
Prefs
@@ -31,6 +32,7 @@ Geany 1.22 (unreleased)
Interface
* Add support for switching to the last used document after closing
a tab (Jiří Techet).
+ * Improve the tab switching dialog for better usability (Jiří Techet).
* Add support for user-defined labels for 'Send Selection to'
custom commands.
* Fix sidebar width when on the right (#3514436).
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).
Branch: refs/heads/master
Author: Colomban Wendling <ban(a)herbesfolles.org>
Committer: Colomban Wendling <ban(a)herbesfolles.org>
Date: Thu, 31 May 2012 20:53:51
Commit: 1725b72ec66730252f0cef48d17943588521cc65
https://github.com/geany/geany/commit/1725b72ec66730252f0cef48d17943588521c…
Log Message:
-----------
Add a node about the possibility for third party plugins to be on p.g.o
Modified Paths:
--------------
doc/plugins.dox
Modified: doc/plugins.dox
2 files changed, 2 insertions(+), 0 deletions(-)
===================================================================
@@ -106,6 +106,8 @@
* Just skip the part about forking geany-plugins and sending a pull request.
* In this case it is of course also a good idea to post some kind of announcement
* to geany-devel and maybe to the main geany mailing list -- it's up to you.
+ * You can also ask for your plugin to be listed on the http://plugins.geany.org/
+ * website as a third party plugin, helping Geany user to know about your plugin.
*
* At time of writing, there are some plugins already available in the
* repositories. Feel free to use any of these plugins as a start for your own,
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).
Branch: refs/heads/master
Author: Colomban Wendling <ban(a)herbesfolles.org>
Committer: Colomban Wendling <ban(a)herbesfolles.org>
Date: Thu, 31 May 2012 20:52:17
Commit: a35435b4d9023bfab2832f1caa8c055c089b5f0f
https://github.com/geany/geany/commit/a35435b4d9023bfab2832f1caa8c055c089b5…
Log Message:
-----------
Reword a few sentences
Modified Paths:
--------------
doc/plugins.dox
Modified: doc/plugins.dox
32 files changed, 17 insertions(+), 15 deletions(-)
===================================================================
@@ -84,26 +84,28 @@
*
* @subsection code Managing the source code
*
- * For authors of plugins for Geany, we created a dedicated @a geany-plugins using
- * project Sourceforge and GitHub to ease development of plugins and help new authors.
+ * For authors of plugins for Geany, we created a dedicated @a geany-plugins project
+ * on Sourceforge and GitHub to ease development of plugins and help new authors.
* All information about this project you can find at http://plugins.geany.org/
*
- * To add a new plugin to this project, get in contact with the people at
- * geany-devel-mailing list and create a fork of the geany-plugins-project
- * at https://github.com/geany/geany-plugins.
- * Beside of adding a new plugin, geany-devel-mailinglist is
- * also the place where to discuss development related questions.
- * However, once you have done your fork of geany-plugins you can develop
- * your plugin until you think its the right time to publish it. At this point create a
- * pull request for adding your patch set into master branch of geany-plugins.
- * Of course, you don't need to use GitHub - just any Git is fine. But GitHub
+ * To add a new plugin to this project, get in touch with the people on the
+ * geany-devel-mailing list and create a fork of the geany-plugins project
+ * at https://github.com/geany/geany-plugins.
+ * Beside of adding a new plugin, geany-devel-mailing list is also the place where
+ * to discuss development related questions.
+ * However, once you have done your fork of geany-plugins you can develop
+ * your plugin until you think its the right time to publish it. At this point,
+ * create a pull request for adding your patch set into the master branch of the main
+ * geany-plugins repository.
+ *
+ * Of course, you don't need to use GitHub - any Git is fine. But GitHub
* is making it way easier for review, merging and get in touch with you for
* comments.
*
- * If you don't want to take part at the geany-plugins-project it is also fine.
- * Just skip the part about forking geany-plugins and sending a pull request.
- * In this case its of course also a good idea to post some kind of announcement
- * also to geany-devel and maybe to the main geany mailinglist -- Up to you.
+ * If you don't want your plugin to be part of the geany-plugins project it is also fine.
+ * Just skip the part about forking geany-plugins and sending a pull request.
+ * In this case it is of course also a good idea to post some kind of announcement
+ * to geany-devel and maybe to the main geany mailing list -- it's up to you.
*
* At time of writing, there are some plugins already available in the
* repositories. Feel free to use any of these plugins as a start for your own,
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).
Branch: refs/heads/master
Author: Frank Lanitz <frank(a)frank.uvena.de>
Committer: Frank Lanitz <frank(a)frank.uvena.de>
Date: Thu, 31 May 2012 20:33:07
Commit: 7b339b8d3053f13020cdd82831b5e4e8b282e19a
https://github.com/geany/geany/commit/7b339b8d3053f13020cdd82831b5e4e8b282e…
Log Message:
-----------
Added a missing word and some smaller changes on spelling (GitHub; pull request)
Modified Paths:
--------------
doc/geany.txt
doc/plugins.dox
Modified: doc/geany.txt
2 files changed, 1 insertions(+), 1 deletions(-)
===================================================================
@@ -5000,7 +5000,7 @@ After you are happy with your changes, create a patch e.g. by using::
and then submit that file to the mailing list for review.
-Also you can clone the Geany at github and send a pullrequest.
+Also you can clone the Geany repository at GitHub and send a pull request.
Note, you will need the Python docutils software package installed
to build the docs. The package is named ``python-docutils`` on Debian
Modified: doc/plugins.dox
4 files changed, 2 insertions(+), 2 deletions(-)
===================================================================
@@ -85,7 +85,7 @@
* @subsection code Managing the source code
*
* For authors of plugins for Geany, we created a dedicated @a geany-plugins using
- * project Sourceforge and github to ease development of plugins and help new authors.
+ * project Sourceforge and GitHub to ease development of plugins and help new authors.
* All information about this project you can find at http://plugins.geany.org/
*
* To add a new plugin to this project, get in contact with the people at
@@ -96,7 +96,7 @@
* However, once you have done your fork of geany-plugins you can develop
* your plugin until you think its the right time to publish it. At this point create a
* pull request for adding your patch set into master branch of geany-plugins.
- * Of course, you don't need to use github - just any Git is fine. But github
+ * Of course, you don't need to use GitHub - just any Git is fine. But GitHub
* is making it way easier for review, merging and get in touch with you for
* comments.
*
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).
Branch: refs/heads/master
Author: Frank Lanitz <frank(a)frank.uvena.de>
Committer: Frank Lanitz <frank(a)frank.uvena.de>
Date: Thu, 31 May 2012 20:30:44
Commit: 54ed2189fe5a8c3f6d9c7a340c8647f4e4195e1f
https://github.com/geany/geany/commit/54ed2189fe5a8c3f6d9c7a340c8647f4e4195…
Log Message:
-----------
Use capitilized version of Git inside documentation
Modified Paths:
--------------
doc/geany.txt
doc/plugins.dox
Modified: doc/geany.txt
2 files changed, 1 insertions(+), 1 deletions(-)
===================================================================
@@ -4985,7 +4985,7 @@ Contributing to this document
This document (``geany.txt``) is written in `reStructuredText`__
(or "reST"). The source file for it is located in Geany's ``doc``
subdirectory. If you intend on making changes, you should grab the
-source right from git to make sure you've got the newest version. After
+source right from Git to make sure you've got the newest version. After
editing the file, to build the HTML document to see how your changes
look, run "``make doc``" in the subdirectory ``doc`` of Geany's source
directory. This regenerates the ``geany.html`` file. To generate a PDF
Modified: doc/plugins.dox
2 files changed, 1 insertions(+), 1 deletions(-)
===================================================================
@@ -96,7 +96,7 @@
* However, once you have done your fork of geany-plugins you can develop
* your plugin until you think its the right time to publish it. At this point create a
* pull request for adding your patch set into master branch of geany-plugins.
- * Of course, you don't need to use github - just any git is fine. But github
+ * Of course, you don't need to use github - just any Git is fine. But github
* is making it way easier for review, merging and get in touch with you for
* comments.
*
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).
Branch: refs/heads/master
Author: Frank Lanitz <frank(a)frank.uvena.de>
Committer: Frank Lanitz <frank(a)frank.uvena.de>
Date: Thu, 31 May 2012 20:18:03
Commit: 8965b8bc48b4d04a43f318528d800df322079ffa
https://github.com/geany/geany/commit/8965b8bc48b4d04a43f318528d800df322079…
Log Message:
-----------
Some updates on general API documentation to reflect, that geany-plugins don't use svn anymore
Modified Paths:
--------------
doc/plugins.dox
Modified: doc/plugins.dox
46 files changed, 21 insertions(+), 25 deletions(-)
===================================================================
@@ -84,41 +84,37 @@
*
* @subsection code Managing the source code
*
- * For authors of plugins for Geany, we created a dedicated @a geany-plugins project at
- * Sourceforge to ease development of plugins and help new authors.
- * Project website: http://sourceforge.net/projects/geany-plugins
- *
- * Each plugin author is welcome to use these services. To do so, you need an account at
- * Sourceforge. You can easily register at (http://sourceforge.net/account/registration/).
- * After you successfully created an account,
- * tell your account name Enrico or Nick and you will write access to the SVN repository
- * (http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/).
- * Then you can use the repository for your own plugin.
- *
- * Authors using this service should subscribe to the
- * geany-plugins-commits at uvena.de and geany-plugins-tracker at uvena.de
- * mailing lists(see my previous post) to stay up to date with changes.
- * General plugin discussion can happen on the normal geany at uvena.de or
- * geany-devel at uvena.de lists.
+ * For authors of plugins for Geany, we created a dedicated @a geany-plugins using
+ * project Sourceforge and github to ease development of plugins and help new authors.
+ * All information about this project you can find at http://plugins.geany.org/
+ *
+ * To add a new plugin to this project, get in contact with the people at
+ * geany-devel-mailing list and create a fork of the geany-plugins-project
+ * at https://github.com/geany/geany-plugins.
+ * Beside of adding a new plugin, geany-devel-mailinglist is
+ * also the place where to discuss development related questions.
+ * However, once you have done your fork of geany-plugins you can develop
+ * your plugin until you think its the right time to publish it. At this point create a
+ * pull request for adding your patch set into master branch of geany-plugins.
+ * Of course, you don't need to use github - just any git is fine. But github
+ * is making it way easier for review, merging and get in touch with you for
+ * comments.
+ *
+ * If you don't want to take part at the geany-plugins-project it is also fine.
+ * Just skip the part about forking geany-plugins and sending a pull request.
+ * In this case its of course also a good idea to post some kind of announcement
+ * also to geany-devel and maybe to the main geany mailinglist -- Up to you.
*
* At time of writing, there are some plugins already available in the
- * repository. Feel free to use any of these plugins as a start for your own,
+ * repositories. Feel free to use any of these plugins as a start for your own,
* maybe by copying the directory structure and the autotools files
* (Makefile.am, configure.in, ...). Most of the available plugins are also ready for
* i18n support, just for reference.
*
- * New plugins should be imported into a new directory inside the trunk/
- * directory. There are also the common branches and tags directories, use
- * them as needed, use always a subdirectory for your own plugin.
- *
* We encourage authors using this service to only commit changes to their
* own plugin and not to others' plugins. Instead just send patches to
* geany-devel at uvena.de or the plugin author directly.
*
- * (the full announcement of this service can be found at
- * http://lists.uvena.de/geany/2008-April/003225.html)
- *
- *
* @section paths Installation paths
*
* - The plugin binary (@c pluginname.so) should be installed in Geany's libdir. This is
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).
Branch: refs/heads/master
Author: Frank Lanitz <frank(a)frank.uvena.de>
Committer: Frank Lanitz <frank(a)frank.uvena.de>
Date: Thu, 31 May 2012 20:18:03
Commit: 81c84e553dc43bd9bf0589a07d41d2da5a929d2d
https://github.com/geany/geany/commit/81c84e553dc43bd9bf0589a07d41d2da5a929…
Log Message:
-----------
Removing reference to svn from sending a patch for this document
Modified Paths:
--------------
doc/geany.txt
Modified: doc/geany.txt
6 files changed, 4 insertions(+), 2 deletions(-)
===================================================================
@@ -4994,12 +4994,14 @@ geany-|(version)|.pdf.
__ http://docutils.sourceforge.net/rst.html
-After you are happy with your changes, create a patch::
+After you are happy with your changes, create a patch e.g. by using::
- % svn diff geany.txt > foo.patch
+ % git diff geany.txt > foo.patch
and then submit that file to the mailing list for review.
+Also you can clone the Geany at github and send a pullrequest.
+
Note, you will need the Python docutils software package installed
to build the docs. The package is named ``python-docutils`` on Debian
and Fedora systems.
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).
Branch: refs/heads/master
Author: Frank Lanitz <frank(a)frank.uvena.de>
Committer: Frank Lanitz <frank(a)frank.uvena.de>
Date: Thu, 31 May 2012 20:18:03
Commit: dbeb690f6719eb210db3271080830325f1d1f8de
https://github.com/geany/geany/commit/dbeb690f6719eb210db3271080830325f1d1f…
Log Message:
-----------
Fixing one apperance of svn inside documentation
Modified Paths:
--------------
doc/geany.txt
Modified: doc/geany.txt
2 files changed, 1 insertions(+), 1 deletions(-)
===================================================================
@@ -4985,7 +4985,7 @@ Contributing to this document
This document (``geany.txt``) is written in `reStructuredText`__
(or "reST"). The source file for it is located in Geany's ``doc``
subdirectory. If you intend on making changes, you should grab the
-source right from SVN to make sure you've got the newest version. After
+source right from git to make sure you've got the newest version. After
editing the file, to build the HTML document to see how your changes
look, run "``make doc``" in the subdirectory ``doc`` of Geany's source
directory. This regenerates the ``geany.html`` file. To generate a PDF
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).
Branch: refs/heads/master
Author: Colomban Wendling <ban(a)herbesfolles.org>
Committer: Colomban Wendling <ban(a)herbesfolles.org>
Date: Thu, 31 May 2012 19:58:37
Commit: c30936028ee5a8d0ca70202bb57676298bc7d727
https://github.com/geany/geany/commit/c30936028ee5a8d0ca70202bb57676298bc7d…
Log Message:
-----------
When not sorting the file list, don't preserve read order
If the caller doesn't want the list to be sorted, there is no need to
preserve the order in which the files were actually read, since that
order is undefined anyway.
Modified Paths:
--------------
src/utils.c
Modified: src/utils.c
2 files changed, 0 insertions(+), 2 deletions(-)
===================================================================
@@ -1440,8 +1440,6 @@ GSList *utils_get_file_list_full(const gchar *path, gboolean full_path, gboolean
/* sorting last is quicker than on insertion */
if (sort)
list = g_slist_sort(list, (GCompareFunc) utils_str_casecmp);
- else
- list = g_slist_reverse(list);
return list;
}
@@ Diff output truncated at 100000 characters. @@
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).