unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Add helper for .desktop file creation?
Date: Mon, 27 May 2019 19:58:19 +0200	[thread overview]
Message-ID: <87y32rkcec.fsf@ambrevar.xyz> (raw)
In-Reply-To: <874l5f6bl7.fsf@nicolasgoaziou.fr>

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

Nicolas Goaziou <mail@nicolasgoaziou.fr> 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.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-05-27 17:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24  7:53 Add helper for .desktop file creation? Pierre Neidhardt
2019-05-25 12:06 ` Nicolas Goaziou
2019-05-25 12:21   ` Nicolas Goaziou
2019-05-25 12:51     ` Pierre Neidhardt
2019-05-25 13:33       ` Nicolas Goaziou
2019-05-25 13:45         ` Nicolas Goaziou
2019-05-25 14:20         ` Pierre Neidhardt
2019-05-25 18:37           ` Pierre Neidhardt
2019-05-27  7:13             ` Pierre Neidhardt
2019-05-27 16:15               ` Nicolas Goaziou
2019-05-27 16:45                 ` Pierre Neidhardt
2019-05-27 17:39                   ` Nicolas Goaziou
2019-05-27 17:58                     ` Pierre Neidhardt [this message]
2019-05-27 19:19                       ` Nicolas Goaziou
2019-05-30  8:24                         ` Pierre Neidhardt
2019-05-27 19:54               ` Marius Bakke
2019-05-27 21:02                 ` Pierre Neidhardt
2019-05-25 13:38       ` Amin Bandali
2019-05-25 14:30   ` Danny Milosavljevic

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=87y32rkcec.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).