Hi all,
I just made a test build of Geany Plugins 1.22 for Windows.
A little surprisingly for me, it all worked fine on the first attempt :).
I only had problems loading the Geany-Lua plugin with some strange error
message which I didn't investigate yet:
http://pastebin.geany.org/EUmwJ/
The error message occurs on plugin loading. I'm not sure whether it is
caused by my system or something else.
If anyone wants to test it, any feedback is appreciated.
The installer...
http://www.uvena.de/tmp/geany-plugins-1.22_setup_testbuild.exe
... requires an existing Geany 1.22 installation.
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
Hi All,
Its about that time of year when we have our annual discussion on
separating session data from config/project data :)
By session data I mean the list of currently open files and MRU list.
The advantages (that I can see):
1. Save config/project as its changed and not rushed at quit time (and
the quit save doesn't happen in the absence of a working, portable,
session management capability)
2. Save session data periodically, or as it changes, or whenever,
without touching the config/project files. So the config isn't at
risk if the session save goes wrong.
The only disadvantage for user config (that I can see) is that it adds
one file, say geany.session.conf alongside geany.conf
For project sessions just using another file in the same place as the
project file is more of a problem since project files can be in the
project tree and some people like to save them in VCS. So users would
have to make sure that their git.ignore (or whatever the other VCSes
use) is edited each time so that the session file isn't saved in the
VCS.
A better option, especially since sessions are inherently user
related, is to store them in the user config location (or subdirectory
thereof). But how to link these files to the project files?
The proposal is that each project gets a UUID generated when it is
created (or when its opened without one) which is saved in the project
file. This uuid is the name of the session file in the
${GEANY_CONFIG}/sessions directory. That way, when a project is
opened, it is easy to uniquely find the session file if it exists.
Using things like filenames, project names etc will always have
clashes. Libuuid is used by GTK so it will always be available on all
platforms we use and so making the UUID is one call. (Pity GTK doesn't
expose it though)
The number of session files can be left to grow like weeds, or can be
trimmed to a (configurable) maximum number deleting the oldest when
needed.
This proposal isn't about a proper session management capability,
there isn't one that works on enough platforms to be worth including.
Any thoughts welcome.
Cheers
Lex
Hi!
I saw this code in src/symbols.c at line 1917:
while (sci_get_style_at(sci, start) != fn_style
&& start < max_pos) start++;
If start >= max_pos then sci_get_style_at will be called (with out of
bounds value?) and then the loop will bail out.
I suggest that the condition is reordered as:
while (start < max_pos
&& sci_get_style_at(sci, start) != fn_style)
start++;
Then sci_get_style_at will only be called if start is less than max_pos.
It is just my humble suggestion.
Best regards,
Daniel
Another (minor) update to the Snap Open script: the file chooser dialog is now much wider. It's a hack, I'm afraid; it just inserts a long line of tabs into the message text.
As far as I can tell, dialog size isn't configurable in Lua scripts? Even in the dialog module, for more complicated dialogs, I couldn't see anything.
Thrawn
Attached is a patch containing a few obvious fixes for warnings in the
plugins, mostly adding consts, gpointer casts and unsigned int loop
counters.
The only one that is likely to have been bad (tm) is in treebrowser.c
it g_freed a static string. Setting the string const found that.
treebrowser.c still has warnings about two unused variables, since in
each case some work is done to set them, the treebrowser maintainer
should look and see if they are meant to be used somewhere, or remove
them and the setting code.
Cheers
Lex
Hi folks,
There are still a huge number of plugins which don't have any
maintainer-information on Maintainers-file on geany-plugins-project --
Which means most likely these are unmaintained or at minimum there is no
direct contact if there is any issue related to. Plugins which are
effected by are:
* codenav
* geanylua
* geanypg
* pretty-printer
* shiftcolumn
* treebrowser
Please be so kind and add your information there if you're taking care
of the plugin or like to in future.
Please keep in mind: If nobody is taking care of these plugins they
might will not be part of upcoming Geany releases if there are any major
issues with.
Cheers,
Frank
Hi,
Currently, plugin_signal_connect() does not check if a signal is
successfully connected before adding it to the list of signals to be
disconnected when the plugin is unloaded. How about making such a
check? Attempting to disconnect signal id 0 only produces an assertion
message, and we already have a more informative warning displayed from
g_signal_connect().
--
E-gards: Jimmy
Hi translators and friends of Geany,
And again we are in final line for another Geany release -- 1.23!
The list of changes done for this release is long (as usual) and so a
lot of string have changed or were added. I like to ask all translators
to check the translations.
I'd be very happy if you could send a patch, a pull request or single
file with translation to either the geany-i18n mailing list or direct
to me within the next two weeks so we can include it to the next
release. Deadline will be 2013-03-97.
To make it more easy for you I've already uploaded updated versions of
the po files to git master at github. You can either download the direct
via web or by cloning the repository from
https://github.com/geany/geany
This can be done e.g. with
git clone https://github.com/geany/geany.git
Also at http://i18n.geany.org/ are statistics and daily updated files
available.
As mentioned before, we are trying to have all translations complete by
2013-03-07.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to
translate same things two or three times. Also please feel to ping me
for every question or if you like to start a new translation for an
unsupported language.
Thanks and happy translating
Frank
Hi translators and freinds of Geany,
We are on final steps for release Geany-Plugins 1.23 together with Geany
1.23.
The list of changes done for this release is long and so a lot of
string have changed or were added. I like to ask all translators to
check their translations. Also if your language is not having a
translation by now I also ask you to add it ;)
I'd be very happy if you could send a patch, a pull request or single
file with translation to either the geany-i18n mailing list or direct
to me within the next two weeks so we can include it to the next
release. Deadline will be 2013-03-07.
To make it more easy for you I've already uploaded updated versions of
the po files (and now this is new) to git master. You can either
download the direct via web or by cloning the repository from
https://github.com/geany/geany-plugins
This can be done e.g. with
git clone https://github.com/geany/geany-plugins.git
Also at http://i18n.geany.org/plugins are statistics and daily updated
files available.
As mentioned before, we are trying to have all translations complete by
2013-03-07.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to
translate same things two or three times. Also please feel to ping me
for every question or if you like to start a new translation for an
unsupported language.
Thanks and happy translating
Frank