[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #65607] cluttering text output when using path
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #65607] cluttering text output when using path() with echo on |
Date: |
Thu, 18 Apr 2024 22:05:49 -0400 (EDT) |
Follow-up Comment #1, bug #65607 (group octave):
I would say that my first thought is not to use 'echo on'. I only use it
occasionally when debugging, and never for ordinary usage. Is there another
way to accomplish your goal? Maybe 'diary' if you are trying to get a record
of commands and resulting output?
The root cause is that setting the path will also evaluate any PKG_ADD scripts
contained in path directories. Try `help autoload` for a description. Since
these are script files, not functions, maybe it is correct to display them?
To see that this is the case, take a look at libinterp/dldfcn/PKG_ADD. That
is where most of the commands that you are seeing are located.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65607>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #65607] cluttering text output when using path() with echo on, Hartmut, 2024/04/18
- [Octave-bug-tracker] [bug #65607] cluttering text output when using path() with echo on,
Rik <=
- [Octave-bug-tracker] [bug #65607] cluttering text output when using path() with echo on, Hartmut, 2024/04/19
- [Octave-bug-tracker] [bug #65607] cluttering text output when using path() with echo on, Rik, 2024/04/19
- [Octave-bug-tracker] [bug #65607] cluttering text output when using path() with echo on, Rik, 2024/04/19
- [Octave-bug-tracker] [bug #65607] cluttering text output when using path() with echo on, Hartmut, 2024/04/20
- [Octave-bug-tracker] [bug #65607] cluttering text output when using path() with echo on, Rik, 2024/04/20