From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thorsten Newsgroups: gmane.emacs.help Subject: Re: tmux & emacs: window issue Date: Mon, 20 Feb 2012 17:23:00 +0100 Message-ID: <87d399qxsr.fsf@googlemail.com> References: <87sji5rjnf.fsf@googlemail.com> <87bootwlmj.fsf@mean.albasani.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1329754944 6292 80.91.229.3 (20 Feb 2012 16:22:24 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 20 Feb 2012 16:22:24 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Feb 20 17:22:19 2012 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RzW0J-0007kA-LU for geh-help-gnu-emacs@m.gmane.org; Mon, 20 Feb 2012 17:22:19 +0100 Original-Received: from localhost ([::1]:39893 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RzW0J-0007dv-4p for geh-help-gnu-emacs@m.gmane.org; Mon, 20 Feb 2012 11:22:19 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:49212) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RzW0B-0007d6-HX for help-gnu-emacs@gnu.org; Mon, 20 Feb 2012 11:22:15 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RzW07-0003CQ-Js for help-gnu-emacs@gnu.org; Mon, 20 Feb 2012 11:22:11 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:40873) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RzW07-0003C2-EH for help-gnu-emacs@gnu.org; Mon, 20 Feb 2012 11:22:07 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1RzW00-0007Zo-R4 for help-gnu-emacs@gnu.org; Mon, 20 Feb 2012 17:22:00 +0100 Original-Received: from e178190157.adsl.alicedsl.de ([85.178.190.157]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Feb 2012 17:22:00 +0100 Original-Received: from quintfall by e178190157.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Feb 2012 17:22:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 34 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: e178190157.adsl.alicedsl.de User-Agent: Gnus/5.130002 (Ma Gnus v0.2) Emacs/24.0.93 (gnu/linux) Cancel-Lock: sha1:EDg99bnwj46OCPV7GmWNHHRu0ys= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:83813 Archived-At: Memnon Anon writes: Hi Memnon, > > Thorsten writes: > >> However, using gnus and an emacs frame splittet into 3 windows, a new >> problem appeared. Before, when visiting a link in an article, w3m just >> opened inside the article window - perfect. Now, w3m overrides the >> windowsplitting in the gnus frame and takes over the whole screen, so I >> avoid following links in the gnus article window. >> >> Did anybody experience similar problems using screen or tmux? > > This doesn't seem to be related to tmux at all, i.e., don't you get the > same behaviour when you run an emacsclient without tmux? No, when I used only emacs and something like winring.el, the gnus frame with the 3 windows was preserved and w3m just opened in the article window where I clicked on the link. > What I usually do when I read mail and news in gnus and w3m takes over > the windows configuration: I do a C-c u, which is bound for me to > winner-undo, keep on reading mail and news and read all links I followed > when I am done. Or, if that links is really important, I read it and > then return with winner-undo. I always thought winner mode was a bit strange with its 3 functions, but now I see it might make sense. Thank for the tip, I will try that out. cheers -- Thorsten