Bug#1034205: wayout: does not do anything

2023-04-27 Thread Antoine Beaupré
On 2023-04-22 20:09:57, Anjandev Momi wrote:
> Hi Antoine!
>
>> I can't figure out how to use this program.
>>
>> The upstream README (which is actually not shipped with the Debian
>> package) has a few examples:
>> So, how does one use this?
>
> You can find a better example of wayout usage here:
>
> https://git.sr.ht/~mil/sxmo-utils/tree/f630b2bbdb712f0a3bb66778efcdf196d1d093e4/item/configs/default_hooks/sxmo_hook_desktop_widget.sh
>
> I always modify the above script because the script works out of the box on
> every device I've tried Sxmo on.
>
> I agree the wayout *man page* should include a better example of how to
> make wayout work. If you find the time, please do some trial and error
> and send us a patch with your improved wayout man page here:
>
> https://sxmo.org/contribute
>
> Alternatively, conky got wayland support recently and Sxmo 1.14.1 supports
> conky. I like wayout cause old habits die hard.

Right. :) So my use case is I want to create a pop-up in a status bar
that doesn't quite support this. Having to run a process in the
background for this is not exactly the best scenario, as I'd need to
implement process management in the thing, which is a little sub par (as
opposed to just forking a process and let it kill itself based on user
interaction).

So I guess it's more something I should check with the status bar...

a.
-- 
The lazy man does not stand in the way of progress. When he sees
progress roaring down upon him he steps nimbly out of the way
 - Christopher Morley, "On Laziness"



Bug#1034205: wayout: does not do anything

2023-04-22 Thread Anjandev Momi
Hi Antoine!

> I can't figure out how to use this program.
>
> The upstream README (which is actually not shipped with the Debian
> package) has a few examples:
> So, how does one use this?

You can find a better example of wayout usage here:

https://git.sr.ht/~mil/sxmo-utils/tree/f630b2bbdb712f0a3bb66778efcdf196d1d093e4/item/configs/default_hooks/sxmo_hook_desktop_widget.sh

I always modify the above script because the script works out of the box on
every device I've tried Sxmo on.

I agree the wayout *man page* should include a better example of how to
make wayout work. If you find the time, please do some trial and error
and send us a patch with your improved wayout man page here:

https://sxmo.org/contribute

Alternatively, conky got wayland support recently and Sxmo 1.14.1 supports
conky. I like wayout cause old habits die hard.

Thank you for using wayout!
Anjan
--
w:] www.momi.ca
pgp:] https://momi.ca/publickey.txt



Bug#1034205: wayout: does not do anything

2023-04-11 Thread Willow Barraco
Wayout is a daemon and must keep running for the output to be preserved.
The call | wayout is an example to demonstrate it take its input from
stdin.
Wayout display things above the wallpaper. It is not an overlay that is
present above other surfaces.
If the pipe shut down, then the stdin is broken, and so Wayout shutdown.

I think what you can do is to prepare a fifo file that Wayout will read.
You then can feed this file from outside, the way you want.



Bug#1034205: wayout: does not do anything

2023-04-10 Thread Antoine Beaupre
Package: wayout
Version: 0.1.4-1
Severity: normal
X-Debbugs-Cc: ~mil/sxmo-de...@lists.sr.ht

I can't figure out how to use this program.

The upstream README (which is actually not shipped with the Debian
package) has a few examples:

> Static example for a calendar:
> 
> $ cal | wayout
> 
> Example to use wayout as a simple digital clock using --feed-line:
> 
> $ while; do date +%H:%M:%S; sleep 1; done | wayout --feed-line
> 
> You can use the pango markup language for text markup and colours:
> 
> $ echo "bold\nred" | wayout

Yet those don't really work so well:

 1. the first example just immediately exits and leaves no trace of
 a calendar in the output

 2. the second example *does* work, but is buried under all the other
 windows, so it's actually pretty hard to tell it actually *did* work
 unless you know where to look for it

 3. the third example fails for the same reason as the first
 (presumably?)

It looks like wayout immediately exits when the pipe shuts down, and
tears out its own widget alongside. For example, the first example, in
verbose mode, says this:

anarcat@angela:~$ cal | wayout --verbose
[main] wayout: version=0.1.4
[main] w=320 h=240 font=Monospace 26
[main] Init Wayland.
[output] Creating: global_name=44
[output] Configuring: global_name=44
[main] Starting loop.
[main] Got end of input, exiting
[main] Finish Wayland.
[output] Destroying all outputs.

Interestingly, using `--feed-line` with `cal` kind of works if you
squint a little, except not really: it only outputs the last line of
the calendar.

So, how does one use this?

My use case is to make a pop-up on a keybinding or a status bar
button, for example to show a calendar or undertime(1) in an overlay.

Thanks!

a.

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'stable-security'), (500, 
'testing'), (500, 'stable'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wayout depends on:
ii  libc62.36-8
ii  libcairo21.16.0-7
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libwayland-client0   1.21.0-1

wayout recommends no packages.

wayout suggests no packages.

-- no debconf information