PCREsearch Basic Install and Usage Instructions video

[johnstonf]

RE: PCREsearch...

NOTE: AFTER THE FACT... I CREATED A VIDEO. SEE IT AT...
http://bit.ly/TotalCommanderPluginPCREsearch

ORIGINAL MESSAGE FOLLOWS...
Is there a video or a basic set of A-Z instructions for installing? (and sample run of the search)... (Like for normal, but non-stupid people who have used TC for a long time, but never used a PlugIn?). I can edit files not problem, but just need to know how/what...

(A youtube basics thingy like 2-3 minutes long would be so great)...

I'm lost...

I put the rar in c:\totalcmd\pcresearch folder, then unzipped the rar

Now i'm looking for (apparently) a .cfg file, but it is NOT in the set I unzipped.

Then I don't know how to combine the plugin into TC.

Help!
Thanks!

[johnstonf]

ok, one step further (using instructions from another plugin...) instead, I just ran the .rar file from TC, and it installed under c:\totalcmd\plugins\wdx\PCREsearch\... now what?

RE: PCREsearch...

Is there a video or a basic set of A-Z instructions for installing? (and sample run of the search)... (Like for normal, but non-stupid people who have used TC for a long time, but never used a PlugIn?). I can edit files not problem, but just need to know how/what...

(A youtube basics thingy like 2-3 minutes long would be so great)...

I'm lost...

I put the rar in c:\totalcmd\pcresearch folder, then unzipped the rar

Now i'm looking for (apparently) a .cfg file, but it is NOT in the set I unzipped.

Then I don't know how to combine the plugin into TC.

Help!
Thanks!

[milo1012]

First of all, you should post this in the official plugin thread.

Second, a video is a bit far fetched IMO, there are some plugins which are even harder to set up.

Just auto install the plugin, like you did.
Now there's a Readme.html file in the install dir, which describes in detail what you need to do.
The default ini (PCREsearch.Sample.ini) already comes with eight fields activated,
so if you're referring to the answer I gave in this thread, open that file (now found in the install dir) with an editor and just overwrite the fields:

Code: Select all

regex1=
regex1name=
regex1type=

(they are already there)
with the content I gave you and modify them to your liking.

Restart TC.
Now, for using it, use the TC search (Alt+F7) and go to plugin tab and select the PCREsearch plugin and the field you just set up (recognizable via the name you entered).
regex1type=0 means yes/no field, so set it to 'yes' to find files that contain your search term.
The rest is up to you (search location, maybe file types), so you can start the search now.

You can also use it for custom columns, but that is another story.


BTW, there are a lot of plugins that are configured through their INI file.
The first thing you should do is looking for a readme file for how to set them up.

[johnstonf]

I made a YouTube video showing others how to quickly get this installed into TC. See it at http://bit.ly/TotalCommanderPluginPCREsearch and hope it helps others to get this nice plugin into their lives quickly and easily.

http://bit.ly/TotalCommanderPluginPCREsearch

[milo1012]

I made a YouTube video showing others how to quickly get this installed into TC.

Nice!
Also a good general instruction for how to set-up (content) plugins.
Many thanks.

One thing though: you had two PCREsearch sections in your ini file at the end (when you saved it).
It still worked like expected because the first section is disregarded when there is a 2nd (but might not if the order would be reversed).

[johnstonf]

Thanks for the @milo1012 !
I re-edited the video, and put it back up...
New link (so i don't have to keep changing the link here) is...
http://bit.ly/TotalCommanderPluginPCREsearch

Maybe you could have a look and see if it looks ok.

/Fred

I made a YouTube video showing others how to quickly get this installed into TC.

Nice!
Also a good general instruction for how to set-up (content) plugins.
Many thanks.

One thing though: you had two PCREsearch sections in your ini file at the end (when you saved it).
It still worked like expected because the first section is disregarded when there is a 2nd (but might not if the order would be reversed).

[johnstonf]

I seem to be able to use this for finding which FILES contain the condition, eg "APPLE within 50 words of ORANGE", but I'm trying to find WHERE in the document the actual occurrence of the condition exists, as it is HUGE. Can I somehow still use PCREsearch to do this? Thanks!

I made a YouTube video showing others how to quickly get this installed into TC.

Nice!
Also a good general instruction for how to set-up (content) plugins.
Many thanks.

One thing though: you had two PCREsearch sections in your ini file at the end (when you saved it).
It still worked like expected because the first section is disregarded when there is a 2nd (but might not if the order would be reversed).

[milo1012]

I'm trying to find WHERE in the document the actual occurrence of the condition exists, as it is HUGE. Can I somehow still use PCREsearch to do this? Thanks!

Not directly, but what you can do: display the resulting string, so that you can view it in custom columns.
I don't know how your files are structured, but when there are certain unique words/strings in between these two search terms
you're looking for, that might help you identifying the position.
So: you could view the custom column for that file, look for such supportive strings,
open that file in some viewer/editor and use a normal search for those strings, which will lead you to the position of your terms.

If this is not enough to find the position(s) for you:
I'm currently working on a new version which can (besides other things)
return the file offset of each result. I could upload the beta version if you
think it helps, i.e. that you can work with the offset.
The final version will also be able to return the line numbers, but that feature isn't finished yet.

If none of this helps you identifying the positions, I think programs like the mentioned
TextCrawler are better for now.

re-edited the video, and put it back up... ... Maybe you could have a look and see if it looks ok.

Great, it's fixed now.
All is explained correctly. Thanks!