Bug#783195: Exits 0 even if the handler cannot be executed

2015-11-01 Thread Elliott Mitchell
I'd tend towards pointing at `man perlfunc`, which is the same information, but available locally. > I do not understand why the original command's error code (127 in our case) The command does not given an error in this case, the system call does. The result is Perl's system() function returns -

Bug#783195: Exits 0 even if the handler cannot be executed

2015-04-24 Thread martin f krafft
also sprach Charles Plessy [2015-04-24 02:11 +0200]: > } else { > $res = system $comm; > $res = int($res/256); > } > I do not understand why the original command's error code (127 in our case) Actually, -128, which is 127 unsigned. ;) http://perldoc.perl.

Bug#783195: Exits 0 even if the handler cannot be executed

2015-04-23 Thread Charles Plessy
Le Thu, Apr 23, 2015 at 08:00:08PM +0200, martin f krafft a écrit : > > % pdfmod > zsh: command not found: pdfmod > > % run-mailcap --debug --action=edit /tmp/3290_001.pdf (...) > - running test: test -n "$DISPLAY" (result=0=true) > - executing: pdfmod /tmp/3290_001.pdf > > % echo $? > 0 Tha

Bug#783195: Exits 0 even if the handler cannot be executed

2015-04-23 Thread martin f krafft
Package: mime-support Version: 3.58 Severity: normal File: /usr/bin/run-mailcap If the edit= parameter for a MIME type specifies a nonexistent command, run-mailcap just exits 0, which in Unix terms means that everything was alright, except nothing actually happened: % pdfmod zsh: command not foun