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 Enrico,
We have had a report on IRC that running geany on the windows command
line will only open files in the Geany install directory unless you
use the full path.
eg C:\somepath> geany somefile.txt
will open installpath\somefile.txt not somepath\somefile.txt.
And with the "Open new documents from the command line" option set it
creates somefile.txt in the install dir since it doesn't exist there.
Suspicion is falling on
https://github.com/geany/geany/commit/775ef628688c69de34640e12666aed5762a80…
As the most experienced windowser (and the committer of that change)
could you look at it please?
Cheers
Lex
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
Hello,
I built Geany with GTK 3.7.12, and then I tried to build Geany Plugin
Spellcheck and GeanyVC for Geany 0.14 GTK3.
For Spellcheck, no issue encountered, but for VC, it denied to build with
GTK3, so I tried to port GeanyVC to GTK3 and it seems that it works fine.
There is still a call to a deprecated function but as I don't know this
function I prefer avoid issues while the function still exists.
I join the diff of my work, and I hope you'll like it and merge it to the
geany-plugins-master branch.
Goodbye.
I am sorry if this message will not jump into necessary thread. I'm
replying to digest message in Gmail and setting appropriate subject.
> A little googling showed me, that this feature is in Geany wishlist. So, I
> > wish to implement it.
> > After the brief investigation I've found, that it may be implemented in
> > on_update_ui (src/editor.c) by checking active lexer, and if it is HTML,
> > then calling editor_highlight_html_tag function (or something like this).
>
> You should do language specific stuff in a plugin, you can connect to
> the editor-notify signal. Just ensure you return false.
>
> >
> > Is it OK to implement on the editor level, or you think it would be
> correct
> > to implement on the Scintilla lexer level (LexHTML.cxx)? Please, suggest.
>
> I assume you want to make it work like brace matching, when the cursor
> is in/next to a tag highlight the opposing tag.
>
Exactly.
> It is probably not possible to implement in the lexer as it won't be
> called for changes to the cursor position.
>
Ok, I will implement it as a plugin. Thank you for the tips!
--
Best regards,
Volodymyr Kononenko
http://kononenko.ws
Hi all,
I am software developer and I am using Geany almost every day. Let it be a
short introduction :)
I found out that Geany does not have a feature, mentioned in mail subject.
Is anybody busy with it?
A little googling showed me, that this feature is in Geany wishlist. So, I
wish to implement it.
After the brief investigation I've found, that it may be implemented in
on_update_ui (src/editor.c) by checking active lexer, and if it is HTML,
then calling editor_highlight_html_tag function (or something like this).
Is it OK to implement on the editor level, or you think it would be correct
to implement on the Scintilla lexer level (LexHTML.cxx)? Please, suggest.
--
Best regards,
Volodymyr Kononenko
http://kononenko.ws
Hi dear plugins developers,
Now Geany and Geany-Plugins 1.23 are out, I merged support for GTK3 in
Geany, and added initial support for building Geany-Plugins against a
GTK3 build of Geany.
As you might know, GTK3 has some incompatibilities with GTK2, and GTK3
code often requires some adjustments to work with GTK3. Since it is not
possible to load both GTK2 and GTK3 in the same program, a GTK3 build of
Geany requires plugins also built against GTK3.
So, I'd like to ask you to consider adjusting your plugins so they build
with GTK3 too. Note that *we don't mean to remove GTK2 support*, so
adjusting your plugin should make it work with *both* GTK2 and GTK3.
The plugins that currently don't build against GTK3 are:
* Addons
* Debugger
* DevHelp
* GeanyDoc
* GeanyInsertNum
* GeanyLaTeX
* GeanyLipsum
* GeanyLua
* GeanyMacro
* GeanyMiniScript
* GeanyNumberedBookmarks
* GeanyPrj
* GeanyVC
* GProject
* Markdown
* MultiTerm
* Pretty Printer
* Scope
* Spellcheck
* TreeBrowser
There are also some plugins that do build against GTK3, but that may
require adjustments to render perfectly[1]:
* CodeNav
* GeanyExtraSel
* GeanySendmail
* GeanyPG
* GeniusPaste
* ShiftColumn
* Tableconvert
* Updatechecker
* XMLSnippets
If you need any assistance to add GTK3 support for your plugin or have
any question about it, feel free to contact me.
Regards,
Colomban
[1] GTK3 behaves a little differently than GTK2 on some matters,
particularly with some widget packing. It is however totally possible
(and not hard) to get packing rules that work exactly the same on both
GTK2 and GTK3.
Le 17/03/2013 17:17, Christian Dywan a écrit :
> Branch: refs/heads/master
> Author: Christian Dywan <christian(a)twotoasts.de>
> Committer: Enrico Tröger <enrico.troeger(a)uvena.de>
> Date: Sun, 17 Mar 2013 16:17:09 UTC
> Commit: d270e6c69082d114901af23b756a3375a5b5ce23
> https://github.com/geany/geany/commit/d270e6c69082d114901af23b756a3375a5b5c…
>
> Log Message:
> -----------
> Parse compiler provided build date to use the translatable date format string
I have a system with LANG=fr_FR.UTF-8.
Opening the about dialog with LANG=C results in:
(geany:23003): GLib-WARNING **:
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error
converting results of strftime to UTF-8: Invalid byte sequence in
conversion input
(geany:23003): GLib-WARNING **:
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error
converting results of strftime to UTF-8: Invalid byte sequence in
conversion input
(geany:23003): GLib-WARNING **:
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error
converting results of strftime to UTF-8: Invalid byte sequence in
conversion input
(geany:23003): GLib-WARNING **:
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error
converting results of strftime to UTF-8: Invalid byte sequence in
conversion input
(geany:23003): GLib-WARNING **:
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error
converting results of strftime to UTF-8: Invalid byte sequence in
conversion input
(geany:23003): GLib-WARNING **:
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error
converting results of strftime to UTF-8: Invalid byte sequence in
conversion input
And opening it without changing the LANG results in:
(geany:23294): Gtk-WARNING **: Failed to set text from markup due to
error parsing markup: Erreur à la ligne 1, caractère 70 : Codage UTF-8
non valide dans le nom - « (construit le x\xc5\u0015\xc0\xff\u007f ou
ultérieurement) » n'est pas valide
(geany:23294): Gtk-WARNING **: Failed to set text from markup due to
error parsing markup: Erreur à la ligne 1, caractère 70 : Codage UTF-8
non valide dans le nom - « (construit le x\xc5\u0015\xc0\xff\u007f ou
ultérieurement) » n'est pas valide
(geany:23294): Gtk-WARNING **: Failed to set text from markup due to
error parsing markup: Erreur à la ligne 1, caractère 70 : Codage UTF-8
non valide dans le nom - « (construit le x\xc5\u0015\xc0\xff\u007f ou
ultérieurement) » n'est pas valide
>
>
> Modified Paths:
> --------------
> src/about.c
>
> Modified: src/about.c
> 8 files changed, 7 insertions(+), 1 deletions(-)
> ===================================================================
> @@ -31,6 +31,7 @@
> #include "support.h"
> #include "geanywraplabel.h"
> #include "main.h"
> +#include "templates.h"
>
> #include "gb.c"
>
> @@ -152,6 +153,8 @@ static GtkWidget *create_dialog(void)
> gchar buffer[512];
> gchar buffer2[128];
> guint i, row = 0;
> + struct tm builddate_tm;
> + char builddate_local[255];
>
> dialog = gtk_dialog_new();
>
> @@ -224,7 +227,10 @@ static GtkWidget *create_dialog(void)
> gtk_label_set_justify(GTK_LABEL(builddate_label), GTK_JUSTIFY_CENTER);
> gtk_label_set_selectable(GTK_LABEL(builddate_label), TRUE);
> gtk_label_set_use_markup(GTK_LABEL(builddate_label), TRUE);
> - g_snprintf(buffer2, sizeof(buffer2), _("(built on or after %s)"), __DATE__);
> + memset(&builddate_tm, 0, sizeof(struct tm));
> + strptime(__DATE__, "%b %d %Y", &builddate_tm);
> + strftime(builddate_local, sizeof(builddate_local), GEANY_TEMPLATES_FORMAT_DATE, &builddate_tm);
> + g_snprintf(buffer2, sizeof(buffer2), _("(built on or after %s)"), builddate_local);
> g_snprintf(buffer, sizeof(buffer), BUILDDATE, buffer2);
> gtk_label_set_markup(GTK_LABEL(builddate_label), buffer);
> gtk_misc_set_padding(GTK_MISC(builddate_label), 2, 2);
>
>
>
> --------------
> This E-Mail was brought to you by github_commit_mail.py (Source: https://github.com/geany/infrastructure).
> _______________________________________________
> Commits mailing list
> Commits(a)lists.geany.org
> https://lists.geany.org/cgi-bin/mailman/listinfo/commits
>