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

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

[Octave-bug-tracker] [bug #56216] GUI Find in Documentation Tab misses s


From: Rik
Subject: [Octave-bug-tracker] [bug #56216] GUI Find in Documentation Tab misses search terms in non-intuitive way
Date: Thu, 25 Apr 2019 12:19:23 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

URL:
  <https://savannah.gnu.org/bugs/?56216>

                 Summary: GUI Find in Documentation Tab misses search terms in
non-intuitive way
                 Project: GNU Octave
            Submitted by: rik5
            Submitted on: Thu 25 Apr 2019 09:19:22 AM PDT
                Category: GUI
                Severity: 1 - Wish
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

The easiest way to see what I mean is to document an example.

Steps to Reproduce

1) Start GUI
2) Switch to Documentation tab
3) Click on Contents tab
4) Click on "1 A Brief Introduction to Octave"
5) Use Ctrl+F to bring up the Find bar
6) Type 'c', the first 'c' in the word "interface" about mid-block is
highlighted
7) Type 'o', the 'co' in "Copying" a few sentences down is highlighted.
8) Type 'm', nothing is now highlighted.

What I expect at this point is that the fragment "com" of the word "command"
is highlighted.  I can achieve this by using the Find Previous button, but
this is counter-intuitive.

Apparently as you add letters the search resumes from the last point where it
found a match.  I don't think that is what should happen.  But even if it is,
when the search fails the location should be reset to 0 and the search
attempted from the beginning of the text.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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