emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#3957: closed (split window for remote commands thr


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#3957: closed (split window for remote commands through eshell)
Date: Tue, 28 Jan 2014 10:23:02 +0000

Your message dated Tue, 28 Jan 2014 11:22:23 +0100
with message-id <address@hidden>
and subject line Re: bug#3957: split window for remote commands through eshell
has caused the debbugs.gnu.org bug report #3957,
regarding split window for remote commands through eshell
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
3957: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3957
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: split window for remote commands through eshell Date: Tue, 28 Jul 2009 15:03:46 -0400
Basically, any time a remote command gets executed through eshell, if
the frame is a single window it gets split into two windows.
Essentially, this is because tramp does its magic through
shell-command, which pops up a window if the output is too large to
fit in the minibuffer.

My first reaction was to wrap the relevant call to shell-command in a
save-window-excursion, but there seem to be some problems with that.
I'm currently trying to figure out how to prevent the root split, so
things like new frames are blocked as well.

It was suggested that I send the bug to this list so that a task would
be created that could be tracked.

Colin



--- End Message ---
--- Begin Message --- Subject: Re: bug#3957: split window for remote commands through eshell Date: Tue, 28 Jan 2014 11:22:23 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
Michael Albinus <address@hidden> writes:

> Since Emacs 24.3, eshell-remote-command is not used
> anymore. eshell-external-command calls start-file-process. This should
> have fixed the issue, could you, please, check?

No response, so I'm closing this bug. Feel free to reopen if it doesn't
work as expected.

Best regards, Michael.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]