unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org, Federico Tedin <federicotedin@gmail.com>
Subject: Re: INSIDE_EMACS and Tramp
Date: Sat, 02 May 2020 13:20:02 -0400	[thread overview]
Message-ID: <jwvk11up8f6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87o8r6wfni.fsf@gmx.de> (Michael Albinus's message of "Sat, 02 May 2020 16:54:57 +0200")

> +(defvar inside-emacs-functions nil
[...]
> +(defun inside-emacs (&optional context)
> +  "Return the string to be set in environment variable INSIDE_EMACS.
> +CONTEXT could be a string which is added."
> +  (mapconcat
> +   #'identity
> +   (delq nil (append `(,emacs-version
> + 	               ,(and (stringp context) context))
> + 	             (mapcar #'funcall inside-emacs-functions)))
> +   ","))

Any chance we could live without `inside-emacs-functions` and instead do:

    (defun inside-emacs (&optional context)
      "Return the string to be set in environment variable INSIDE_EMACS.
    CONTEXT could be a string which is added."
      (let ((base (or (getenv "INSIDE_EMACS") emacs-version)))
        (if context (concat case "," context) base)))


-- Stefan




  parent reply	other threads:[~2020-05-02 17:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200402230535.10490.95720@vcs0.savannah.gnu.org>
     [not found] ` <20200402230536.E0A3F20CDD@vcs0.savannah.gnu.org>
2020-04-03  8:35   ` INSIDE_EMACS and Tramp (was: master f28166d: Copy INSIDE_EMACS env variable to subprocesses in Eshell (Bug#25496)) Michael Albinus
2020-04-04 14:53     ` Federico Tedin
2020-04-04 15:10       ` INSIDE_EMACS and Tramp Michael Albinus
2020-04-04 20:13         ` Federico Tedin
2020-04-13  9:07           ` Michael Albinus
2020-04-17 20:16             ` Federico Tedin
2020-05-02 14:54               ` Michael Albinus
2020-05-02 15:39                 ` Eli Zaretskii
2020-05-02 16:04                   ` Michael Albinus
2020-05-02 16:17                     ` Eli Zaretskii
2020-05-02 16:16                 ` Eli Zaretskii
2020-05-02 17:20                 ` Stefan Monnier [this message]
2020-05-03 12:33                   ` Michael Albinus
2020-05-03 14:51                     ` Stefan Monnier
2020-05-03 16:08                       ` Michael Albinus
2020-05-03 20:54                         ` Stefan Monnier
2020-05-04  7:08                           ` Michael Albinus
2020-05-04  8:47                             ` Michael Albinus
2020-05-04 15:38                               ` Stefan Monnier
2020-05-04 16:11                                 ` Michael Albinus
2020-05-03 14:52                 ` Federico Tedin
2020-05-03 16:19                   ` Michael Albinus

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=jwvk11up8f6.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=federicotedin@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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).