From: Barry Margolin <barmar@genuity.net>
Subject: Re: How to see the value of each char in a string?
Date: Tue, 26 Nov 2002 18:44:43 GMT [thread overview]
Message-ID: <viPE9.21$fP2.761@paloalto-snr1.gtei.net> (raw)
In-Reply-To: arv4rj$qdk$1@panix2.panix.com
In article <arv4rj$qdk$1@panix2.panix.com>,
David Combs <dkcombs@panix.com> wrote:
>How to see the value of each char in a (long) string?
>
>Here's why I need to do that:
>
>In *shell*, (using csh), I yanked a command onto after the
>shell-promt, hit <return>, and got BEEP.
>
>I started hitting C-c's, couldn't kill the command I had
>given.
>
>Whenever I hit another <return>, I'd get echoed a ^G.
My guess is that the command included a pipe to "more", and that's more's
prompt. Full-screen programs like this don't work well in the *shell*
buffer. Try typing "q" to get out.
I don't understand what this problem has to do with your original question
about seeing the value of each character in a string.
--
Barry Margolin, barmar@genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
next prev parent reply other threads:[~2002-11-26 18:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 6:37 How to see the value of each char in a string? David Combs
2002-11-26 17:31 ` Kai Großjohann
2002-12-04 10:14 ` David Combs
2002-12-04 17:53 ` Kai Großjohann
2002-12-05 10:42 ` Kester Clegg
2002-11-26 18:44 ` Barry Margolin [this message]
2002-11-27 7:36 ` David Combs
2002-11-27 9:04 ` Oliver Scholz
2002-11-27 18:50 ` David Combs
2002-11-27 19:22 ` Barry Margolin
2002-11-29 22:24 ` David Combs
2002-11-30 7:28 ` Barry Margolin
2002-11-30 17:22 ` Kai Großjohann
2002-12-02 10:12 ` Barry Margolin
2002-12-02 17:53 ` Kai Großjohann
2002-11-28 10:07 ` Oliver Scholz
2002-11-29 23:57 ` 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='viPE9.21$fP2.761@paloalto-snr1.gtei.net' \
--to=barmar@genuity.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).