Your message dated Sun, 25 Feb 2007 12:07:01 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385301: Update
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: zsh-beta
Version: 4.3.2-dev-1+20060822-1
Severity: normal
I use job control in my .xsession, but after the latest update it stopped
working.
I have 'setopt monitor' near the top of my .xsession. I run various jobs in
the background,
including my wm which I later foreground.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (900, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-5-wasp-1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages zsh-beta depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libcap1 1:1.10-14 support for getting/setting POSIX.
ii libncurses5 5.5-2 Shared libraries for terminal hand
ii libpcre3 6.4-2 Perl 5 Compatible Regular Expressi
ii passwd 1:4.0.18.1-2 change and administer password and
zsh-beta recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> It seems that the latest zsh-beta (4.3.2-dev-1+20070218-1) is explicit
> about job control not working when it's used in a script. In other
> words, if you try to 'setopt monitor' in a script you get a 'can't
> change option: monitor' kind of message.
Due to http://www.zsh.org/mla/workers/2006/msg00543.html
> I'm guessing based on this that this bug should be wont-fix, or at least
> that job control not being available in scripts is an upstream decision
> rather than a bug. I'd be interested in knowing why, but not enough to
> try to track it down, I'm afraid. ;)
> I've long since come up with a work-around (an ugly one, but workable)
> for the case where I wanted it, and as far as I'm concerned this bug can
> be closed.
When I have need for job control in a script, I use #!/bin/zsh -i
Of course, these scripts are all interactive anyway.
--- End Message ---
