From: Alexandros Prekates <aprekates@posteo.net>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Help me understand the exec entry in emacsclient.desktop
Date: Sat, 2 Dec 2023 01:37:47 +0000 [thread overview]
Message-ID: <20231202033737.792a9e7a@enous-devuan> (raw)
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
That is the entry:
Exec=sh -c "if [ -n \\"\\$*\\" ]; then exec emacsclient
--alternate-editor= --display=\\"\\$DISPLAY\\" \\"\\$@\\"; else exec
emacsclient --alternate-editor= --create-frame; fi"
My interpretation so far is: If files where given as arguments then
start in a certain display and use the current opened frame .
If files were not given then create a new frame.
But it doesnt make much sense to me. Also why sh %F and not %F ?
And why in the latter case display is not being set ?
Alexandros.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next reply other threads:[~2023-12-02 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 1:37 Alexandros Prekates [this message]
2023-12-17 0:58 ` Help me understand the exec entry in emacsclient.desktop Mekeor Melire
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231202033737.792a9e7a@enous-devuan \
--to=aprekates@posteo.net \
--cc=help-gnu-emacs@gnu.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.
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).