Comments on: Running Shells in Emacs: An Overview

By: Nurullah Akkaya

Nurullah Akkaya — Thu, 18 Oct 2012 16:19:10 +0000

You can fix the “‘eterm-color’: unknown terminal type.” error, by copying “eterm-color” and “eterm-color.ti” from “/usr/share/emacs/23.2/etc/e” into “~/.terminfo/e/” on the remote machine.

By: Compiling and running scripts in Emacs | Mastering Emacs

Compiling and running scripts in Emacs | Mastering Emacs — Tue, 29 May 2012 15:27:52 +0000

[...] talked about running shells and executing shell commands in Emacs before, but that’s mostly used for ad hoc commands or [...]

By: Executing Shell Commands in Emacs | Mastering Emacs

Executing Shell Commands in Emacs | Mastering Emacs — Wed, 19 Oct 2011 22:02:56 +0000

[...] sessions using comint, the Emacs command interpreter library. In earlier articles I covered shell integration and terminal emulation in Emacs, but this time I want to talk about the other use case: executing shell commands and capturing [...]

By: rgiar

rgiar — Wed, 09 Feb 2011 02:28:35 +0000

try –inf-ruby-mode which is custom-made for emacs

By: Jeff Maner

Jeff Maner — Wed, 12 Jan 2011 20:12:48 +0000

LOL! Didn’t know it was deprecated 15 years ago, but that’s what I’m talking about. Your response makes good sense. I’ve relied on doskey for years to make cmd.exe understand ls and other commands I prefer to Windows’ native commands. I’m having trouble getting them all working as EShell aliases, so I thought I’d check into using shell instead. Guess it’s back to EShell. Thanks for this post and your great Guide to Mastering EShell!

By: mickey

mickey — Wed, 12 Jan 2011 19:31:31 +0000

doskey? I thought they deprecated that thing 15 years ago. Assuming we’re talking about the ancient tool for MS-dos that added history and aliasing (as your post would imply) then I’d imagine it is because it hooks — or tries to — some low-level commands in the command console that a simple stdin/out redirection wouldn’t trigger.

By: Jeff Maner

Jeff Maner — Wed, 12 Jan 2011 18:52:49 +0000

Any idea why doskey won’t work in M-x shell? I can call doskey, I can assign doskey macros, but the macros aren’t recognized on invocation. For example, doskey ls=dir $* successfully defines ls as dir, but ls is subsequently not recognized.

By: chuck

chuck — Fri, 03 Dec 2010 17:03:44 +0000

Thanks for turning me on to M-x ansi-term!

I could use some suggestions, though… right now I usually have both emacs and Terminal open on my Mac, and the Terminal window usually has a couple tabs open, most of which have ssh sessions to different servers. I occasionally will run emacs in one of those ssh sessions to do some quick editing; I’ve noticed that when I do, (1) my alt/option key doesn’t work as Meta, so I have to use Esc instead, and (2) I don’t get any colors, just all green. Often though, I have much more involved editing to do on files on those servers, so I’ll open them in my local emacs using TRAMP. But then I’m usually going back to my Terminal do issue shell commands on the server. It seems like ansi-term could help a lot here, but the first thing I’d be doing in the ansi-term buffer would be sshing to a server; once I do, I’m finding that some things don’t work, for example if I try to run ‘top’ I get the error “‘eterm-color’: unknown terminal type.”

I’m not even completely sure which would be better to fix — get emacs on the servers set up nicer, or get it working better to run ssh sessions to the servers within M-x ansi-term on my local machine’s emacs.

By: escherdragon

escherdragon — Thu, 18 Nov 2010 17:08:28 +0000

The Sunrise Commander (a dual-pane file manager for GNU Emacs based on Dired) provides convenient integration with term-mode and eshell and makes quite easy to work with multiple terminals in Emacs.

http://www.emacswiki.org/emacs/Sunrise_Commander

Cheers,
–
José A. Romero L.
escherdragon at gmail
“We who cut mere stones must always be envisioning cathedrals.”
(Quarry worker’s creed)

By: jaybee

jaybee — Mon, 15 Nov 2010 14:41:23 +0000

Have a look at http://www.enigmacurry.com/2008/12/26/emacs-ansi-term-tricks/ which has a neat way of setting things up so the same command either starts a new shell, makes an existing shell buffer active, or renames a shell buffer (prerequisite to starting a new one).