zsh-users
 help / color / mirror / code / Atom feed
From: "Joshua Symons" <vmcore@mysun.com>
To: mason@primenet.com.au
Cc: zsh-users@sunsite.dk
Subject: Re: Preexec & Printf
Date: Thu, 25 Apr 2002 20:31:56 -0500	[thread overview]
Message-ID: <20832251d4.251d420832@mysun.com> (raw)

----- Original Message -----
From: Geoff Wing <mason@primenet.com.au>
Date: Thursday, April 25, 2002 8:22 pm
Subject: Re: Preexec & Printf

> Joshua Symons <vmcore@mysun.com> typed:
> : I have a pretty generic problem, but I can't seem to make my way 
> around: it. Here is an example of what is happening:
> 
> : [(ichirou:151:pts/15)~ %] which preexec
> : preexec () {
> :         print -Pn "\e]0;%m:%l   -   $* \a"
> :}
> : [(ichirou:152:pts/15)~ %] printf '^[[32;40mwith quotes\n'
> 
> : For echo, print, and printf, my '' is getting passed (straight 
> quote): into preexec and erroring back out into my shell. I can't 
> seem to get
> : around the quotes that are passed into preexec. This doesn't 
> happen in
> : dtterm for some reason, not sure why. 
> : Any help that could be given would be nice.
> 
> Your problem is different to what you think.  You're using xterm and
> you're expecting it to not print the set of characters sent through 
> thepreexec without consideration of what characters are permissible.
> Obviously you'll have problems if you try to send a BEL (\a) via the

I was actually using the example provided in the xterm title setting
how-to.
Is there a better way to terminate the title?

> normal line because it'll terminate the title-set OSC in the print 
> in the

OSC ?

> preexec().  You'll also have problems with xterm with other non-
> printablecharacters, e.g. ESC, CR, LF - xterm will also use those 
> as terminators
> since they're non-valid.  You'll need to do some more character
> sanitisation first on the string sent via the preexec() print.
> 
> Regards,
> -- 
> Geoff Wing : <gcw@pobox.com>
> Rxvt Stuff : <gcw@rxvt.org>
> Zsh Stuff  : <gcw@zsh.org>
> 


             reply	other threads:[~2002-04-26  1:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26  1:31 Joshua Symons [this message]
2002-04-26  1:47 ` Geoff Wing
  -- strict thread matches above, loose matches on Subject: below --
2002-04-26  2:10 Joshua Symons
2002-04-26  1:54 Joshua Symons
2002-04-26  2:06 ` Bart Schaefer
2002-04-26  1:25 Joshua Symons
2002-04-26  1:45 ` Bart Schaefer
2002-04-26  9:21   ` Oliver Kiddle
2002-04-26  1:07 Joshua Symons
2002-04-26  1:16 ` Bart Schaefer
2002-04-26  1:19   ` Bart Schaefer
2002-04-26  0:47 Joshua Symons
2002-04-26  1:01 ` Bart Schaefer
2002-04-26  1:22 ` Geoff Wing

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=20832251d4.251d420832@mysun.com \
    --to=vmcore@mysun.com \
    --cc=mason@primenet.com.au \
    --cc=zsh-users@sunsite.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).