octave-patch-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-patch-tracker] [patch #9464] texinfo errors/warnings will set st


From: Colin Macdonald
Subject: [Octave-patch-tracker] [patch #9464] texinfo errors/warnings will set status flag
Date: Thu, 7 Mar 2019 13:33:57 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

Follow-up Comment #3, patch #9464 (project octave):

Thanks, I've revised.

1. I passed 'once' to regexprep in the unlikely event the temp file name
contains "--output=".

2. I revised the message a bit to clarify this is only about errors.  Without
'--no-warn' we get a lot of warnings like "/tmp/octave-help-2ri7iS:117:
warning: entry for index `fn' outside of any node".  Outside the scope of this
fix...  Anyway, AFAICT warnings don't set non-zero return value.

3. What should we do about BIST?  If we put a deliberately broken texinfo
string in, the test suite is going to output messages like
"/tmp/octave-help-JpLtLe:118: unknown command `defunxx'".

4. If we did want to silence that output, IIRC evalc won't capture stderr
output of system.  Not for the first time, I'm reminded it would be useful to
have something like "system" that returns the stderr and stdout as separate
strings...

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?9464>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]