I started working on a plugin that uses features of libclang for C/C++
projects (CDK = C/C++ Development Kit). The code is at:
If anyone is interested to help out in this early stage, especially with
the user interface and experience. I have some interesting features
working already but the way humans interact with the plugin really sucks.
If anyone is a C/GObject/Glade wizard and wants to help develop the
human interface to this plugin, please respond here or send me an email
I've been using Geany in Linux for a while and it really makes my life easier.
I wanted to share a couple of simple mods that will result familiar for people used to Visual Studio.
You can find them here
1) Changes the "Find" dialog boxes behavior like VS
behavior is changed mimicking VS IDE style.
a) Only one dialog can be displayed at the time.
b) Marked text is automatically loaded as text to the dialog "find" field.
2) Adds to the tab menu (right-click) an option ("Copy Full Path") giving the full path of the opened file .
Very handy when writing/commenting about code.
I consider VS IDE find dialog boxes style ubiquitous
I hope you guys can find these mods useful.
As on different channels people are getting nervous:
SF had some major issues with the storage. They are currently in
recovering mode. Until they finished, plugins.geany.org will not be
available -- at least I hope so it will be back later. Proactive
information from sf was not given so I only have the information from
Twitter¹ and related pages
We might will need to switch also plugin pages to our infrastructure later.
Our github-Repos are not effected by this as well as geany.org is fine.
Just wanted to check on the status of my pull request since it's been a
It's a relatively small change that adds support for argument hinting in
CUDA kernel calls (of the form MatAdd<<<numBlocks, threadsPerBlock>>>(A, B,
C);) as well as C# generic function calls (of the form Swap<int>(ref a, ref
I've never done a pull request before; is there anything else I need to do
to make a contribution?
On 20/07/15 22:32, Colomban Wendling wrote:
> Le 20/07/2015 22:28, Enrico Tröger a écrit :
>> On 20/07/15 14:46, Jiří Techet wrote:
>>> On Mon, Jul 20, 2015 at 11:19 AM, Lex Trotman <elextr(a)gmail.com> wrote:
>>>> Move plugins.geany.org to github pages. https://pages.github.com/
>>>> Attaches right to the repositories where the site source is.
>> I'm not keen on relying more and more on Github.
>> It's great service they offer, no doubt here. But since we already host
>> some services, especially web pages, I think we should also host
>> plugins.geany.org ourselves.
> Totally agreed. BTW, what is plugins2.g.o supposed to be? It exists,
> but it's mostly broken.
IIRC it was a test installation of Dominic.
>>> Or to the geany server - what matters is just to be far away from SF
>>> wherever it is...
>> That's the plan currently.
>> Already ealier today I emailed Dominic asking to assist in moving
>> plugins.geany.org to the geany server. Just waiting for his feedback.
>> But I'm afraid we have to wait to SF come back anyway because we
>> probably don't have the release tarballs anywhere else than on SF.
> Don't we have at least the latest ones, like on Frank's computer, and
> the installers on yours?
Ha, you are right. I actually have the tarballs as well as the installer
of the last release locally.
I'd like to wait for Dominic's feedback but in the worst case, I will
have a look tomorrow evening on getting it to work in any way.
Get my GPG key from http://www.uvena.de/pub.asc
Am 20.07.2015 um 10:31 schrieb Harold Aling:
> Sourceforge.net is blocked by default here (see attachment). This might
> be a good moment to move to a non-badware code hosting site?
Maybe. The geany-plugins downloads have not been effected by the "add
adds to installer"-issue earlier, so we just did not discussed it in a
After another long delay, we are finally happy to announce a new release
For a comprehensive list of changes please see:
* Fix spawning programs on Windows (for real this time!, Dimitar
* Use native Windows quoting rules for commands on Windows.
* Fix and improve MacOS X support (Jiří Techet).
* Show document-related dialogs embedded in the main window ("info
bars") (Matthew Brush and Thomas Martitz).
* Huge tag management performance improvement (auto-completion,
calltips, etc.) (Jiří Techet).
* Update Scintilla to 3.5.6.
* GTK3 support, while not enabled by default, is now considered stable.
* Add support for single-line regular expressions.
* Add filetypes CoffeScript (Mark Dresselhaus), JSON, Zephir.
* Significantly improved filtypes CSS, Erlang (Beng Tan), Go (Jiří
* Update translations: be, ca, cs, de, el, es, fr, id, it, ja, nl, pl,
pt_BR, pt, ru, sl, sr, sv, zh_CN.
We want to thank all developers, translators and everyone who
contributed to this release with patches, feedback, bug reports and so
on. Thank you!
As usual, all downloads can be found on
http://www.geany.org/Download/Releases. But this time you'll also find
a MacOS X DMG, thanks to Jiří Techet!
Additionally, to try and avoid another long delay before the next
version, we decided to try and embrace a time-based 4 months release
schedule. If we can stick to it, next release should come out around
As anyone trying to follow Pull Requests on Github has probably noticed,
when you force push to your PR branch, Github deletes various comments
related to the PR, depending on what got clobbered (it seems).
This makes it extremely difficult to keep track of and finally merge PRs
because issues that may have been raised are gone and it leaves holes in
the comments which are a useful way to make sure any issues, notes,
ideas, etc. have been dealt with before merging.
In addition to the dropped comments, it makes it harder to follow the
changes made since it clobbers the Git history too, so you have to
basically review the entire changset by looking at the whole diff of all
files affected by the PR at once.
Another reason to avoid is because it makes it harder to test a PR if
the repos history keeps getting munged, it breaks your previous pulls.
I propose that we disallow force pushing, rebasing, squashing, etc. on
any PR until it is fully ready for final merging. We could probably use
a label or milestone or something to signify that a PR has been fully
reviewed and is ready for merging. At that point it _might_ make sense
to fudge history and get rid of some noisy "fixup" commits.
If it sounds like a good idea, I could probably try and update any
relevant documentation (HACKING comes to mind) to make a note of this.
: I personally don't think it's a big deal leaving the history to
match real life, but I can see how "Fix some typo" type of commits
aren't very useful to keep around.
: Although force pushing is generally considered bad-practice on
public branches, so I doubt too many people would do it without being asked.
I would like to add GeanyHighlightSelectedWords, to Geany Plugins.Would it be okay that I do a git pull-request for doing this? I
am the mgnt user on sourceforge, and last week there was a ticketadded to GeanyHighlightSelectedWords, ticket #2, and in thisticket was a question: why not make a pull-request to Geany Plugins.
I know there would be some things I would need to do before, likereplace the Makefile with Makefile.am, the autotools, automake way,and write a README file using restructured text content so that thatREADME file can be converted to html. Maybe there is more thatshould be done.
I hope my question is okay.
Have a great day,Marius Ioan Buzea
Hi. I'm just learning to do some programming using SWI Prolog and is
using Geany as my IDE on Ubuntu. Since Geany does not currently support
Prolog, I have used the information from the syntax highlighting file
from Notepad++ to make a filetypes.Prolog.conf file. I am using the
lexer_filetype=C for this purpose, and everything seems to be working
fine as far as I can tell, except for single line comment. The single
line comment for Prolog is %% but does not seem to be working as Geany
still recognizes // instead.
Also, whom do I send my conf file to for consideration?