unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: is easy to get hung in infinite ^G stream; how to stop it?
Date: Thu, 27 May 2004 02:56:39 -0400	[thread overview]
Message-ID: <barmar-2BB819.02563927052004@comcast.dca.giganews.com> (raw)
In-Reply-To: c93vha$eav$1@reader2.panix.com

In article <c93vha$eav$1@reader2.panix.com>,
 dkcombs@panix.com (David Combs) wrote:

> PS: One puzzle: what's this stuff about how wonderful
> "ed" is?  (Yes, is better than ex for *scripts*, for sure) --
> how does it relate to this post?  Except to suggest
> that when in *shell* I should use ed rather than vi --
> again, vi is only an easy way to get the ^G problem
> (and I very often do use ex from *shell*).

In general, when you're in a *shell* buffer, you can't use any 
full-screen applications.  The shell buffer is not emulating a video 
terminal, it's more like a dumb hardcopy terminal.

One thing that will help alot is to set $PAGER to "cat" when you're in a 
shell buffer.  Put the following in your .cshrc:

if ( $?EMACS ) setenv PAGER cat

This should avoid most unintentional use of "more" or "less".

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

  reply	other threads:[~2004-05-27  6:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-25  6:28 is easy to get hung in infinite ^G stream; how to stop it? David Combs
2004-04-25  6:57 ` David Combs
2004-04-25 14:04 ` Barry Margolin
2004-05-25 23:45   ` David Combs
2004-05-26  4:31     ` Barry Margolin
2004-05-26 22:00       ` David Combs
2004-05-26 22:15         ` Stefan Monnier
2004-05-27  5:49           ` David Combs
2004-05-27  6:56             ` Barry Margolin [this message]
2004-05-27 19:34             ` Stefan Monnier
2004-05-28  8:22             ` Kai Grossjohann
2004-04-25 17:06 ` Kai Grossjohann
2004-05-25  6:31   ` David Combs

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=barmar-2BB819.02563927052004@comcast.dca.giganews.com \
    --to=barmar@alum.mit.edu \
    /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).