On 27.6.2015 г. 23:50, Lex Trotman wrote:
On 28 June 2015 at 05:46, Dimitar Zhekovdimitar.zhe...@gmail.com wrote:
On 27.6.2015 г. 04:40, Lex Trotman wrote:
spawn_write_data
This one looks platform independent, but it's actually very easy to create
a stdin-write function that blocks under
Am 28.06.2015 um 05:14 schrieb Matthew Brush:
On 2015-06-27 07:54 PM, Lex Trotman wrote:
On 28 June 2015 at 12:40, Matthew Brush mbr...@codebrainz.ca wrote:
On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:
[...]
An updated list of the API-s asked to remain public:
meWIF*
lex
On 28 June 2015 at 05:46, Dimitar Zhekov dimitar.zhe...@gmail.com wrote:
On 27.6.2015 г. 04:40, Lex Trotman wrote:
My concern is that, for a given platform, all commands a user enters
into Geany or plugins should use the same meta chars and quoting.
[...]
Well, after we could not agree on
On 28 June 2015 at 12:40, Matthew Brush mbr...@codebrainz.ca wrote:
On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:
[...]
An updated list of the API-s asked to remain public:
meWIF*
lexspawn_get_program_name
lexspawn_check_command
me/lexspawn_kill_process
On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:
[...]
An updated list of the API-s asked to remain public:
meWIF*
lexspawn_get_program_name
lexspawn_check_command
me/lexspawn_kill_process
spawn_async_with_pipes
lexspawn_async
me/lexspawn_with_callbacks
me
On 28 June 2015 at 12:54, Lex Trotman ele...@gmail.com wrote:
On 28 June 2015 at 12:40, Matthew Brush mbr...@codebrainz.ca wrote:
On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:
[...]
An updated list of the API-s asked to remain public:
meWIF*
lexspawn_get_program_name
lex
On Fri, Jun 26, 2015 at 3:31 AM, Lex Trotman ele...@gmail.com wrote:
There is also a custom spawn in geanyctags, I didn't look at what it
did differently.
There isn't - I'm using utils_spawn_sync() inside the spawn_cmd() function.
Cheers,
Jiri
On 24.6.2015 г. 02:05, Colomban Wendling wrote:
BTW, I just noticed that on Windows spawn_async_with_pipes() requires
the GLib main loop to be running if child_pid=NULL (well, it registers a
watch func, not sure what happens if it doesn't execute -- zombie?).
We probably don't care much though.
On 26.6.2015 г. 01:47, Lex Trotman wrote:
Hi Dimitar,
Hi, Lex.
On 26 June 2015 at 03:13, Dimitar Zhekovdimitar.zhe...@gmail.com wrote:
It uses quoting internally [...bla-bla-bla unneeded tech details...]
I'm now totally confused, so let me ask the important question directly:
I should
On 27 June 2015 at 03:13, Dimitar Zhekov dimitar.zhe...@gmail.com wrote:
On 26.6.2015 г. 01:47, Lex Trotman wrote:
Hi Dimitar,
Hi, Lex.
On 26 June 2015 at 03:13, Dimitar Zhekovdimitar.zhe...@gmail.com wrote:
It uses quoting internally [...bla-bla-bla unneeded tech details...]
I'm now
On 26 June 2015 at 17:45, Jiří Techet tec...@gmail.com wrote:
On Fri, Jun 26, 2015 at 3:31 AM, Lex Trotman ele...@gmail.com wrote:
There is also a custom spawn in geanyctags, I didn't look at what it
did differently.
There isn't - I'm using utils_spawn_sync() inside the spawn_cmd()
On 24.6.2015 г. 03:12, Lex Trotman wrote:
On 24 June 2015 at 10:06, Colomban Wendlinglists@herbesfolles.org wrote:
Le 24/06/2015 01:57, Lex Trotman a écrit :
Colomban,
Correct me if I'm wrong, but despite my loudly voiced misgivings :)
doesn't the spawn_* series do command quoting and
On 2015-06-20 08:12 PM, Matthew Brush wrote:
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
On 26 June 2015 at 11:11, Matthew Brush mbr...@codebrainz.ca wrote:
On 2015-06-20 08:12 PM, Matthew Brush wrote:
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
On 23.6.2015 г. 02:25, Matthew Brush wrote:
[...]
One thing I forgot: the plugin API currently exports
utils_spawn_[a]sync, and a few plugins use utils_spawn_sync. These
functions were (partially correct) wrappers around the old glib/win32
spawn, and are now wrappers around spawn_[a]sync.
Le 24/06/2015 00:18, Matthew Brush a écrit :
[…]
I think the general policy is to export stuff on demand as plugins need
it. Seeing as you wrote the API in question, I'm assuming you know best
the stuff you will need, so I don't personally see much problem
preemptively exposing that
Le 24/06/2015 01:57, Lex Trotman a écrit :
Colomban,
Correct me if I'm wrong, but despite my loudly voiced misgivings :)
doesn't the spawn_* series do command quoting and g_spawn* not?
If that the case they should not be mixed on the same platform
otherwise the user has to know which
On 2015-06-23 09:04 AM, Dimitar Zhekov wrote:
On 23.6.2015 г. 02:25, Matthew Brush wrote:
[...]
One thing I forgot: the plugin API currently exports
utils_spawn_[a]sync, and a few plugins use utils_spawn_sync. These
functions were (partially correct) wrappers around the old glib/win32
spawn,
On 2015-06-23 01:40 PM, Lex Trotman wrote:
On 24 June 2015 at 02:04, Dimitar Zhekov dimitar.zhe...@gmail.com wrote:
On 23.6.2015 г. 02:25, Matthew Brush wrote:
[...]
One thing I forgot: the plugin API currently exports utils_spawn_[a]sync,
and a few plugins use utils_spawn_sync. These
On 24 June 2015 at 10:06, Colomban Wendling lists@herbesfolles.org wrote:
Le 24/06/2015 01:57, Lex Trotman a écrit :
Colomban,
Correct me if I'm wrong, but despite my loudly voiced misgivings :)
doesn't the spawn_* series do command quoting and g_spawn* not?
If that the case they should
On 21.6.2015 г. 20:39, Matthew Brush wrote:
On 2015-06-21 04:25 AM, Dimitar Zhekov wrote:
On 21.6.2015 г. 06:12, Matthew Brush wrote:
[...]
Spawn neither requires not uses anything from Geany (except i18n), and
does not change anything in Geany state, so it's functions are not
Yeah, it
On 2015-06-20 08:12 PM, Matthew Brush wrote:
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
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
23 matches
Mail list logo
