zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Juhapekka Tolvanen <juhtolv@st.jyu.fi>, zsh-workers@sunsite.dk
Subject: Re: bug in preexec()
Date: Fri, 20 Jul 2001 17:56:33 +0000	[thread overview]
Message-ID: <1010720175634.ZM7406@candle.brasslantern.com> (raw)
In-Reply-To: <20010720192942.A15962@silmu.st.jyu.fi>

On Jul 20,  7:29pm, Juhapekka Tolvanen wrote:
} Subject: bug in preexec()
} 
} If I give some command, for example this:
} 
} ls ; sleep 200
} 
} My titlebar shows that command three times and last two are kind
} of distorted

The format of arguments to preexec changed between 3.1.9 and 4.0.1.
Previously it received only a single argument as $1, so $1 and $* were
interchangable.  Now it receives three arguments; to get the previous
behavior, you need to be sure you're referring only to $1.

The doc says:

     [...]  If the history mechanism is active (and the line was not
     discarded from the history buffer), the string that the user typed
     is passed as the first argument, otherwise it is an empty string.
     The actual command that will be executed (including expanded
     aliases) is passed in two different forms: the second argument is
     a single-line, size-limited version of the command (with things
     like function bodies elided); the third argument contains the full
     text that is being executed.

That second argument is (intentionally) the same thing you'd see from
the "jobs" command if the command were backgrounded.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      reply	other threads:[~2001-07-20 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-20 16:29 Juhapekka Tolvanen
2001-07-20 17:56 ` Bart Schaefer [this message]

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=1010720175634.ZM7406@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=juhtolv@st.jyu.fi \
    --cc=zsh-workers@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).