unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Murilo via Guix-patches via <guix-patches@gnu.org>
To: "outlook user" <RACP@outlook.fr>,
	"73103@debbugs.gnu.org" <73103@debbugs.gnu.org>
Subject: [bug#73103] TR:
Date: Wed, 18 Dec 2024 10:07:23 -0300	[thread overview]
Message-ID: <D6EULB4YXA9R.SWLZPFCNWGI@disroot.org> (raw)
In-Reply-To: <GVXP251MB0839D62659EC9D8E8343353297052@GVXP251MB0839.EURP251.PROD.OUTLOOK.COM>

> There should be a place where all that is advertised (outside Guix official channels to avoid conflict when that applies). I'm so clueless personally

I find toys to be more than enough to be honest, maybe it needs some more
advertising, but once you know about it, works wonders, it shows both guix and
outside of guix (user channels).

>> streams not playing
> You mean like Twitch or YouTube or videocall or something else? Personally with the AppImage everything was working fine (but I haven't checked everything possible)

I mean twitch streams and youtube streams. Video calls work fine, twitch videos
(VODs) work fine, youtube videos work fine. Might be something I missed when
packaging but honestly I don't mind since I use mpv to watch everything anyways.

>> running on native wayland
> What was the workaround/solution? Personally it receives the order to use WayLand

I didn't do anything special, I just open zen and it is already native wayland,
no tweaks, no flags, no nothing, just plain executing the `zen` command. My WM
also shows the window is native wayland, and I even use hardware accel from GPU
on native wayland with it just fine.
I do have couple env vars for wayland set: QT_QPA_PLATFORM=wayland
XDG_SESSION_TYPE=wayland XDG_CURRENT_DESKTOP=Hyprland

>> use the channel
> Last time I messed with channels I've had to maintain a whole version control system **just** to figure out what wasn't working, took me, idk, months of maintenance time, weeks of mind time and maybe hours/day of actual time. Maybe you know a foolproof way or something?

I'm not sure, I've never had any problems with using channels. Outside of what
we already have in the manual for how to use channels, I just make sure the
package symbols I'm using on my config match the ones I want to use (sometimes
channels duplicate them, then using #:hide or #:select for modules help) and
that's about it. If anything, guix pull lets you roll back if something breaks.




  reply	other threads:[~2024-12-18 13:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07 14:46 [bug#73103] [PATCH] gnu: zen: Adding Zen browser outlook user
2024-09-20 21:48 ` bug#73103: " Vagrant Cascadian
2024-12-17 15:09 ` [bug#73103] outlook user
2024-12-17 15:41   ` [bug#73103] outlook user
     [not found]   ` <AS8P251MB0854CF0508C3ABD9BE64930997042@AS8P251MB0854.EURP251.PROD.OUTLOOK.COM>
     [not found]     ` <87seqmb6kv.fsf@xn--no-cja.eu>
2024-12-17 19:11       ` [bug#73103] TR: outlook user
2024-12-17 19:50         ` [bug#73103] outlook user
2024-12-17 19:57           ` [bug#73103] outlook user
2024-12-17 23:22         ` [bug#73103] TR: Noé Lopez via Guix-patches via
2024-12-18  0:28           ` Murilo via Guix-patches via
2024-12-18  7:00             ` outlook user
2024-12-18 13:07               ` Murilo via Guix-patches via [this message]
2024-12-18  6:37           ` [bug#73103] outlook user
2024-12-18  6:13 ` [bug#73103] outlook user

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D6EULB4YXA9R.SWLZPFCNWGI@disroot.org \
    --to=guix-patches@gnu.org \
    --cc=73103@debbugs.gnu.org \
    --cc=RACP@outlook.fr \
    --cc=murilo@disroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).