all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Angel de Vicente <angelv@iac.es>
To: help-gnu-emacs@gnu.org
Subject: Re: tmux & emacs: window issue
Date: Tue, 21 Feb 2012 00:18:57 +0000	[thread overview]
Message-ID: <yegwr7hox72.fsf@carro.ll.iac.es> (raw)
In-Reply-To: 87sji5rjnf.fsf@googlemail.com

Hi,

Thorsten <quintfall@googlemail.com> writes:

> Hi List, 
> I don't really know if this question should go to an Emacs or an tmux
> (== modern gnu screen) newsgroup, so I try it here: 
>
> I just discovered, that having one emacs daemon running, I can open as
> many emacsclients as I want and can do (being on plain terminal) all the
> window management with my terminal multiplexer (tmux). This works fine
> and appears more stable than something like winring.el, that caused more
> emacs crashes for me than anything else. 
>
> 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?

I run screen, launch an emacs -daemon at some point, and then I open
multiple emacsclient -t instances inside screen. One of these instances
is just for Gnus, and I don't have the problem you describe. When
entering a group I have two windows, the summary buffer and the article
buffer. Following a link in the article buffer just causes that window
to be replaced with the w3m stuff.

Cheers,
-- 
Ángel de Vicente
http://angel-de-vicente.blogspot.com/




  parent reply	other threads:[~2012-02-21  0:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20  8:31 tmux & emacs: window issue Thorsten
2012-02-20 15:53 ` Memnon Anon
2012-02-20 16:23   ` Thorsten
2012-02-21  0:18 ` Angel de Vicente [this message]
2012-02-21  7:44   ` Thorsten
2012-02-21 11:58     ` Angel de Vicente
2012-02-21 12:15       ` Thorsten

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=yegwr7hox72.fsf@carro.ll.iac.es \
    --to=angelv@iac.es \
    --cc=help-gnu-emacs@gnu.org \
    /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.