From: "Robert D. Crawford" <rdc1x@comcast.net>
Subject: Re: yet another rookie question M-x shell
Date: Wed, 08 Mar 2006 09:16:46 -0600 [thread overview]
Message-ID: <87r75dge5d.fsf@laptop.rdc1.home> (raw)
In-Reply-To: 1141822182.505756.279110@i40g2000cwc.googlegroups.com
"billy" <bp1497@att.com> writes:
> I have no problem getting a shell to work. How do I get more than one
> shell available? M-x returns me to the same shell each time.
M-x rename-buffer
name the old shell something else... a good idea would be to name it
something related to what you feel you need it for i.e. "rootshell" or
"compilation shell" or "this is a shell that I want because I want to
litter my buffer list with lots o' stuff".
Then, after you rename the original shell, you type this command:
M-x shell
and you will have another shell.
Remember, emacs helps those who help themselves. You might find these
commands useful:
C-h i - this will bring you to the top level of your info docs. Then,
if you browse or hit C-s you can search for appropriate items.
M-x man - while not emacs specific, and not ideal for looking for emacs
documentation, I feel that emacs might not be the only thing that you
might need documentation on.
M-x apropos
C-h f <function-name>
C-h v <variable-name>
These are more advanced topics and you should look them up. While not
necessarily useful at this juncture in your education, they will be
helpful later.
The documentation for emacs is quite good. Become familiar with it.
rdc
--
**************************************************************************
Robert D. Crawford rdc1x@comcast.net
Avoid reality at all costs.
**************************************************************************
next prev parent reply other threads:[~2006-03-08 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 12:49 yet another rookie question M-x shell billy
2006-03-08 15:15 ` Peter Tury
2006-03-08 15:16 ` Robert D. Crawford [this message]
2006-03-08 19:51 ` Johan Bockgård
2006-03-10 17:56 ` Kevin Rodgers
2006-03-11 1:39 ` mlathe
2006-03-13 16:19 ` Kevin Rodgers
2006-03-13 20:50 ` mlathe
2006-03-13 23:37 ` Kevin Rodgers
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=87r75dge5d.fsf@laptop.rdc1.home \
--to=rdc1x@comcast.net \
/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).