On Thu, Jun 06, 2013 at 12:10:26PM +0200, Thorsten Glaser wrote: > tglase@tglase:~ $ select-editor > > Select an editor. To change later, run 'select-editor'. > 1. /bin/ed > 2. /usr/bin/jupp > 3. /usr/bin/mcedit > > /usr/bin/select-editor[47]: read: -p: no coprocess > > > The last line repeats infinitely (until ^C is pressed). > The -p option to read is used for coprocess I/O in all > Korn shells, and your script is apparently written for > a different n??n-POSIX shell, yet uses #!/bin/sh shebang > thus violating Policy §10.4 (RC bug). > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'stable'), (100, 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) > Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/lksh > > -- no debconf information
Hello Thorsten, I don't see the problem above when I run select-editor (as you have done) or the command below. /bin/dash -x /usr/bin/select-editor On my system /bin/sh points to dash and `man dash` shows that -p is a valid read parameter. Is it a bashism when dash read supports it? On your system /bin/sh points to lksh. What could be used in lksh instead of read -p? Thank you, Aníbal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
