unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Jaft <jaft.r@outlook.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "63558@debbugs.gnu.org" <63558@debbugs.gnu.org>
Subject: [bug#63558] [PATCH] gnu: Add qutebrowser/wayland.
Date: Sat, 2 Sep 2023 06:04:12 +0000 (UTC)	[thread overview]
Message-ID: <BY5PR07MB70293EE113B4957694B536B399EBA@BY5PR07MB7029.namprd07.prod.outlook.com> (raw)
In-Reply-To: <87msy62cm2.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

 I'm running XWayland and, at one point, it just stopped working (would launch in X, instead); it's been a while since I ran it (I've been running this version, instead) but I think that was why I wrote this up. Even when it was working, launching it from an X app. would cause it to run as X. I remember it being really annoying in unexpected ways and not always predictable.    On Friday, September 1, 2023 at 09:26:49 AM CDT, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:  
 
 Hi,

"Wamm K. D" <jaft.r@outlook.com> writes:

> * gnu/packages/web-browsers.scm (qutebrowser/wayland): New variable.
> ---
> Create a package that can be used with Wayland, like UnGoogled
> Chromium and Icecat have.

There's a difference though; here qutebrowser uses Qt, and qtwayland
works as a plugin, so as long as it's found in your user profile it
should just work.  Is it not the case?

I'd like to avoid adding package variants if possible.

-- 
Thanks,
Maxim
  

[-- Attachment #2: Type: text/html, Size: 2185 bytes --]

  reply	other threads:[~2023-09-02  6:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 20:00 [bug#63558] [PATCH] gnu: Add qutebrowser/wayland Wamm K. D
2023-09-01 14:26 ` Maxim Cournoyer
2023-09-02  6:04   ` Jaft [this message]
2023-09-03 14:53     ` bug#63558: " Maxim Cournoyer

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=BY5PR07MB70293EE113B4957694B536B399EBA@BY5PR07MB7029.namprd07.prod.outlook.com \
    --to=jaft.r@outlook.com \
    --cc=63558@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).