help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: is easy to get hung in infinite ^G stream; how to stop it?


From: David Combs
Subject: Re: is easy to get hung in infinite ^G stream; how to stop it?
Date: Tue, 25 May 2004 23:45:34 +0000 (UTC)

In article <barmar-C8F79B.10045025042004@comcast.ash.giganews.com>,
Barry Margolin  <barmar@alum.mit.edu> wrote:
>In article <c6flqh$3kb$1@panix3.panix.com>,
> dkcombs@panix.com (David Combs) wrote:
>
>> Want to see something funny?
>> 
>> (Ok, not so funny, then.)
>> 
>> Within *shell*, do "man <something>".
>> 
>> Yes, exactly that way.  No, *not* via M-x man.
>> 
>> At least if you're me (running 21.2.1), emacs gets
>> all screwed up trying to display a man-page into *shell*,
>> you get this ^G.
>> 
>> Hit <return>, you get one line of the man-page,
>> and another ^G.
>
>Type "q" followed by RETURN.
>
>-- 
>Barry Margolin, barmar@alum.mit.edu
>Arlington, MA
>*** PLEASE post questions in newsgroups, not directly to me ***

I've tried it -- it seems to do nothing:



224 ==/dkcjunk==> dirs
/dkcjunk /opt6/myexternals/home/dkc/4msnew 
/big5/david3/from_netcom-dir2/sources-stuff/lynx2-8-5/src 
225 ==/dkcjunk==> pushd /home/dkc; cd .
/home/dkc /dkcjunk /opt6/myexternals/home/dkc/4msnew 
/big5/david3/from_netcom-dir2/sources-stuff/lynx2-8-5/src 
226 ==/home/dkc==> egrepin -c tck *.mss | egrep -v '\.mss:0$'
sundgrep.mss:1
sundgrep_orig.mss:1
227 ==/home/dkc==> popd; cd .
/dkcjunk /opt6/myexternals/home/dkc/4msnew 
/big5/david3/from_netcom-dir2/sources-stuff/lynx2-8-5/src 
228 ==/dkcjunk==> alias xalias 'printf "At startup, su(ck)-in one .smd 
"subcommand"-file:\n  (NOTE: below, "su" is ok-abbrev for suck-in ("source") 
cmd "subcommands t.smd",\n      meaning "read in the sub-commands located in 
subcommands-file t.smd")\n  At startup, "su" EITHER:  cuffs.smd   OR    
tools.smd\n    (should be local indir-symlinks *thru* 
/home/dkc/4msnew/{cuffs,tools}.smd)"'

228 ==/dkcjunk==> xalias
qq
q
q
Q
q
q

q


See just above, my "g<return>", several of them.

Does nothing, I think.

  -----

Any other suggestions on recovering a seemingly-"destroyed"
*shell*-buffer that's gotten (apparantely irretrievably) sucked 
into the ^G^G^G,,, snakepit.

thanks,

David




reply via email to

[Prev in Thread] Current Thread [Next in Thread]