From: Stefan Kangas <stefan@marxist.se>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 3736@debbugs.gnu.org, Sven Joachim <svenjoac@gmx.de>,
Jason Rumney <jasonr@gnu.org>
Subject: bug#3736: 23.1.50; Please use null-device instead of /dev/null
Date: Wed, 18 Nov 2020 18:31:20 -0800 [thread overview]
Message-ID: <CADwFkmkOoOnedWb_aZco2UYo5KBtMmN+X4mY1howwLUSeX571A@mail.gmail.com> (raw)
In-Reply-To: <nq63ebjf2a.fsf@alcatel-lucent.de> (Michael Albinus's message of "Thu, 02 Jul 2009 17:10:53 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> Jason Rumney <jasonr@gnu.org> writes:
>
>> Probably the best solution is for tramp to implement a general
>> server-local-variable mechanism, as there are probably other variables
>> that need different values for different servers too. The user could
>> then configure a variable (such as tramp-server-local-variable-alist)
>> to define any such variables that they need to, which would then be
>> let bound as appropriate in tramp functions.
>
> Nice idea. Tramp does it already in some cases (for example for
> environment variables of the remote host), but your proposal is more
> general.
>
> Noted.
(That was 12 years ago.)
Now that we have this concept of "connection local variables", does that
satisfy the requirement to be able to specify null-device for remote
hosts?
next prev parent reply other threads:[~2020-11-19 2:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1659.1246480655.2239.bug-gnu-emacs@gnu.org>
2009-07-02 12:22 ` bug#3736: 23.1.50; Please use null-device instead of /dev/null Michael Albinus
2009-07-02 13:03 ` Jason Rumney
2009-07-02 13:57 ` Sven Joachim
2009-07-02 14:14 ` Jason Rumney
2009-07-02 15:10 ` Michael Albinus
2020-11-19 2:31 ` Stefan Kangas [this message]
2020-11-19 16:32 ` Michael Albinus
2020-11-21 15:16 ` Michael Albinus
2020-11-26 15:28 ` Michael Albinus
2020-11-26 16:47 ` Stefan Kangas
2009-07-02 14:21 ` Lennart Borgman
2009-07-02 15:06 ` Michael Albinus
2009-07-02 18:49 ` Eli Zaretskii
2009-07-01 20:22 Lennart Borgman
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=CADwFkmkOoOnedWb_aZco2UYo5KBtMmN+X4mY1howwLUSeX571A@mail.gmail.com \
--to=stefan@marxist.se \
--cc=3736@debbugs.gnu.org \
--cc=jasonr@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=svenjoac@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.