Julien Cristau wrote:
> On Mon, Jul 21, 2008 at 09:00:04 +0000, Debian Bug Tracking System wrote:
>> * calling /usr/share/bug/texlive-doc-base 3>&1 aborts with an error  
>> (getkey: command not found) when called in the console.
>>
> That's one of the documented functions such a script can rely on.

Where is that documented? And where does getkey come from? Haven't found
a package providing this command.

>> as you can see rng already gathered the info and even put in in a file,  
>> all the user has to do is to attach this file to the mail.
>>
> That doesn't make any sense.  If you gather the info, then surely
> putting it in the mail is not much more work.  I'm pretty sure you can
> attach files to a mail, if nothing else.

Not every MUA supports an "attach file" option. It's not that I haven't
already tried it (#491499). So since attaching the file automatically is
not possible right now, asking the user kindly to attach the file is the
second best rng can do. And please keep in mind that this only happens
when the output of a script is *very* large -- to large for the shell to
handle -- like the one from xserver-xorg, for the most other packages,
everything should work fine automatically and attaching a file is not
needed.

>> The "file too long" problem isn't rng's fault but a limitation of the  
>> shell which can't execute commands of unlimited length. Rng detects such  
>> cases where calling the MUA failed and puts the output in a file and  
>> asks the user kindly to attach it.
>>
> Yes, it's rng's fault.  I'm not sure why you say the shell has anything
> to do with this.

How do you think rng invokes the different MUAs? If you have a better
solution which supports calling MUAs with bodies of arbitrary
textlengths, then please send me a patch. I'd love to have this included
rather to rely on the user to attach a file.

-- 
Bastian Venthur                                      http://venthur.de
Debian Developer                                 venthur at debian org




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to