Devel

devel@lists.geany.org

1641 discussions

Libraries enquiry.
by Saurabh Mishra 09 Jul '17

09 Jul '17

Hello everyone, I'm Saurabh Mishra (IT student) from India.I've installed the recent Geany from git. Actually, I'm new to open source and I found the Geany project very interesting. And I really want to make some useful contributions to Geany. But, I do need some help regarding what Libraries should I learn? If you can just guide me about this then it'll be very helpful. Regards: Saurabh Mishra

2 1

Helping Geany move forward: testing
by Vasiliy Faronov 09 Jul '17

09 Jul '17

Hi all, >From discussions elsewhere, such as [1], it sounds like one of the things holding back Geany development right now is a need for more testing. I have some spare time that I can dedicate to exploratory testing of PRs to Geany and Geany-Plugins. I'm not a QA professional, but I am a programmer, I use a range of Geany features daily, and I understand Geany's code. How can I test PRs in a way that would really help them get merged? In particular: 1. How can I determine that a PR is mostly blocked on testing, and is likely to be merged when positive testing results come in? Some PRs are marked as "approved" in GitHub yet are not merged -- is that it? 2. How can I communicate my results to the satisfaction of Geany committers? For example, I could write up some kind of a report: an outline of what I tried, with screenshots of what I got -- would that help? Thank you. [1] https://github.com/geany/geany/pull/1246#issuecomment-290047712 -- Vasiliy

5 18

Fwd: Updating Geany doesn't update user's filetypes files
by Abel 28 Jun '17

28 Jun '17

