unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: andrea crotti <andrea.crotti.0@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: better shells flow and integration
Date: Sun, 01 Feb 2015 22:30:29 +0000	[thread overview]
Message-ID: <87zj8xqn7e.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <CAF_E5JbjhnOeKjYpBQyWx25cGMGX2GvdwpACmmE3PcCxgZ5mFQ@mail.gmail.com> (message from andrea crotti on Sun, 1 Feb 2015 19:35:03 +0000)

andrea crotti <andrea.crotti.0@gmail.com> writes:
...
> So for some things I tend to use tmux and terminator, which are cool but
> are not inside Emacs sadly.
>
> Trying to find some ways to improve the flow:
> 1. is there a way to avoid these unresponsive moments and/or limit the
>    number of lines in the shell (or other similar) buffer?
>
> 2. alternatively maybe can I integrate Emacs and tmux?
>    Actually as soon as I thought about this I found a few things:
>    http://bradylove.com/blog/2013/05/24/commanding-tmux-with-emacs/
>    And a couple of packages in ELPA, so I'll try that out.

You can run GNU Screen inside an Emacs term or ansi-term.  I expect you
can do the same with Tmux.  There's a bit about doing it with Screen
here http://www.emacswiki.org/emacs/GnuScreen , there are couple of
gotchas and things you have to setup in Screen's rc file.  This way, if
you have to reboot X and/or Emacs then you can reconnect to the Screen
session.

I think disconnecting from the virtual terminal that's churning out all
the output should fix the responsiveness of Emacs.  But, when your
actually viewing a lot of data I think Emacs will be slower using M-x
term and Screen than using M-x shell.

BR,
Robert Thorpe



      reply	other threads:[~2015-02-01 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 19:35 better shells flow and integration andrea crotti
2015-02-01 22:30 ` Robert Thorpe [this message]

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=87zj8xqn7e.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=andrea.crotti.0@gmail.com \
    --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.
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).