Hi,
Just wanted to check on the status of my pull request since it's been a
while: https://github.com/geany/geany/pull/496
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
b);).
I've never done a pull request before; is there anything else I need to do
to make a contribution?
Cheers
~ Ethan
Hello,
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've built new Windows installers from current GIT master.
Downloads can be found here:
http://download.geany.org/snapshots/
Please note that these are test builds from the current development
version, don't expect release quality.
You have been warned :).
After you installed the snapshots, you can also use the nightly
builds again on Windows (i.e. copy the archive contents over the
installation).
Any feedback is welcome.
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
Hello
I have just noticed that current git, by default, doesn't prompt anymore
when reloading documents, even when they are changed.
I traced it back to the $SUBJECT commit. IMO it's fine to keep the undo
history on reload and not prompt, but it's not fine if the file is
currently modified (unsaved) and reloading throws all unsaved changes
away, without warning.
This is especially problematic because the new pref is on by default so
users will probably be surprised by the new, changed behavior and lose
some hours of work (happend to me...).
I'm asking for restoring the prompt (by default), at the very least if
the file is unsaved.
Best regards
Hi folks,
I need to apologize! Due to chunky fingers I accidentally forced-push an
old head to geany-plugins master repo. Colomban was able to recover the
old state (inkl. same sha) but your client might, depending on when you
have cloned/pull the repo, complain that there is something suspicions.
So don't panic! Everything under control.
Cheers,
Frank
Hi, all,
Taking point from:
On 28.6.2015 г. 06:14, Matthew Brush wrote:
> It can easily be made available on-demand, as normal.
I'm renewing my request for ui_setup_open_button_callback to be made
available for the plugins. By the time I first requested it, there were
plugins with their own versions (inferior - no native Win32 dialogs),
and currently, it seems that geanylua, spellcheck and scope imitate it.
To save you some browsing of the mailing list archives, the following
points were raised at the time:
"GtkFileChooserButton should be used" - however, Scope requires file and
directory names which may not exist at the moment of choice, and if
memory serves me, the file chooser button / dialog does not support
names in $PATH either.
"It should be properly g-object-ified" - well, nobody was willing to do
that, much less add Glade support.
(@Matthew: yes, I have plans to use it, had them from >= 2 years. :)
Currently, my hope is to use it from the stable 1.25 release, if
possible, or whenever it becomes available.)
There are other things I need, but let's see how this will it turn out...
--
E-gards: Jimmy
Hi All,
I just noticed that the new spawn code exposes almost every single bit
of API possible. Do we really want to do that, or should we limit it
only to what is currently needed by any plugins? A quick survey of
Geany-Plugins shows no usage of any of this yet.
IMO, we shouldn't expose anything which is not needed by plugins,
especially if it's not related to the plugin API.
Cheers,
Matthew Brush
Hi everyone! ,
I want to pick a project to work on and needed some help. I was wondering what would be a perfect beginners project/ or practise assignment. Also, if there is such a thing what files should I read and what source code should I take a look at.
PS: I have looked at the HACKING file and have had a decent look at the bugs and feature requests
Thanks,
Atal Akbari
> From: devel-request(a)lists.geany.org
> Subject: Devel Digest, Vol 87, Issue 27
> To: devel(a)lists.geany.org
> Date: Sun, 28 Jun 2015 09:00:02 +0000
>
> Send Devel mailing list submissions to
> devel(a)lists.geany.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.geany.org/cgi-bin/mailman/listinfo/devel
> or, via email, send a message with subject or body 'help' to
> devel-request(a)lists.geany.org
>
> You can reach the person managing the list at
> devel-owner(a)lists.geany.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Devel digest..."
>
>
> Today's Topics:
>
> 1. Re: Spawn module API (Lex Trotman)
> 2. Re: Spawn module API (Lex Trotman)
> 3. Re: Spawn module API (Matthew Brush)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 28 Jun 2015 12:54:56 +1000
> From: Lex Trotman <elextr(a)gmail.com>
> To: Geany development list <devel(a)lists.geany.org>
> Subject: Re: [Geany-Devel] Spawn module API
> Message-ID:
> <CAKhWKDP9E-pcyrUQT0Og7wB-g45BnPT_RBoGM=4-F3LYKcAs3w(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 28 June 2015 at 12:40, Matthew Brush <mbrush(a)codebrainz.ca> wrote:
> > On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:
> >>
> >> [...]
> >>
> >> An updated list of the API-s asked to remain public:
> >>
> >> me WIF*
> >> lex spawn_get_program_name
> >> lex spawn_check_command
> >> me/lex spawn_kill_process
> >> spawn_async_with_pipes
> >> lex spawn_async
> >> me/lex spawn_with_callbacks
> >> me spawn_write_data
> >> lex? spawn_get_exit_status_cb
> >> lex spawn_sync
> >>
> >
> > We should only export what you have concrete plans to use during the next
> > cycle. If Lex wants update plugins during the next cycle to use other parts
> > of the API, we can expose them at the time that the PR is made. No point to
> > speculatively expose API that nobody has immediate plans to use.
>
> If no API is available then nobody will have any plans so no API is
> needed so nobody will have any plans for the egg so no chicken is
> needed so ....
>
>
> >
> > Cheers,
> > Matthew Brush
> > _______________________________________________
> > Devel mailing list
> > Devel(a)lists.geany.org
> > https://lists.geany.org/cgi-bin/mailman/listinfo/devel
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 28 Jun 2015 13:04:07 +1000
> From: Lex Trotman <elextr(a)gmail.com>
> To: Geany development list <devel(a)lists.geany.org>
> Subject: Re: [Geany-Devel] Spawn module API
> Message-ID:
> <CAKhWKDPoVZmA--NnLxW83q4UNQxqyXdmYD9YJfAq+NqztewGTg(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 28 June 2015 at 12:54, Lex Trotman <elextr(a)gmail.com> wrote:
> > On 28 June 2015 at 12:40, Matthew Brush <mbrush(a)codebrainz.ca> wrote:
> >> On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:
> >>>
> >>> [...]
> >>>
> >>> An updated list of the API-s asked to remain public:
> >>>
> >>> me WIF*
> >>> lex spawn_get_program_name
> >>> lex spawn_check_command
> >>> me/lex spawn_kill_process
> >>> spawn_async_with_pipes
> >>> lex spawn_async
> >>> me/lex spawn_with_callbacks
> >>> me spawn_write_data
> >>> lex? spawn_get_exit_status_cb
> >>> lex spawn_sync
> >>>
> >>
> >> We should only export what you have concrete plans to use during the next
> >> cycle. If Lex wants update plugins during the next cycle to use other parts
> >> of the API, we can expose them at the time that the PR is made. No point to
> >> speculatively expose API that nobody has immediate plans to use.
> >
> > If no API is available then nobody will have any plans so no API is
> > needed so nobody will have any plans for the egg so no chicken is
> > needed so ....
>
> Or to look at it another way:
>
> "Welcome to Geany 1.25, so that their command parsing is the same as
> Geanys, all plugins are recommended to upgrade to the spawn_* API -
> that we havn't released."
>
> Cheers
> Lex
>
>
> >
> >
> >>
> >> Cheers,
> >> Matthew Brush
> >> _______________________________________________
> >> Devel mailing list
> >> Devel(a)lists.geany.org
> >> https://lists.geany.org/cgi-bin/mailman/listinfo/devel
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 27 Jun 2015 20:14:06 -0700
> From: Matthew Brush <mbrush(a)codebrainz.ca>
> To: devel(a)lists.geany.org
> Subject: Re: [Geany-Devel] Spawn module API
> Message-ID: <558F667E.90903(a)codebrainz.ca>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 2015-06-27 07:54 PM, Lex Trotman wrote:
> > On 28 June 2015 at 12:40, Matthew Brush <mbrush(a)codebrainz.ca> wrote:
> >> On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:
> >>>
> >>> [...]
> >>>
> >>> An updated list of the API-s asked to remain public:
> >>>
> >>> me WIF*
> >>> lex spawn_get_program_name
> >>> lex spawn_check_command
> >>> me/lex spawn_kill_process
> >>> spawn_async_with_pipes
> >>> lex spawn_async
> >>> me/lex spawn_with_callbacks
> >>> me spawn_write_data
> >>> lex? spawn_get_exit_status_cb
> >>> lex spawn_sync
> >>>
> >>
> >> We should only export what you have concrete plans to use during the next
> >> cycle. If Lex wants update plugins during the next cycle to use other parts
> >> of the API, we can expose them at the time that the PR is made. No point to
> >> speculatively expose API that nobody has immediate plans to use.
> >
> > If no API is available then nobody will have any plans so no API is
> > needed so nobody will have any plans for the egg so no chicken is
> > needed so ....
> >
>
> It can easily be made available on-demand, as normal.
>
> We should only be concerned about what Scope is requesting as it has
> concrete plans to use them during the next development cycle and doesn't
> want the plugin to depend on the next development version of Geany
> during that time[0]. There's no reason to speculatively rush other APIs
> in if no plugins have immediate plans to use them nor have the concern
> about depending on the development version of Geany.
>
> Cheers,
> Matthew Brush
>
> [0]: Which IMO is a kind of tenuous reason since most people will use
> the version of Scope that their distro provides or from other releases,
> which for the most part means the next released version of Geany/GP
> anyway. I guess maybe some bleeding edge distros might package it
> in-between releases or something, though.
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Devel mailing list
> Devel(a)lists.geany.org
> https://lists.geany.org/cgi-bin/mailman/listinfo/devel
>
>
> ------------------------------
>
> End of Devel Digest, Vol 87, Issue 27
> *************************************
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
Hello, my name is Minh and I'm currently a sophomore in college, looking
for open source project to strengthen my coding skill. I know Java and C
and have a little exposure to C++. I have previously used Geany a lot for
doing my school assignments and recently I stumbled across the development
section. I'm still very new in contributing to a large scale project like
this. I look forward to work along with the team.