From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Zefram" <zefram@fysh.org>,
"Bart Schaefer" <schaefer@candle.brasslantern.com>
Cc: <zsh-workers@sunsite.auc.dk>
Subject: Prompt escapes RE: $'...' and double-quotes
Date: Tue, 7 Mar 2000 11:35:32 +0300 [thread overview]
Message-ID: <000501bf8810$19a03fd0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <E12RwXA-0007Eb-00@crucigera.fysh.org>
$'...' reminds me - is there any easy way to get prompt escapes embedded?
Manual for $'...' states, it the same as for print builtin - but print may
be forced to interpret prompt escapes as well.
-andrej
Have a nice DOS!
B >>
next prev parent reply other threads:[~2000-03-07 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-06 5:13 Bart Schaefer
2000-03-06 12:22 ` Zefram
2000-03-07 8:35 ` Andrej Borsenkow [this message]
2000-03-07 16:38 ` Prompt escapes " Bart Schaefer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000501bf8810$19a03fd0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--cc=zefram@fysh.org \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).