From: Maxime Devos <maximedevos@telenet.be>
To: Demis Balbach <db@minikn.xyz>, 53797@debbugs.gnu.org
Subject: [bug#53797] [PATCH] gnu: Add emacs-app-launcher.
Date: Sat, 05 Feb 2022 13:05:28 +0100 [thread overview]
Message-ID: <a0b6cdf10a282a84a781d230b0368296fba3b3b3.camel@telenet.be> (raw)
In-Reply-To: <20220205112019.31624-1-db@minikn.xyz>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
Demis Balbach schreef op za 05-02-2022 om 12:20 [+0100]:
> + "app-launcher defines the app-launcher-run-app command which uses Emacs
> +standard completion feature to select an application installed on your machine
> +and launch it.")
What does ‘launching’ mean here? Is ‘launching an application’
functionally the same as running it (with 'fork'+'exec' or 'system' or
whatever)? Does it have extra bells and whistles?
It's a super vague word, e.g. when Xiden has been announced on guix-
devel, one of the words that kept being repeated was 'launcher', but it
wasn't defined anywhere in its practically empty manual. (Nowadays
there's actually a manual and it does define launchers, but it didn't
use to.)
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-05 12:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 11:20 [bug#53797] [PATCH] gnu: Add emacs-app-launcher Demis Balbach
2022-02-05 12:05 ` Maxime Devos [this message]
2022-02-06 10:55 ` Demis Balbach
2022-02-05 12:12 ` Maxime Devos
2022-02-05 12:14 ` Maxime Devos
2022-02-05 12:13 ` Maxime Devos
2022-02-06 10:58 ` Demis Balbach
2022-02-06 11:39 ` Maxime Devos
2022-02-05 12:16 ` Maxime Devos
2022-02-06 10:59 ` Demis Balbach
2022-02-06 11:40 ` Maxime Devos
2022-02-05 12:20 ` Maxime Devos
2022-02-06 11:01 ` Demis Balbach
2022-02-06 11:44 ` Maxime Devos
2023-09-01 22:35 ` bug#53797: " Vagrant Cascadian
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=a0b6cdf10a282a84a781d230b0368296fba3b3b3.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53797@debbugs.gnu.org \
--cc=db@minikn.xyz \
/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.