[Geany-Devel] Re: Introduction

On Sat, 30 Mar 2024 at 04:23, sylvain cresto via Devel wrote: > > Hello, > > My name is Sylvain Cresto. > > While looking for a good programmer's text editor, I discovered Geany a short > time ago. > I like developing in C so I'll try to write some improvements, starting with > some plugins.

[Geany-Devel] Re: github copilot

Maybe look at https://github.com/techee/geany-lsp On Tue, 28 Nov 2023 at 04:30, Ramin Moussavi via Devel wrote: > > i would like to have github copilot integration in geany > so i had a look at the neovim plugin > > i started to write small c prototype which just uses the jsonrpc / lsp >

[Geany-Devel] Re: Hello evbd.

On Fri, 30 Jun 2023 at 00:10, Andreas Schöller via Devel wrote: > > > Hello Lex, > > thx for your quick reply. > > Am 29.06.2023 um 02:02 schrieb Lex Trotman via Devel : > > On Thu, 29 Jun 2023 at 07:58, Andreas Schöller via Devel > wrote: > > Perhaps you shou

[Geany-Devel] Re: Hello evbd.

On Thu, 29 Jun 2023 at 07:58, Andreas Schöller via Devel wrote: > > Hello Geany developers, > > i know i’m late to the party and its gotten quite on this list. Is there any > development going on ? It mostly uses github for development discussion now. > In 2016 there was a long discussion

[Geany-Devel] Re: Geany download themes website is broken

Thank you, we know, see https://github.com/geany/geany-themes/pull/58 Cheers Lex On Fri, 12 May 2023 at 00:46, e.antonoff--- via Devel wrote: > I mean this website: https://www.geany.org/download/themes/ > > Apologies for this, I think my pull request #57 is the problem. It wasn't > obvious

[Geany-Devel] Re: Hello and a little problem

On Wed, 10 May 2023 at 09:40, e.antonoff--- via Devel wrote: > Hello, > > New here. I am not a C/C++ dev, so I simply joined in order to add my > color theme to the geany_themes repo, but got a problem: > > So I cloned locally geany_themes, made a new branch, added my theme and a > screenshot,

[Geany-Devel] Re: Geany colour scheme on MIT license?

