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

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

[Octave-bug-tracker] [bug #32088] Feature request: -ALL option for WHICH


From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #32088] Feature request: -ALL option for WHICH
Date: Tue, 15 Nov 2022 17:45:50 -0500 (EST)

Update of bug #32088 (project octave):

                  Status:         Patch Submitted => Confirmed              
        Operating System:               GNU/Linux => Any                    

    _______________________________________________________

Follow-up Comment #21:

status update: 

still present in Octave 7.3.0

-all is still the only option that doesn't work, noting however that it fails
silently (assumedly because it can't find a nonexistent file/function named
'-all'.), perhaps misleading the user.

ignoring the file #51094 version, the last patch submitted in 2011 obviously
no longer applies cleanly to the code, and in any case it worked by modifying
'path' within which.m, which seemed to be an undesirable approach.  

the initial intent to process changes in ___which___ mentioned in comment #14
stalled in 2015.  

@gyom's comment #16 file_in_loadpath m-code level suggestion seems interesting
but not sure it would capture all of the method and subfunction results as
identified in earlier comments. 

Removing the Patch Submitted status, as it doesn't seem to really apply
anymore.  

If desired, since this likely won't make it for at least another version,
attached is a patch that issues a warning rather than just failing silently.
(it also then strips the -all out of varargin, perhaps that's not necessary
since it currently fails silently.)

(file #53962)

    _______________________________________________________

Additional Item Attachment:

File name: which_all_warning.patch        Size:1 KB
    <https://file.savannah.gnu.org/file/which_all_warning.patch?file_id=53962>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?32088>

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




reply via email to

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