> From: devel-request@lists.geany.org
> Subject: Devel Digest, Vol 87, Issue 27
> To: devel@lists.geany.org
> Date: Sun, 28 Jun 2015 09:00:02 +0000
>
> Send Devel mailing list submissions to
> devel@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@lists.geany.org
>
> You can reach the person managing the list at
> devel-owner@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@gmail.com>
> To: Geany development list <devel@lists.geany.org>
> Subject: Re: [Geany-Devel] Spawn module API
> Message-ID:
> <CAKhWKDP9E-pcyrUQT0Og7wB-g45BnPT_RBoGM=4-F3LYKcAs3w@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 28 June 2015 at 12:40, Matthew Brush <mbrush@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@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@gmail.com>
> To: Geany development list <devel@lists.geany.org>
> Subject: Re: [Geany-Devel] Spawn module API
> Message-ID:
> <CAKhWKDPoVZmA--NnLxW83q4UNQxqyXdmYD9YJfAq+NqztewGTg@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 28 June 2015 at 12:54, Lex Trotman <elextr@gmail.com> wrote:
> > On 28 June 2015 at 12:40, Matthew Brush <mbrush@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@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@codebrainz.ca>
> To: devel@lists.geany.org
> Subject: Re: [Geany-Devel] Spawn module API
> Message-ID: <558F667E.90903@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@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@lists.geany.org
> https://lists.geany.org/cgi-bin/mailman/listinfo/devel
>
>
> ------------------------------
>
> End of Devel Digest, Vol 87, Issue 27
> *************************************