From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Add helper for .desktop file creation? Date: Mon, 27 May 2019 19:58:19 +0200 Message-ID: <87y32rkcec.fsf@ambrevar.xyz> References: <878suwz3tg.fsf@ambrevar.xyz> <87d0k67n7n.fsf@nicolasgoaziou.fr> <878suu7mhk.fsf@nicolasgoaziou.fr> <87r28mofxd.fsf@ambrevar.xyz> <87r28m64m5.fsf@nicolasgoaziou.fr> <87o93qobso.fsf@ambrevar.xyz> <8736l2nzwm.fsf@ambrevar.xyz> <877eacmksu.fsf@ambrevar.xyz> <878sur6fgl.fsf@nicolasgoaziou.fr> <87blznlubm.fsf@ambrevar.xyz> <874l5f6bl7.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:58545) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVJtM-0001K2-FW for guix-devel@gnu.org; Mon, 27 May 2019 13:58:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hVJtG-0003Ti-RH for guix-devel@gnu.org; Mon, 27 May 2019 13:58:32 -0400 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:46071) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hVJtE-0003Pk-04 for guix-devel@gnu.org; Mon, 27 May 2019 13:58:28 -0400 In-Reply-To: <874l5f6bl7.fsf@nicolasgoaziou.fr> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Nicolas Goaziou Cc: Guix-devel --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Nicolas Goaziou writes: > I was thinking about a match against key before (match value ...), which > would then match value against a chosen predicate, and return an error > if it doesn't match. > ... Could work, I'll see what I can do. But first I'd like to know how to actually add this to Guix! :) Rebuild the world on core-updates or is there another way? >>> The docstring may explain that, e.g., compound :mime-type key becomes >>> MimeType. >> >> Hmm, OK but why? The procedure produces the expected behaviour with >> #:mime-type, is there anything else to clarify? > > As a packager, I need to know what key is going to produce > StartupWMClass (note that :startup-wm-class produces, StartupWmClass, if > that matters), or DBusActivatable. Unless I'm missing something, it is > not obvious from the docstring. I could be misunderstanding you. The keys are self-documented like all key arguments. From any REPL / text editor, you would typically "show the procedure arguments" to see what's available. In Emacs/Geiser, you can use Eldoc or completion to access the full list of key parameters. =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlzsJTsACgkQm9z0l6S7 zH+FRwgAl60xeQsP7jzHAur+EbI9ZXQNj0ZLuylK3FrqRGUfOX3/45gPhShwQ8IM tompGOUwliCh8KNjxanudEvJN9WkIrp6xYUt8M01fR31GEmEQA06WSUKxDSYBUxQ fwm8C5KuX1fpG2BY1gC+toIpuBHVjCP6PwxnpLq9gaNxHpsd7gXebdCoQ9Yqderx WXVk53UzVeQVgd80ahz1OhJUJHNnFZdT7QFiJUmhXNE3RSgom3Qf34wrQEmEY3e5 apG7+p0pnyP5kmx0f+Jk+VLvOnYC/pmHE7DFG3svJOokGpk9/mF9Ouo+GHlkdibo JSCDHrA5WeaeBu2EnEJUZxtpQcUV3g== =x619 -----END PGP SIGNATURE----- --=-=-=--