On Tue, 14 Mar 2023 at 08:02, Lex Trotman wrote: > > On Tue, 14 Mar 2023 at 06:25, Julian Groß via Devel > wrote: > > > > Dear Geany developers, > > > > > > is it possible to use the default Geany colour theme (as defined in > > https://git

[Geany-Devel] Re: Geany colour scheme on MIT license?

On Tue, 14 Mar 2023 at 06:25, Julian Groß via Devel wrote: > > Dear Geany developers, > > > is it possible to use the default Geany colour theme (as defined in > https://github.com/geany/geany/blob/master/data/filedefs/filetypes.common > ) in an MIT licensed project? > I have recently switched to

[Geany-Devel] Fwd: Re: bracket colors plugin

oops we got off the list -- Forwarded message - From: Lex Trotman Date: Fri, 27 Jan 2023 at 17:00 Subject: Re: [Geany-Devel] Re: bracket colors plugin To: Asif Aaron Amin > ... > I'm just about ready to make a pull request (learning autotools took longer > than

[Geany-Devel] Re: bracket colors plugin

On Sat, 14 Jan 2023 at 05:54, Asif Aaron Amin via Devel < devel@lists.geany.org> wrote: > Lex/All, > > I presume you mean VS code using differing colours for each nesting level >> of braces. I also happen to use VS, but you can't expect that contributors >> to one project will be aware of the

[Geany-Devel] Re: bracket colors plugin

On Thu, 15 Dec 2022 at 02:42, Asif Aaron Amin via Devel < devel@lists.geany.org> wrote: > All, > > First I'd like to thank you for developing Geany as it has been my > preferred IDE for 7 years due to how customizable and fast it > is, especially over ssh/X forwarding. I also use VS Code in

Re: [Geany-Devel] Geany spews Gtk-CRITICAL messages on cursor movement

On Tue, 21 Dec 2021 at 16:10, Austin Green wrote: > > Recently built (on Xubuntu system) Geany from source. > Version: geany 1.39 (git >= d031d6f2) (built on 2021-12-14 with GTK 3.24.30, > GLib 2.68.4) > > Sometimes it emits hundreds of error messages of this general type: > (geany:7480):

Re: [Geany-Devel] Building geany using msys2 on Windows 10

On Wed, 15 Sept 2021 at 08:57, Lex Trotman wrote: > > > So looking at https://nightly.geany.org/win32/build_win32_geany.log, > > the problem is clear: the build is using Python 2.7. Python2 will read > > the file as ASCII by default, while Python3 will try to detect the >

Re: [Geany-Devel] Building geany using msys2 on Windows 10

> So looking at https://nightly.geany.org/win32/build_win32_geany.log, > the problem is clear: the build is using Python 2.7. Python2 will read > the file as ASCII by default, while Python3 will try to detect the > encoding and fall back to UTF-8. Plus Python2 is now unsupported. > > When I tried

Re: [Geany-Devel] Building geany using msys2 on Windows 10

> >> The menu item "Help->help" and pressing "F1" correctly open the help > >> file in Firefox Nightly at > >> "file:///C:/Program%20Files/Geany/share/doc/geany/html/index.html" > > > > Not sure why this uses a different method to the other help, although > > It's the same method and that's

Re: [Geany-Devel] Building geany using msys2 on Windows 10

>> Some > > messages do not have the timestamp prefix. Many debug messages have > > the same time stamp, so adding the milliseconds value would be > > helpful. > > Request a feature addition, although I think the timestamp is added by > Glib, so we might not be able to control it. > And here is

Re: [Geany-Devel] Building geany using msys2 on Windows 10

> Can someone suggest how to correct this snippet of code in the wiki > > > > On 09.09.21 06:31, Lex Trotman wrote: > > >> Not sure who posted the wiki or how relevant it is (its a wiki after > > > > Anyway, to get back to Doug's question: > > > I'm g

Re: [Geany-Devel] Building geany using msys2 on Windows 10

Attila, the windows build environment is completely different to the Linux one so your comment is irrelevant. Setting up the environment is the difficult part for most people. Also you can just give configure an argument --enable-gtk3 rather than editing configure.ac, also on the current Geany

Re: [Geany-Devel] Building geany using msys2 on Windows 10

Not sure who posted the wiki or how relevant it is (its a wiki after all :), for example Geany now only supports GTK3, not GTK2. The official Windows build processes are currently under upgrade as a result, see https://github.com/geany/geany/pull/2590 and

Re: [Geany-Devel] Plugin API - request access to keybindings_check_event function

On Sat, 20 Mar 2021 at 13:39, Austin Green wrote: > > Is there a mechanism for requesting changes to the plugin API? Other than > this list? > > I would like to be able to call the function keybindings_check_event which is > in keybindings.c The way to do it is to make a pull request, but you

Re: [Geany-Devel] Order of plugin signal connections

> > Well, whaddaya know? I cloned a recent version of geany, and found that > someone has already implemented a very similar Geany signal, called > "key-press". For at least part of this thread I thought you meant that signal, not the low level GTK signal. Cheers Lex

Re: [Geany-Devel] Order of plugin signal connections

> > This is true, for 'key-press-event' and 'key-release-event' at least. > However, for my 'pre-key-press-event', it is NOT the case; all connected > callbacks are always called. I'm guessing that GTK makes a distinction > between events originating in X or the kernel, and user-created

Re: [Geany-Devel] Order of plugin signal connections

On Fri, 15 May 2020 at 14:35, Austin Green wrote: > > @Lex: > > Of course you can't enforce non-suppression, the best you can do is to > > document it clearly (hint not to forget the documentation :) > > Actually you can (and my code currently does) enforce it, simply by ignoring > the return

Re: [Geany-Devel] Order of plugin signal connections

On Fri, 15 May 2020 at 10:48, Austin Green wrote: > > Hi Matthew, > > On Thu, 14 May 2020 16:20:58 -0700 > Matthew Brush wrote: > > > Can you elaborate on what you are trying to do specifically? There may > > be a better way. > > Sure thing. > > The plugin 'recordkey', and possibly others,

Re: [Geany-Devel] Order of plugin signal connections

On Thu, 14 May 2020 at 16:52, Austin Green wrote: > > Hi Lex, > > Further to my last message, which proposed: a new signal, say > "pre-key-press-event", then, in Geany start-up (before any plugin loading) > connect to "key-press-event". In the handler for "key-press-event", Geany > just emits

Re: [Geany-Devel] Order of plugin signal connections

On Tue, 12 May 2020 at 12:00, Austin Green wrote: > > I need to ensure that one particular plugin will process keyboard events > before other plugins get to see them (as some plugins may cause further > handling of the event to be suppressed). Is there a way to achieve that? > I'm guessing

Re: [Geany-Devel] geany.glade.h

On Mon, 4 May 2020 at 10:02, Dmitry Unruh via Devel wrote: > > Each of *.po files references to a file ../data/geany.glade.h but this > file is absent in the sources. Is this file lost? IIUC these are created by intltool when it extracts strings from glade but I'm no expert. Cheers Lex >

Re: [Geany-Devel] Inserting in virtual space

On Fri, 3 Apr 2020 at 12:49, Austin Green wrote: > > Hi Scintilla experts, > > I want to insert text at the caret position when the caret is in virtual > space, i.e. off the end of the line. Have tried > SCI_REPLACESEL > SCI_INSERTTEXT > and sundry ways of trying to find the

Re: [Geany-Devel] Patching Scintilla code

On Fri, 3 Apr 2020 at 04:03, j kanem wrote: > > Hi dev-list, > > I have a question regarding the Scintilla code that is in the Geany repo. Is > this raw code straight from Scintilla, or is it patched by Geany devs? https://github.com/geany/geany/blob/master/scripts/update-scintilla.sh > > I

Re: [Geany-Devel] Colour scheme woes

On vim and rust, if the example below (from the Rust manual) does not colour "Color" and "Point" as functions in the "let" lines then it must also be parsing declarations, not using syntax. ``` #![allow(unused_variables)] fn main() { struct Color(i32, i32, i32); struct Point(i32, i32, i32); let

Re: [Geany-Devel] Colour scheme woes

On Sun, 22 Mar 2020 at 13:43, Austin Green wrote: > > Thanks for responding, Lex. > > On Sun, 22 Mar 2020 12:47:56 +1000 > Lex Trotman wrote: > > > > I'm calling it Slick; I've created a slick.conf file, copied from the > > > default.conf, > > &

Re: [Geany-Devel] Colour scheme woes

On Sun, 22 Mar 2020 at 11:31, Austin Green wrote: > > I'm trying to create a new Geany colour scheme, with only partial success. > > I'm calling it Slick; I've created a slick.conf file, copied from the > default.conf, Neither grep nor I can find a file called default.conf?? > and made

Re: [Geany-Devel] Smalltalk support in Geany

Geany is a volunteer project, nothing will happen unless "somebody" submits a pull request. Not saying it will be accepted, but if nobody has done it to date it likely means nobody uses smalltalk and it isn't going to happen otherwise. Cheers Lex On Thu, 14 Nov 2019 at 07:04, Snowflake the Pony

Re: [Geany-Devel] How to programmatically de-select text

On Wed, 28 Aug 2019 at 20:38, Austin Green wrote: > > Hi Lex, > > > > Trying to programmatically cancel a text selection. There are functions > > > that will probably do it, e.g. sci_set_selection, but bearing in mind the > > > restriction on changing the API, those functions are not callable

Re: [Geany-Devel] How to programmatically de-select text

On Wed, 28 Aug 2019 at 15:12, Austin Green wrote: > > Trying to programmatically cancel a text selection. There are functions that > will probably do it, e.g. sci_set_selection, but bearing in mind the > restriction on changing the API, those functions are not callable from my > code. > >

Re: [Geany-Devel] Problem with pointer from API function -- solved

On Tue, 27 Aug 2019 at 16:00, Austin Green wrote: > > Hi Lex, > > On Tue, 27 Aug 2019 14:39:52 +1000 > Lex Trotman wrote: > > > On Tue, 27 Aug 2019 at 14:29, Austin Green > > wrote: > > ... > > > As well as adding the GEANY_API_SYMBOL macro to

Re: [Geany-Devel] New language in Geany

> It's apparently quite common Ummm, 80 out of 8500 (and some are now dead) using the statistics of that page isn't exactly common. Cheers Lex On Wed, 7 Aug 2019 at 01:58, Matthew Brush wrote: > > On 2019-08-06 6:01 a.m., Tim Tassonis wrote: > > On 8/1/19 9:41 AM, KK2000 wrote: > >> Dear Geany

Re: [Geany-Devel] shorter lines for language syntax

Just to point out that the requirement for one long line is set by the Glib key file library that Geany uses to read/write the config files. It is not necessarily going to be as easy as first glance. Cheers Lex On Sat, 13 Apr 2019 at 08:27, Andy Alt wrote: > > Hi Billy. > > I don't recall

Re: [Geany-Devel] VTE Color Palette

On Tue, 1 Jan 2019 at 10:28, Tobias Moritz wrote: > > Hello, > > I wrote a patch for the VTE plugin to support color palette (16). So here is > my question, is this already in development, should I send my patch per mail > or pull request? Pull request thanks. Cheers Lex > > Best regards and

Re: [Geany-Devel] Presentation - Rubén

On Fri, 28 Dec 2018 at 04:55, Enrico Tröger wrote: > > Hi Rubén, > > > > > My name is Rubén. I'm a master's degree student at UDC and I've been using > > Geany and loving it for years. Finally I've subscribed to developer mailing > > list with the goals of: > > > > > > * Dive into the Geany

Re: [Geany-Devel] Geany Plugins and Document Close Behavior

On 13 May 2018 at 17:35, Lex Trotman <ele...@gmail.com> wrote: > Hi, > > The best way of providing for changes would be to make a pull request > on Github. Then they will at least be CI checked. Also on Github you can point to parts of the source which support your ex

Re: [Geany-Devel] Geany Plugins and Document Close Behavior

Hi, The best way of providing for changes would be to make a pull request on Github. Then they will at least be CI checked. Cheers Lex On 13 May 2018 at 16:55, Jason Cumbie wrote: > Hello Geany Developers, > > I’m a software developer who has had fun using Geany for my

Re: [Geany-Devel] Scintilla Use

> I would think by the time older LTS distros are up to C++17, that > Scintillua/LongTerm3 will have no reason to exist anymore. Old LTS will never get it, thats why they are called "stable", what I meant is the next LTS, for example Ubuntu is scheduled to release a new LTS next month which will

Re: [Geany-Devel] Scintilla Use

On 22 March 2018 at 10:35, Matthew Brush wrote: > Hi, > > Going forward, are we going to use the Scintilla LongTerm3 branch or v4.x > releases? Interesting question. I had been assuming that once Neil settled it down and after the next round of LTS Linuxen were released

Re: [Geany-Devel] Why has the universal ctags project to be merged?

On 22 March 2018 at 07:17, Lars Paulsen wrote: > Hello, > > I have got a maybe stupid question out of curiosity: > Why needs the universal ctags project be merged into Geany instead of e.g. > just copying it over? > I guess the reason is not that we do not trust their test

Re: [Geany-Devel] How are ctags used?

On 20 March 2018 at 07:25, Lars Paulsen wrote: > Hello, > > I have got a question regarding the design of Geany or better say how do the > components work together regarding ctags. Ignore Scintilla for parsing, it ONLY does highlighting, and the parser results have to be

Re: [Geany-Devel] GTK version policy

On 24 February 2018 at 05:53, Lars Paulsen wrote: > Hello All, > > I have ported the scope plugin to GTK3. > During that work I also noticed some deprecation warnings for the workbench > plugin which I did create not long ago > and as suggested by the HACKING file I did write

Re: [Geany-Devel] Linker issues with VTE

On 22 February 2018 at 16:11, Lars Paulsen wrote: > Hello Colomban, > > I saw that in the GTK3 porting PR for the debugger plugin and also tried > changing scope.m4 accordingly: > https://github.com/geany/geany-plugins/pull/645/files#diff-41e5fe75dcc03252ed3688fd124e9223 > >

Re: [Geany-Devel] How to force geany-plugins to build against GTK3?

On 21 February 2018 at 06:32, Thomas Martitz wrote: > Am 20.02.2018 um 18:00 schrieb Lars Paulsen: >> >> Hello All, >> >> I have a simple question: how can I force geany-plugins to be built >> against GTK3? >> >> I tried "CFLAGS=-dGP_GTK_VERSION_MAJOR=3 ./configure" but that

Re: [Geany-Devel] Create project files from within a plugin

On 19 February 2018 at 16:29, Lars Paulsen wrote: > Hi Matthew, > > thanks for the answer. > > Yes, I wanted to create it programmatically. But I really only meant to > create a project file. Not open it and make it the actual project. > But there does not seem to be such a

Re: [Geany-Devel] Building geany on Windows is slow; libgeany

On 25 January 2018 at 22:19, Nick Treleaven wrote: > Hi, > I hadn't built Geany for a while, I found the MSYS2 build instructions with > autotools. Libtool seems incredibly slow - mainly for linking but even > compiling is slow. I've tried disabling AV to no effect. Are there

Re: [Geany-Devel] [RFC]: Adding Filetype Extensions

On 21 December 2017 at 09:09, Matthew Brush wrote: > Hi, > > There are quite a few Issues/Pull Requests on Github about adding more > extensions to `filetype_extensions.conf` so various types of files are > detected/colourized/symbolized properly out of the box. > > IMO, we

Re: [Geany-Devel] How can a plugin invoke menu items/geany actions?

On 21 December 2017 at 07:37, Lars Paulsen wrote: > Hi All, > > I would like to start actions in geany from inside a geany plugin? > > E.g. start the Color Chooser as if it was selected from the geany tools > menu. > I tried to call the callback function directly but that

Re: [Geany-Devel] geany plugins fails to compile with latest pango

On 25 November 2017 at 10:28, Tim Tassonis <st...@decentral.ch> wrote: > > > On 11/25/2017 01:09 AM, Lex Trotman wrote: >> >> On 25 November 2017 at 09:44, Colomban Wendling >> <lists@herbesfolles.org> wrote: >>> >>> Hey

Re: [Geany-Devel] Workbench translation and the use of Directory vs Folder

On 18 November 2017 at 18:20, Lars Paulsen wrote: > Hi Colomban, > > yeah, that names are ambiguous. > > Items labeled "Directory" are the root or base directories or external > directories that the user can add. Then these directories are scanned for > sub-directories and

Re: [Geany-Devel] Comments in translation files

On 30 July 2017 at 00:07, Lars Paulsen wrote: > Hello All, > > I solved my problem with running xgettext from the command line. > But I got one question left: > > How can I update the language files using the geany-plugins makefile? > > My own plugin is build and installed

Re: [Geany-Devel] Comments in translation files

On 29 July 2017 at 21:31, Lars Paulsen wrote: > Hello All, > > I got a question about the translation files. If I have a translated string > like in the example below, does the comment with the source location have a > meaning for the translation tool or is it "only" an

Re: [Geany-Devel] Hooks on calling some functions for plugins?

On 5 July 2017 at 17:25, Thomas Martitz wrote: > Am 03.07.2017 um 12:33 schrieb Денис Феклушкин: >> >> Hi! >> >> I am writing D language plugin on D: >> https://github.com/denizzzka/geany_dlang >> >> This plugin isn't adds any new functionality but I planning replace >> already

Re: [Geany-Devel] Hooks on calling some functions for plugins?

On 5 July 2017 at 16:15, Денис Феклушкин <feklushkin.de...@gmail.com> wrote: > > > 2017-07-05 8:05 GMT+07:00 Lex Trotman <ele...@gmail.com>: >> >> On 5 July 2017 at 02:00, Vasiliy Faronov <vfaro...@gmail.com> wrote: >> > Hi Denis, >> &

Re: [Geany-Devel] Hooks on calling some functions for plugins?

On 5 July 2017 at 02:00, Vasiliy Faronov wrote: > Hi Denis, > > As far as I understand, none of this is directly supported by Geany right now. > > This is a known problem: https://github.com/geany/geany/issues/1458 > > Until it is solved systematically (if ever), you might be

Re: [Geany-Devel] Fwd: Updating Geany doesn't update user's filetypes files

On 26 June 2017 at 10:36, Colomban Wendling <lists@herbesfolles.org> wrote: > Le 25/06/2017 à 17:22, Lex Trotman a écrit : >> […] >> As Matthew says the filetype files in the users directory are the >> users own, it would be rude of Geany to overwrite them, since u

Re: [Geany-Devel] Fwd: Updating Geany doesn't update user's filetypes files

On 26 June 2017 at 09:03, Matthew Brush wrote: > On 2017-06-25 03:07 PM, Abel wrote: >>> >>> >>> >>> Which configuration in detail did you expect to be updated? >>> >>> >> The filetypes files which contain the keywords definition for each >> language. In particular, I was

Re: [Geany-Devel] Plugin interface

> For what's it worth, I'm also waiting for waiting for #1112 [1] too before > adding peasy to geany-plugins. Makes sense, if your bindings need introspection there is no point in releasing them until Geany is set up to generate it. > So long it's publicly available at here[2]. > I'm not

Re: [Geany-Devel] Plugin interface

It has been pointed out that I totally avoided actually explicitly answering the question, yes use the new interface. Cheers Lex ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel

Re: [Geany-Devel] CodeAi Fixes a Null Pointer Dereference

On 13 May 2017 at 03:44, Benjamin Bales wrote: > I apologize for that. Here's the report in plain text format: > > CodeAi (https://github.com/C0deAi), an automated repair tool developed > at QbitLogic (www.qbitlogic.com), suggested the following fix. Could I >

Re: [Geany-Devel] CodeAi Fixes a Null Pointer Dereference

Ben > > On Wed, May 10, 2017 at 8:22 PM, Matthew Brush <mbr...@codebrainz.ca> > wrote: > >> On 2017-05-10 04:09 PM, Lex Trotman wrote: >> >>> On 11 May 2017 at 08:10, Benjamin Bales <benjamin.ba...@qbitlogic.com> >>> wrote: >>> &

Re: [Geany-Devel] CodeAi Fixes a Null Pointer Dereference

On 11 May 2017 at 08:10, Benjamin Bales wrote: > 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:

Re: [Geany-Devel] Adding SystemVerilog Parser

s Lex > > > Josh E-C > > > From: Devel <devel-boun...@lists.geany.org> on behalf of Lex Trotman > <ele...@gmail.com> > Sent: Wednesday, May 3, 2017 10:03:48 AM > To: Geany development list > Subject: Re: [Geany-Devel]

Re: [Geany-Devel] Adding SystemVerilog Parser

Hi, If you mean the parsers in the ctags/parsers directory, those come from the Universal Ctags project https://github.com/universal-ctags/ctags so you should probably start by asking there. Cheers Lex On 3 May 2017 at 23:23, Joshua A. Einstein-Curtis wrote: > Hi Geany

Re: [Geany-Devel] Helping Geany move forward: testing

On 1 May 2017 at 23:32, Frank Lanitz <fr...@frank.uvena.de> wrote: > On 29.04.2017 03:35, Lex Trotman wrote: >> We really NEED automatic UI testing and we NEED function unit testing, >> but realistically we are not going to get either. If we don't have >> enough resourc

Re: [Geany-Devel] Helping Geany move forward: testing

On 29 April 2017 at 23:15, Vasiliy Faronov <vfaro...@gmail.com> wrote: > On Sat, Apr 29, 2017 at 2:58 PM, Lex Trotman <ele...@gmail.com> wrote: >> The vast majority are therefore not testing anything in master prior >> to release, so they are not helping stabilise the

Re: [Geany-Devel] Helping Geany move forward: testing

... >> I have to agree with Matthew that: >> >> 1. Nobody wants to break master because its what everybody is using. >> Problem is that if we had a development branch nobody would be using >> it because it might break, so its insufficiently tested. I don't have >> a solution to that. > > > master

Re: [Geany-Devel] Helping Geany move forward: testing

As an exercise I scanned the top few (highest numbered) PRs to assess their commitability from MY personal point of view, found one immediately committable and did, the rest are: #1482 still open question if it should revert to previous bad behaviour. #1481 work in progress #1478 improvement

Re: [Geany-Devel] Helping Geany move forward: testing

... >> >> Geany is almost entirely an interactive application, so until >> interactive tests are possible I don't think technical tests like >> these will add a great deal to the committability of PRs. > > > If the tests just test functions, all it needs is to get Geany started up, > then the

Re: [Geany-Devel] Helping Geany move forward: testing

On 29 April 2017 at 09:55, Matthew Brush wrote: > On 2017-04-28 02:35 PM, Thomas Martitz wrote: >> >> Am 27.04.2017 um 22:51 schrieb Vasiliy Faronov: >>> >>> Hi all, >>> >>> From discussions elsewhere, such as [1], it sounds like one of the >>> things holding back Geany

Re: [Geany-Devel] Helping Geany move forward: testing

Hi Vasily, On 28 April 2017 at 06:51, Vasiliy Faronov wrote: > 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 can only speak from my point of view, but I believe

[Geany-Devel] New Direction for Geany

Dear All, Geany having failed at being a small fast lightweight IDE and having become a chubby middle aged application, its time for a re-think, a new direction, a fresh start. Instead it is proposed that Geany embrace the paradigms of the most successful IDEs (like Emacs or Eclipse) and make

Re: [Geany-Devel] Future of THANKS/contributors list inside help dialog

On 12 March 2017 at 20:59, Enrico Tröger <enrico.troe...@uvena.de> wrote: > On 10/03/17 01:01, Lex Trotman wrote: >> On 10 March 2017 at 07:14, Enrico Tröger <enrico.troe...@uvena.de> wrote: >>> On 09/03/17 14:56, Frank Lanitz wrote: >>>> Hi, >>

Re: [Geany-Devel] Future of THANKS/contributors list inside help dialog

On 10 March 2017 at 07:14, Enrico Tröger wrote: > On 09/03/17 14:56, Frank Lanitz wrote: >> Hi, >> >> Currently we have apart of the git list itself two places where we have >> added contributors in past, but which look quiet orphaned nowadays: >> >> The

Re: [Geany-Devel] Future of THANKS/contributors list inside help dialog

On 9 March 2017 at 23:56, Frank Lanitz wrote: > Hi, > > Currently we have apart of the git list itself two places where we have > added contributors in past, but which look quiet orphaned nowadays: > > The contributors-dialog on Geany->Help: > >

Re: [Geany-Devel] Storing per-project settings for plugins

> >> >> What does that mean? It's not 100% perfect, but it does what it's intended >> to do quite well. Should we just start committing random changes so it's >> "actively developed"? > > > > It's not being updated for new Geany APIs, nor does the upstream developer > (you :-) review PRs in a

Re: [Geany-Devel] Future removal of Geany-Plugins from Fedora

On 13 November 2016 at 05:47, Matthew Brush wrote: > On 2016-11-11 03:24 PM, Matthew Brush wrote: >> >> Hi All, >> >> I was seeking help for some issue for the Markdown plugin with WebKitGtk >> today on IRC and someone pointed out this issue with Fedora: >> >>

Re: [Geany-Devel] Future removal of Geany-Plugins from Fedora

On 12 November 2016 at 09:24, Matthew Brush wrote: > Hi All, > > I was seeking help for some issue for the Markdown plugin with WebKitGtk > today on IRC and someone pointed out this issue with Fedora: > > https://bugzilla.redhat.com/show_bug.cgi?id=1375807 > > Basically the

Re: [Geany-Devel] Scintillua again.

On 21 October 2016 at 01:32, wrote: > As far as I can tell from reading some old posts and requests, Geany does not > support Scintillua. > > I am neither a C nor C++ programmer (although I am making some feeble efforts > at trying to write a lexer for Scintilla / Geany for a

Re: [Geany-Devel] OSX ports?

On 10 October 2016 at 16:09, Chris H wrote: > > Quoting Chris H : > Apologies, my mailer truncated my message... >> >> Greetings, >> Sorry if this has been asked in the past. I've attempted to find similar >> topics in the >> list archive. But to no avail. The link on Geany's

Re: [Geany-Devel] OSX ports?

The link on the Geany website seems to work http://www.geany.org/Download/Releases Cheers Lex On 10 October 2016 at 16:00, Chris H wrote: > > Greetings, > Sorry if this has been asked in the past. I've attempted to find similar > topics in the > list archive. But to no

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

[...]>> >> std::vector has a second parameter, which has a default value so its >> legal to omit it, but the type you will get from an accurate parser to >> store in TM will be the complete type which will be something like >> std::vector not just plain std::vector. >> This is

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

[...] >> It is of course always "possible", after all its a mere matter of >> programming :) >> >> And of course an instantiated class template is just a type, but what >> is the name of std::vector and std::vector so it can be looked >> up? > > > vector and vector, with scope being std (I think

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

On 31 August 2016 at 11:27, Matthew Brush wrote: > On 2016-08-30 06:43 AM, Colomban Wendling wrote: >> >> Le 29/08/2016 à 05:14, Matthew Brush a écrit : >>> >>> […] >>> >>> Syntax Highlighting >>> --- >>> >>> Most likely using an API based on/similar to

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

> > I think we all agree that help of language-specific plugins is > desired/required. No need to restate "we need language specific support" all > the time. > > We just disagree on how the language-specific knowledge is transported to > Geany, other plugins and the user. > Well, I read your

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

On 1 September 2016 at 00:55, Thomas Martitz <ku...@rockbox.org> wrote: > Am 31.08.2016 um 16:52 schrieb Lex Trotman: >> >> On 1 September 2016 at 00:43, Thomas Martitz <ku...@rockbox.org> wrote: >>> >>> Am 31.08.2016 um 16:39 schrieb Matthew Brush:

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

On 1 September 2016 at 00:43, Thomas Martitz wrote: > Am 31.08.2016 um 16:39 schrieb Matthew Brush: >> >> >> I can't speak to all compiler libraries, but at least libclang, libpython >> and libvala "compile" the source (well just the front-end of the compiler is >> needed).

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

> Why not? TM could have separate tags for each known template instance and > know which of these applies to someAs, based on information provided by a > ft-plugin. Then the rest would work. Yes, if Geany can be made to understand that `vector` and `vector< int >` and `vector ` are all the same

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

> I love Lex's ADL example, C++ can seem just crazy :) Crazy like a Fox, makes the compiler near impossible, but makes lots of stuff "just work" :) So a much simpler example then (using C syntax to explain since we all know it, but could be any language): int a; {

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

All I really wanted was a way to disable > Scintilla's lexer (ie. switch it to `SCLEX_CONTAINER`) without changing the > filetype in Geany, and without doing it behind Geany's back from the plugin. In fact some of the tools using scintilla and which provide a richer styling do exactly that,

Re: [Geany-Devel] [FT-plugins] Proposed "Features"

On 29 August 2016 at 22:38, Thomas Martitz <ku...@rockbox.org> wrote: > Am 29.08.2016 um 14:23 schrieb Lex Trotman: >> >> This adds per use case hooks to plugins, which then became part of the >> stable API. I don't think that we have to codify every single use case

Re: [Geany-Devel] [FT-plugins] Proposed Design

On 29 August 2016 at 12:30, Matthew Brush <mbr...@codebrainz.ca> wrote: > On 2016-08-28 06:59 PM, Lex Trotman wrote: >> >> On 29 August 2016 at 10:47, Matthew Brush <mbr...@codebrainz.ca> wrote: >>> >>> [...] >>> >>> "Registrat

Re: [Geany-Devel] [FT-plugins] Allowing plugins to supply filetype specific functionality

[...] > My proposition is that people without time or knowledge not contribute to > the development of this enhancement. Of course everyone would be able to > comment on stuff as it is merged back into master, but only those willing to > actively develop the solutions have any kind of strong voice

Re: [Geany-Devel] [FT-plugins] Allowing plugins to supply filetype specific functionality

[...] > I just meant for that meta tracker issue. It gets too hard to keep track of > what's going on when there's dozens and dozens of comments. I would expect > code-related discussions to happen on the individual PRs or separate ML > threads. I was thinking of the design discussion (see below)

Re: [Geany-Devel] Toggle menu and status bars

Ok a skinny burger (as used in chrome, three dots not three bars :) Cheers Lex On 7 July 2016 at 10:14, Matthew Brush wrote: > On 2016-07-06 05:10 PM, Steven Blatnick wrote: >> >> What does hamburger mean in this context? >> > >

  1   2   3   4   5   >