From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 18940@debbugs.gnu.org, dpittman@fb.com
Subject: bug#18940: 24.4; vc-hg does not disable pager, leading to hangs (at least with tramp)
Date: Sun, 16 Nov 2014 17:29:51 +0200 [thread overview]
Message-ID: <83a93rduz4.fsf@gnu.org> (raw)
In-Reply-To: <87mw7rtnxg.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Sun, 16 Nov 2014 11:55:23 +0100
> Cc: 18940@debbugs.gnu.org, dpittman@fb.com
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > It seems related, indeed, but in the case at hand, this
> > process-environment value should be specific to the process started with
> > process-file, not specific to a particular server.
>
> We need a mechanism which shall allow kind of let-bind the process
> environment variables when starting a new (remote) process. But there
> shall be also server-specific defaults to be used.
>
> I haven't started yet a design, how this could look like. Proposals welcome!
Maybe I'm missing something, but what's wrong with let-binding
process-environment?
next prev parent reply other threads:[~2014-11-16 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 21:47 bug#18940: 24.4; vc-hg does not disable pager, leading to hangs (at least with tramp) Daniel Pittman
[not found] ` <handler.18940.B.141505143415260.ack@debbugs.gnu.org>
2014-11-03 22:13 ` bug#18940: Acknowledgement (24.4; vc-hg does not disable pager, leading to hangs (at least with tramp) ) Daniel Pittman
2014-11-09 10:24 ` bug#18940: 24.4; vc-hg does not disable pager, leading to hangs (at least with tramp) Michael Albinus
2014-11-13 15:36 ` Michael Albinus
2014-11-13 18:10 ` Stefan Monnier
2014-11-13 21:37 ` Michael Albinus
2014-11-14 1:49 ` Stefan Monnier
2014-11-16 10:55 ` Michael Albinus
2014-11-16 15:29 ` Eli Zaretskii [this message]
2014-11-16 18:38 ` Michael Albinus
2014-11-16 21:08 ` Stefan Monnier
2014-11-15 2:24 ` bug#18940: Enabling hg extensions Jordi Gutiérrez Hermoso
2014-11-15 16:00 ` 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=83a93rduz4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18940@debbugs.gnu.org \
--cc=dpittman@fb.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).