https://bugs.kde.org/show_bug.cgi?id=406776
--- Comment #21 from avlas <jsar...@gmail.com> --- (In reply to Nikita Sirgienko from comment #20) > (In reply to avlas from comment #17) > > (In reply to Nikita Sirgienko from comment #16) > > > Hi avlas, Octave writes error messages and warnings into stderr. In Cantor > > > we don't distinguish between warnings and errors. And, if a expression > > > finished with error, Cantor show only error and don't show output of > > > failed > > > command. > > > > That sounds good. But the output should still appear for warnings in > > addition to the warning message, right? > > No, I mean, in this moment, Cantor don't show output for warnings (yes, it's > not very compfort for user). See https://bugs.kde.org/show_bug.cgi?id=406777 > for my advanced explanetion. > > > For whatever reason this doesn't seem to be the case in my system. > > > > Did you have a chance to try the f_test I mentioned? > Yes, you can see a result of this in attachments. Thank you for testing and for the explanation. Unfortunately it is not very obvious to reproduce :/ One last way I can imagine to try to reproduce my issue is the following: - Move the functions of the backend to a different location in the filesystem and add the new location to octave's path (in .octaverc). This is basically what I need to do given that Octave's flatpak cannot reach system's location: "warning: addpath: /usr/share/cantor/octavebackend/: The file or directory does not exist" I even tried moving it to the home share folder $HOME/.local/share/cantor/octavebackend/ but this didn't work either. Perhaps one thing that might help would be checking if backend functions are in octave's path, instead of just looking for them in the expected filesystem location. -- You are receiving this mail because: You are watching all bug changes.
