Author Topic: Find in Files (current buffer) worked but Quick Find (current buffer) did not?  (Read 4027 times)

JimmieC

  • Senior Community Member
  • Posts: 490
  • Hero Points: 17
I "think" I ran into a strange case. Find in Files found search results but it seems that Quick Find cannot find any of them. I am just starting to use Quick Find so perhaps it is user error.

The only thing thing noteworthy is that the file I am search is not part of the open project. I dragged the file onto SE.

See attached screen capture (3.2 MB, hopefully the forum will upload it).

Jim

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1299
  • Hero Points: 130
Not quite sure what could be going on there.  I do not know how it got in that state, I am not able to replicate anything like that in testing.  If you close the Mini-find and bring it back up does it still not find anything?

JimmieC

  • Senior Community Member
  • Posts: 490
  • Hero Points: 17
Closed mini-find and re-opened with Ctrl-F, did not fix it.

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1299
  • Hero Points: 130
Could you record a macro trying with mini-find and post the recorded macro source?  There may be an option that is not supposed to be there or something else I am not seeing in the video.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Along similar lines...try reproducing this in a clean config (vs +new -sc <new-temp-config-dir>)

JimmieC

  • Senior Community Member
  • Posts: 490
  • Hero Points: 17
I did a couple of searches with Find In Files, then using mini-find.
#include "slick.sh"
_command last_recorded_macro() name_info(','VSARG2_MARK|VSARG2_REQUIRES_EDITORCTL)
{
   _macro('R',1);
   _mffind2("8000|rts430","LI","<Current Buffer>","*.map;*.cmd",'',"224",'1');
   _mffind2("8000|rts430","LI","<Current Buffer>","*.map;*.cmd",'',"224",'0');
   if (find("8000|rts430","IP?+")) stop();
   if (find_next('0')) stop();
   if (find_next('0')) stop();
   if (find_next('0')) stop();
   if (find_next('1')) stop();
   if (find_next('1')) stop();
   if (find_next('1')) stop();
}

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1299
  • Hero Points: 130
Weird.  Macro is reporting that Regular Expression is not enabled, which would at least explain why there are no matches, but I clearly see the Regex button enabled and using the Perl syntax in the video for Mini-Find.  Is the status line also report that Regular Expression(Perl) is in use, I can't see that part in the video.

JimmieC

  • Senior Community Member
  • Posts: 490
  • Hero Points: 17
Attached is png of the whole screen. I am not sure where the Regex status would\should be so I took a snapshot.
Jim

JimmieC

  • Senior Community Member
  • Posts: 490
  • Hero Points: 17
Clark,
A clean config produced the same result; Did not fix it.
Jim

EDIT: Clean config fixed it, I did not have Regex enabled on mini-find after clean config.
« Last Edit: December 13, 2016, 06:07:49 PM by JimmieC »

JimmieC

  • Senior Community Member
  • Posts: 490
  • Hero Points: 17
Clark,
Correction.
After a second look, a clean config fixed it.
I did not have Regex enabled on mini-find after clean config.
Jim

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1299
  • Hero Points: 130
I reviewed the underlying code, and it does appear possible something like that could happen.  I am going to add sanity checks to prevent that problem in an upcoming hotfix release.

JimmieC

  • Senior Community Member
  • Posts: 490
  • Hero Points: 17
OK. I tested with Clark's suggestion of a clean config, which fixed it. However, that was done in separate directory from the command line.

How do I reset the config in the default My SlickEdit Config folder?

Jim

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1299
  • Hero Points: 130
It may be enough to change the Regular Expression syntax from Perl to SlickEdit, close the dialog, then open it up again and change it back.  That may correct the data that is causing the issue.  Give that a try.