[Octave-bug-tracker] [bug #65753] Documentation window: Function Index: Search box respects trailing spaces

[John W. Eaton]

Follow-up Comment #7, bug #65753 (group octave):

I agree, we should not remove characters from search strings unconditionally. 
I understand that there might be some confusion if searching for "abc " fails
when the spaces are not visible in some way.  But always stripping them could
also be confusing.  If the search fails, can we display a message that quotes
the spaces in some way that makes them visible or otherwise points out that
the search may contain unusual or non-printing characters?

"Often when I Ctrl+C copy from other apps such as a browser, the Clipboard
picks up a trailing space."

What causes the extra space to be included in the copied text?  If it is just
because your selection was sloppy and you included extra characters
unintentionally, then how could Octave possibly know that?  It seems bad to me
to always assume that we know better than the user what it is they are trying
to search for.


    _______________________________________________________

Reply to this item at:

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

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