unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: dkcombs@panix.com (David Combs)
Subject: Re: "more", "ls -l", and column 80 in shell
Date: Sun, 25 Jun 2006 00:24:36 +0000 (UTC)	[thread overview]
Message-ID: <e7kl44$t8p$1@reader2.panix.com> (raw)
In-Reply-To: 87slm4p8sx.fsf@tiger.rapttech.com.au

In article <87slm4p8sx.fsf@tiger.rapttech.com.au>,
Tim X  <timx@nospam.dev.null> wrote:
>...

>Some basic rules of thumb and advice which I hope will help
>
>1. Don't try to use emacs as if it was equivalent to one of the
>   standard shells like bash, tcsh or (gasp) csh. While emacs provides

M-x shell
   (then, in *shell*):
tcsh

Works *absolutely* fine -- ie the same as in a dtterm (no emacs).

(of course, no "more", etc, but grep, find, etc all work
      exactly as expected.  Likewise pushd, popd, dirs, etc.
    (Although from time to time it gets confused, at which
      point you simply do  M-x dirs )

>   various ways of doing interaction at this level, you are much
>   better off using equivalent emacs features when possible i.e.
>   dired, 
      of course (plus with dired-x, too).

M-x locate, M-x grep, M-x cd etc. 
Huh?

About M-x grep, I find it very useful to use normal
   grep/egrep/etc, *with -n*, and on *at least 2 files*
    (eg if just one to be grepped, then append /dev/null to
      get to the 2-or-more-files -- so as to get file-names
      at the left of the grep-output)
   and then, if desired, hack that file to remove lines,
     add marks to certain lines, etc,
   and THEN do M-x grep, and change the offered args to
    "`cat mygrep.out`"


>
>2. When using one of emacs' shell interfaces, keep in mind that it is
>   often necessary to have some escape key sequence to either access
>   shell commands that conflict with normal emacs interpreted commands

I don't understand, so: Please expain, ie show examples where necessary.


>   or you need to use an escape sequence within the shell buffer to
                           HUH?  Explain?

>   access emacs commands. Also, note that some shell interfaces, like
>   M-x term have different operating modes - a line mode and a
>   terminal mode.
>

Thanks!

David

  reply	other threads:[~2006-06-25  0:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15 22:44 "more", "ls -l", and column 80 in shell RjjdBae
2006-06-15 23:46 ` Barry Margolin
2006-06-16  6:48   ` Tim X
2006-06-16 14:42 ` RjjdBae
2006-06-17  6:58   ` Tim X
2006-06-25  0:24     ` David Combs [this message]
2006-06-25  2:39       ` Tim X
2006-06-25  8:45         ` Peter Dyballa
2006-06-17  8:18   ` Peter Dyballa
     [not found]   ` <mailman.2970.1150533187.9609.help-gnu-emacs@gnu.org>
2006-06-25  0:30     ` David Combs
2006-06-25  8:35       ` Peter Dyballa
     [not found]       ` <mailman.3300.1151224578.9609.help-gnu-emacs@gnu.org>
2006-06-25  9:42         ` Tim X
2006-06-25 15:30           ` Peter Dyballa
     [not found]           ` <mailman.3306.1151249429.9609.help-gnu-emacs@gnu.org>
2006-06-25 21:44             ` Miles Bader
2006-06-25 22:58               ` Peter Dyballa
     [not found]               ` <mailman.3321.1151276298.9609.help-gnu-emacs@gnu.org>
2006-06-26  0:37                 ` Miles Bader
2006-06-26  8:33                   ` Peter Dyballa

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='e7kl44$t8p$1@reader2.panix.com' \
    --to=dkcombs@panix.com \
    /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).