Find string list quit working (solved)

Find string list quit working (solved)

2
NewbieNewbie
2

    13:21 - Sep 24#1

    I am running UltraEdit Text/Hex Editor (x64) version 28.10.0.26 on Windows. I'm an infrequent user of UltraEdit. What I want to do is to search for a string in whatever files I have open and return a window with all of the lines containing that string. In that window I want to click on one of the lines and go to the specific line in the file where the string is. I thought I could do this previously, but now I can't get it to work now. I've tried the following:

    "Find" --->  "Current file" + "List lines containing strings"

    This returns what I'm looking for in the "Find String List" window but only for the current file. If I then repeat and select "All open files". The "List lines containing string" (and other check boxes) turn gray but the check box remains and nothing appears in the find string list.

    I tried the "Gather Windows" in Layout, but that didn't fix it.

    I found a thread similar to what I'm seeing here: "List lines containing string" results window does not appear (solved). In following these steps I found uedit32.in0 in in %APPDATA%\IDMComp\UltraEdit. I did did not find uedit64.in0 even though the "file" ---> "about" shows x64 in the description. I followed the steps in the thread for uedit32.in0 but it didn't fix the problem. I don't see the thing blue line mentioned in the thread.

    I'm completely lost. Can someone help me figure out what I'm doing wrong?

    Thank you.

    6,682583
    Grand MasterGrand Master
    6,682583

      16:49 - Sep 24#2

      You run the wrong Find command. The Find opened with Alt+F3 or pressing twice Ctrl+F on using the default key settings has the option All open files to start the Find in the current file. There can be used the commands Find next with F3 or Shift+F3 or Find prev with Ctrl+F3 to search for the next/previous occurrence of the searched string in the current file or the next/previous opened file as often as wanted for viewing/editing all found occurrences in all opened files.

      There must be executed Find in files with Ctrl+Shift+F with selecting Open files and unchecking the option Results to edit window after clicking on the gearwheel button for getting displayed the advanced options. Clicking on button Find in the Find in Files window opens now the Output Window with the current output window tab showing the results of the Find in Files. There can be double clicked a found line to make the file containing this line the active file and setting the caret at the beginning of this line.

      I recommend also right clicking into the Output Window to see its context menu. There are the special output window commands Next message with hotkey Ctrl+Shift+DOWN ARROW and Previous message with hotkey Ctrl+Shift+UP ARROW. Those hotkeys can be pressed with an opened file having the input focus to move the caret to the next/previous found line according to output window contents in either the current file or the next/previous opened file. The output window is scrolled synchronously to see also in the output window the active found line. This feature is mainly for developers with warnings and errors shown in the current tab of the output window which is the reason for the word message in the command names Next message and Previous message, but the feature can be used also for lines found with a Find in Files with the found lines written into the Output Window.
      Best regards from an UC/UE/UES for Windows user from Austria

      2
      NewbieNewbie
      2

        21:53 - Sep 24#3

        Thank you for your help. I see now what I was doing wrong. 🙂  I did try "find in files" previously, but the output window would just flash open and then close. I didn't think to look in it for the results. I know now that I have to open the output window to see the results. I've used multiple versions of UltraEdit since version 8 and I recalled a window popping up automatically in one of those past versions. I got confused when I didn't see that happening again. I really appreciate your setting me straight.