I forward this mail to the devs list since nobody is accepting me for the users one :( ---------- Forwarded message ---------- From: Abel <akronix5(a)gmail.com> Date: 23 June 2017 at 11:20 Subject: Updating Geany doesn't update user's filetypes files To: Geany general discussion list <users(a)lists.geany.org> Hi. I've recently updated Geany from 1.29 to 1.30.1 through the unofficial ppa <https://launchpad.net/%7Egeany-dev/+archive/ubuntu/ppa>, Geany seems to be updated correctly but the filetypes configuration files located in ~/.config/geany/filedefs haven't got updated whereas /usr/share/geany/filedefs has. How can I get my local user config files updated as well when updating Geany? Is there any automatic way? *Greetings,* * Abel.*

6 8

String freeze for Geany-Plugins 1.31
by Frank Lanitz 25 Jun '17

25 Jun '17

Hi translators, You know it: As Geany is getting a new major release, the plugins are getting updated too. This time: 1.31. In preparation I have updated the po-files for Geany-Plugins at github and asking you whether you could update translations, review them or maybe add new languages. As on Geany core, 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 week so we can include it to the next release. Deadline will be also 2017-07-07 CET. To get most recent files you could just clone the repositories from Geany: 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. If you have any questions, don't hesitate to ping me directly via IRC: geany @freenode (frlan) Jabber/XMPP: frlan(a)jabber.ccc.de or via Mail: look above or some of the mailing lists. Happy translating! Cheers, Frank

1 0

String freeze for Geany 1.31 -- Please translate
by Frank Lanitz 25 Jun '17

25 Jun '17

Dear translators and friends of Geany, We are on the final meters for Geany 1.31. In preparation I've updated po-files for Geany core project inside github repositories and asking you whether you could update translations, review them or maybe add new languages. 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 week so we can include it to the next release. Deadline will be 2017-07-07 24:00hCET. To get most recent files you could just clone the repositories from Geany: https://github.com/geany/geany This can be done e.g. with git clone https://github.com/geany/geany.git You can find daily updated po files at http://i18n.geany.org too, which includes some statistics. 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. If you have any questions, don't hesitate to ping me directly via IRC: geany @freenode Jabber/XMPP: frlan(a)jabber.ccc.de or via Mail: look above or some of the mailing lists. Thanks and happy translating Frank

1 0

Review plugin-PR for upcoming 1.31 release
by Frank Lanitz 23 Jun '17

23 Jun '17

Hi plugin maintainer, fans and users, In about three weeks we are planning to release the next release of Geany as well as the geany-plugins (2017-07-08). Now it's good time to review open pr requests whether they can be merged into the release. Please be so kind and check https://github.com/geany/geany-plugins/pulls for pull requests related to "your" plugin. Of course, you can also have a look at https://github.com/geany/geany-plugins/issues whether there is some low hanging fruit last minute fix possible ;) Schedule: * Upcoming weekend (~2017-06-25) string freeze * 2017-07-07 deadline for translations * 2017-07-08 release It would be awesome if we can build a new and again great release together ;) Cheers, Frank

1 1

Plugin interface
by Lars Paulsen 23 Jun '17

23 Jun '17

Hi all, I got a simple question: As I understood from the development manual plugins should use geany_load_module() <http://www.geany.org/manual/reference/plugindata_8h.html#ab164d92669f69e393…> instead of plugin_init()... Is that correct? I am just wondering because it seems that 90% of the geany plugins use plugin_init() and co. Kind Regards, Lars

5 10

Re: [Geany-Devel] [geany/geany-plugins] 9fe302: Add missing style mappings for Rust and PHPSCRIPT
by Colomban Wendling 26 May '17

26 May '17

Hey, Couldn't you use something like `!highlighting_is_code_style()` or alike? Maybe it wasn't part of the API earlier or there's a subtlety I didn't think about, but it would seem more robust. Cheers, Colomban Le 25/05/2017 à 09:23, Enrico Tröger a écrit : > Branch: refs/heads/master > Author: Enrico Tröger <enrico.troeger(a)uvena.de> > Committer: Enrico Tröger <enrico.troeger(a)uvena.de> > Date: Thu, 25 May 2017 16:23:38 UTC > Commit: 9fe302801be4ac87e86a7533385c10bfbd5876a9 > https://github.com/geany/geany-plugins/commit/9fe302801be4ac87e86a7533385c1… > > Log Message: > ----------- > Add missing style mappings for Rust and PHPSCRIPT > > > Modified Paths: > -------------- > spellcheck/src/speller.c > > Modified: spellcheck/src/speller.c > 21 lines changed, 21 insertions(+), 0 deletions(-) > =================================================================== > @@ -889,6 +889,7 @@ gboolean sc_speller_is_text(GeanyDocument *doc, gint pos) > break; > } > case SCLEX_HTML: > + case SCLEX_PHPSCRIPT: > case SCLEX_XML: > { > switch (style) > @@ -1145,6 +1146,26 @@ gboolean sc_speller_is_text(GeanyDocument *doc, gint pos) > } > break; > } > + case SCLEX_RUST: > + { > + switch (style) > + { > + case SCE_RUST_DEFAULT: > + case SCE_RUST_COMMENTBLOCK: > + case SCE_RUST_COMMENTBLOCKDOC: > + case SCE_RUST_COMMENTLINE: > + case SCE_RUST_COMMENTLINEDOC: > + case SCE_RUST_STRING: > + case SCE_RUST_STRINGR: > + case SCE_RUST_BYTESTRING: > + case SCE_RUST_BYTESTRINGR: > + case SCE_RUST_LEXERROR: > + return TRUE; > + default: > + return FALSE; > + } > + break; > + } > case SCLEX_SQL: > { > switch (style) > > > > -------------- > This E-Mail was brought to you by github_commit_mail.py (Source: https://github.com/geany/infrastructure). > _______________________________________________ > Plugins-Commits mailing list > Plugins-Commits(a)lists.geany.org > https://lists.geany.org/cgi-bin/mailman/listinfo/plugins-commits >

2 1

Re: [Geany-Devel] Fold level in symbols pane
by Enrico Tröger 25 May '17

25 May '17

Hi, you replied only to me, so the others didn't see your answer but will get it in the quote below. On 05/25/2017 02:14 PM, Robert Zajda wrote: > Hi, > > Thanks for the answer. > > This problem refers to CSS/SASS only. > > > On 25.05.2017 13:55, Enrico Tröger wrote: >> On 05/16/2017 09:37 AM, Robert Zajda wrote: >>> Hi, >>> >>> There is a patch with SASS support 4 geany available on >>> http://geany.robert.dvu.pl/. >> I guess this is related to https://github.com/geany/geany/issues/908 ? >> It would help a lot if you could provide some more text in the issue, >> even if you just copy it from your website. Or even better, create pull >> requests for your patches. > > Yes this is related, but this issue is only an info (not a problem) > about patch. I just noticed the other patch is about the Scintilla CSS lexer only, you should report this (if not already done) to the Scintilla project directly. >>> There is one problem in latest version. >>> >>> Fold level in symbols pane is limited to second level. Can anyone help, >>> how to change that to be infinity? >> I don't understand exactly what you mean. >> In the screenshot attached, I have multiple levels including folding of >> each level, also below level two. >> > Yes it works with python an and php. But I made new CSS/SASS ctags file > which is based on php file. > Everything is ok except that fold level is limited. This is limited > somewhere else in the geany code. I can't find it so i'm asking for help. Ok. Without having had a look at the code, I would assume that the limitation is rather in the CTags parser than in Geany's code as it works well for other filetypes. Even if it is in Geany, it is most probably in src/symbols.c. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

1 0

CodeAi Fixes a Null Pointer Dereference
by Benjamin Bales 25 May '17

25 May '17

CodeAi (https://github.com/C0deAi), an automated repair tool developed at QbitLogic (www.qbitlogic.com), suggested the following fix. Could I submit it as a patch if it looks alright? plugins/saveactions.c: “doc->file_type” pointer might be dereferenced when null on line 283. Initialization may be provided by “doc” passed in as a function argument, but a null check would be prudent just in case. The fix checks “doc->file_type” for null before allowing a dereference on the following line. A snapshot of the bug report generated by CodeAi is attached. A full report is available upon request. diff --git a/plugins/saveactions.c b/plugins/saveactions.c @@ -280,8 +280,10 @@ static void instantsave_document_new_cb(GObject *obj, GeanyDocument *doc, gpoint doc->file_name = new_filename; - if (doc->file_type->id == GEANY_FILETYPES_NONE) + if(doc->file_type) { + if (doc->file_type->id == GEANY_FILETYPES_NONE) document_set_filetype(doc, filetypes_lookup_by_name(instantsave_default_ft)); + } /* force saving the file to enable all the related actions(tab name, filetype, etc.) */ document_save_file(doc, TRUE); /* force saving the file to enable all the related actions(tab name, filetype, etc.) */ document_save_file(doc, TRUE); } } Base-commit: 84253714771f48dbc7fab02f7de43f253734dee2 Please let me know if you are interested in seeing more fixes from our tool. Thanks! Sincerely, -- Benjamin Bales Chief Technology Officer [image: QbitLogic] 1050 Crown Pointe Pkwy, Ste. 840 Atlanta, GA 30338 470-554-2690 CONFIDENTIALITY NOTICE This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. This communication may contain privileged attorney material or other Property and Confidential matter. If you are not the intended recipient or the person responsible for delivering the e-mail for the intended person, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you believe you have received this e-mail in error, please immediately delete this e-mail and notify Benjamin Bales by telephoning 470-554-2690.

5 13

← Newer
1
...
8
9
10
11
12
13
14
...
165
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel