From: dkcombs@panix.com (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) [thread overview]
Message-ID: <c90lqu$7in$1@reader2.panix.com> (raw)
In-Reply-To: barmar-C8F79B.10045025042004@comcast.ash.giganews.com
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
\a\a\a\a\aqq
\a\a\aq
\a\aq
\a\aQ
\a\aq
\a\aq
\a\a
\aq
\a\a
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
next prev parent reply other threads:[~2004-05-25 23:45 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 [this message]
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
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='c90lqu$7in$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).