unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: How to get DISPLAY of emacsclient?
Date: Sun, 27 Nov 2022 16:12:39 +0000	[thread overview]
Message-ID: <3d2972a5f51db6812298@heytings.org> (raw)
In-Reply-To: <tlvvjp$lca$1@ciao.gmane.io>

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


>>> Currently I prefer to concentrate on the case of accessing X selection 
>>> or getting DISPLAY without creation of visible frames.
>> 
>> Sorry, I don't understand what "getting DISPLAY without creation of 
>> visible frames" means.  Is the $DISPLAY environment variable not 
>> enough?
>
> I do not see a way to get the value of the DISPLAY environment variable 
> specific to the emacsclient process.
>

But where do you need that value, and what do you mean by "without 
creation of visible frames"?  Not all emacsclient processes have a 
corresponding display, e.g. if you just do

emacsclient --eval '(+ 1 1)'

there is no display involved.  If you create an emacsclient process with 
-c or -r, then in Elisp you can get the display on which the frame is 
displayed with (getenv "DISPLAY"), or (cdr (assq 'display 
(frame-parameters))).

  reply	other threads:[~2022-11-27 16:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 15:17 How to get DISPLAY of emacsclient? Max Nikulin
2022-11-25 16:57 ` Stefan Monnier
2022-11-26  3:36   ` Max Nikulin
2022-11-26 21:33     ` chad
2022-11-27 11:34       ` Max Nikulin
2022-11-27 13:42         ` Gregory Heytings
2022-11-27 14:23           ` Max Nikulin
2022-11-27 14:38             ` Gregory Heytings
2022-11-27 15:26               ` Max Nikulin
2022-11-27 16:12                 ` Gregory Heytings [this message]
2022-11-28  1:19             ` Po Lu
2022-11-27 20:36     ` Jim Porter
2022-11-28 15:33       ` Max Nikulin
2022-11-28 17:15         ` Gregory Heytings
2022-11-28 18:19         ` Stefan Monnier
2022-11-29 16:23           ` Max Nikulin
2022-11-30  0:41             ` chad
2022-11-30  2:44               ` Stefan Monnier
2022-11-30 12:47                 ` Max Nikulin

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=3d2972a5f51db6812298@heytings.org \
    --to=gregory@heytings.org \
    --cc=emacs-devel@gnu.org \
    --cc=manikulin@gmail.com \
    /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/emacs.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).