(I'm not sure what is the best channel to discuss jalv.select
development other than opening a Github issue right away. If this is not
the right place, please direct to me to an appropriate mailing list.)
Currently, if I have jalv.select already running, whether minimized or
not, and try to run it
Am 28.03.2016 um 15:00 schrieb Christopher Arndt:
(I'm not sure what is the best channel to discuss jalv.select
development other than opening a Github issue right away. If this is not
the right place, please direct to me to an appropriate mailing list.)
Currently, if I have jalv.select alread
Am 28.03.2016 um 15:00 schrieb Christopher Arndt:
What I would ideally like is that, if jalv.select is already running and
you start another instance, the running instance opens its window (if
minimized). That would require some kind of IPC, so I'm not sure, if
this is something that's worth a
Hi Hermann,
Am 30.03.2016 um 13:03 schrieb Hermann Meyer:
> So I've added a named pipe to jalv.select, so that communication with
> the app is possible.
> Currently it understand "quit", "show" and "hide".
that's great, thanks!
Is that fifo always created in the working dir or is there a way to
Am 30.03.2016 um 13:40 schrieb Christopher Arndt:
Hi Hermann,
Am 30.03.2016 um 13:03 schrieb Hermann Meyer:
So I've added a named pipe to jalv.select, so that communication with
the app is possible.
Currently it understand "quit", "show" and "hide".
that's great, thanks!
Is that fifo always
Am 30.03.2016 um 18:53 schrieb Hermann Meyer:
> I've set the fifo-path now to /tmp instead working dir, to ensure that
> "all" instances use the same fifo and have access to it.
Not that it's a very common usage scenario, but won't that preclude
jalv.select being used by different users on the sam
Am 30.03.2016 um 19:28 schrieb Christopher Arndt:
Am 30.03.2016 um 18:53 schrieb Hermann Meyer:
I've set the fifo-path now to /tmp instead working dir, to ensure that
"all" instances use the same fifo and have access to it.
Not that it's a very common usage scenario, but won't that preclude
j
Am 31.03.2016 um 05:45 schrieb Hermann Meyer:
> I like to have it in /tmp, because, for the case that jalv.select ended
> unexpected, the fifo get deleted at lest when you shut down the machine.
> In home, it may exist for ever, at least.
Good point.
You could append the UID to the fifo name.
Ch
Am 31.03.2016 um 09:51 schrieb Christopher Arndt:
Am 31.03.2016 um 05:45 schrieb Hermann Meyer:
I like to have it in /tmp, because, for the case that jalv.select ended
unexpected, the fifo get deleted at lest when you shut down the machine.
In home, it may exist for ever, at least.
Good point
Am 31.03.2016 um 12:11 schrieb Hermann Meyer:
> Am 31.03.2016 um 09:51 schrieb Christopher Arndt:
>> You could append the UID to the fifo name.
>>
> Also a good point. done.
Perfect.
One more thing: Whereas, when I run the first instance, itsw window
always opens horizontally centered on my deskt
Am 31.03.2016 um 13:19 schrieb Christopher Arndt:
Am 31.03.2016 um 12:11 schrieb Hermann Meyer:
Am 31.03.2016 um 09:51 schrieb Christopher Arndt:
You could append the UID to the fifo name.
Also a good point. done.
Perfect.
One more thing: Whereas, when I run the first instance, itsw windo
And I guess it warrants a release, did I understand it right, you guys
devised a command-line interface to jalv.select, right? Like I used
jalv.select to lauch say, Sorcer, and now...? Please, can you give me
one ore more use-cases? It sounds interesting. AND jalv.select actually
never made the
12 matches
Mail list logo
