Your message dated Tue, 11 Apr 2023 12:59:51 -0400 with message-id <[email protected]> and subject line Re: Bug#1034205: wayout: does not do anything has caused the Debian Bug report #1034205, regarding wayout: does not do anything to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1034205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034205 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: wayout Version: 0.1.4-1 Severity: normal X-Debbugs-Cc: ~mil/[email protected] 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 "<b>bold</b>\n<span foreground=\"red\">red</span>" | 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 libc6 2.36-8 ii libcairo2 1.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
--- End Message ---
--- Begin Message ---On 2023-04-11 08:39:07, Willow Barraco wrote: > Wayout is a daemon and must keep running for the output to be preserved. Oh, okay, then it's not what I need at all then. Closing this bug... > The call | wayout is an example to demonstrate it take its input from > stdin. Well, I would argue it's a pretty bad example because it does precisely nothing by default, it's pretty confusing. :) > Wayout display things above the wallpaper. It is not an overlay that is > present above other surfaces. That's too bad! > 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. I guess I expected wayout to just fork and create a widget that will "stick" with whatever it was fed on stdin... Now instead I need to make my own daemon to keep track of that stuff myself! I guess there's actually no way for the user dismiss the widget either? A. -- The world is a dangerous place, not because of those who do evil, but because of those who look on and do nothing. - Albert Einstein
--- End Message ---
