title: How can I get Eclipse IDE to default to "Selected lines" in the Find/Replace dialogue when multiple lines are selected?
body: <p>When working in Eclipse and hitting Ctrl+F with lines of code selected, the default behavior I expect is for the Find/Replace dialogue to open with the "Selected lines" option and, perhaps, either buffer contents or a previous search query in the "Find" prompt. On my home machine, what happens instead is the entire selection gets automatically copied to the "Find" prompt and Scope is reset to "All" instead of "Selected lines" every time.</p>
  
  <p>I somehow <em>do</em> have this working by default on my work machine: "Selected Lines" scope option is chosen automatically when more than one line is selected in the editor.</p>
  
  <p>Possibly unrelated: I do have CDT installed and I work mostly with C++ in Eclipse. Home machine is running Ubuntu 18.10, work machine is running Ubuntu 18.04.</p>
  
  <p>I tried:</p>
  
  <ul>
  <li>Re-downloading Eclipse, reinstalling CDT &amp; cmake4eclipse</li>
  <li>Changing to a new Workspace in Eclipse (without copying settings)</li>
  <li>Searching high and low online for recipes on how to control this.</li>
  </ul>
  
  <p>How do I change the IDE at home to the desired "Selected Lines" behavior?</p>
  
  <p>[Edit 1 hour later]: I am now almost convinced the issue has to do with the Ubuntu version somehow. I'm running 18.04 on my Laptop (same as my work computer) and I just upgraded CDT &amp; Eclipse Platform to latest stable versions (9.7 and 4.11/2019-03, respectively), which I have everywhere else. The new "wrong" behavior didn't appear. I will also start a thread on the Eclipse forums or perhaps even open a bug report. I don't want to reinstall the whole system or downgrade it (slim chance of success) just to get this back; if it's an Eclipse bug, I'd rather work on fixing it.</p>
  
  <p>[Edit 2 days later] The bug did not manifest on a fresh install of Ubuntu 18.10. I still have no idea what was different on the 'culprit' machine. I ended up wiping the drive and reinstalling 18.04 on the same machine and the problem went away.</p>