all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: jgart <jgart@dismail.de>
Cc: paren@disroot.org, Tobias Geerinckx-Rice <me@tobias.gr>,
	59372-done@debbugs.gnu.org
Subject: bug#59372: [PATCH] gnu: peek: Add missing input.
Date: Sun, 29 Jan 2023 14:02:12 +0800	[thread overview]
Message-ID: <87o7qhj2u3.fsf_-_@envs.net> (raw)
In-Reply-To: <20221121145805.GB18341@dismail.de> (jgart@dismail.de's message of "Mon, 21 Nov 2022 14:58:05 -0600")

jgart <jgart@dismail.de> writes:

> On Mon, 21 Nov 2022 21:18:32 +0100 Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>> Does it not show that window on a foreign distribution?
>
> Yup, it does show that window on a foreign distro.
>
> So, we should just have the user install ffmpeg along with peek in their profile?
>
> Should this ticket be closed then? https://issues.guix.gnu.org/issue/51202#3

Yes, I think it's expected to install ffmpeg yourself for peek when not
in gnome shell.  Close now.




  reply	other threads:[~2023-01-29  6:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  1:27 [bug#59372] [PATCH] gnu: peek: Add missing input jgart via Guix-patches via
2022-11-19  2:50 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-19  4:07   ` jgart via Guix-patches via
2022-11-19  9:38     ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 14:27       ` jgart via Guix-patches via
2022-11-21 15:14         ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 20:18         ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 20:58           ` jgart via Guix-patches via
2023-01-29  6:02             ` 宋文武 via Guix-patches via [this message]
2022-11-21 17:13   ` zimoun
2022-11-21 19:38     ` jgart via Guix-patches via
2022-11-22 14:39       ` zimoun
2022-11-22 18:29         ` jgart via Guix-patches via
2022-11-19  9:13 ` ( via Guix-patches via

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

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

  git send-email \
    --in-reply-to=87o7qhj2u3.fsf_-_@envs.net \
    --to=guix-patches@gnu.org \
    --cc=59372-done@debbugs.gnu.org \
    --cc=iyzsong@envs.net \
    --cc=jgart@dismail.de \
    --cc=me@tobias.gr \
    --cc=paren@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.