pFind 6.3

[rg66]

I was trying to change Default File Manager in preferences to exo-open and it wouldn't changed, kept getting this error

Code: Select all

# pfind
xwininfo: error: No window with name "pFind 6.1 - File finder" exists!
/usr/local/pfind/func: line 75: -: syntax error: operand expected (error token is "-")

Changed line 68 in /usr/local/pfind/func to XWININFO="`xwininfo -name "pFind $VERSION - $(gettext 'File finder')"`"
It's working now, looks like -stats was causing the issue.

[rg66]

Changed line 68 in /usr/local/pfind/func to XWININFO="`xwininfo -name "pFind $VERSION - $(gettext 'File finder')"`"
It's working now, looks like -stats was causing the issue.

Looks like it wasn't -stats because it's broken again, not sure what else I did but it was working briefly. Tried in slacko-6 to make sure it wasn't anything in X-slacko but same error.

[live]

II. How did you get the nice grey background color of your screenshots?

From my alternative desktop manager (for jwm)
http://murga-linux.com/puppy/viewtopic.php?p=794783

What about having a common configuration files for all puppy apps (pfind, pEasyDisk, pMusic, etc.

live wrote:
I would add:
* for audio: m4b, opus, vorbis
* for video: mp4, mkv, webm
* for code: css
Me to - thanks ')

For doc: csv as well

V. A metatag search possibility.
Extremely slow, and I don't think it is suitable for pFind.
pMusic on the other hand is already made for this.

pMusic>Advanced search
How do search on image comments exif tag?
FYI:
http://stackoverflow.com/questions/1486 ... nt-matches
http://photo.stackexchange.com/question ... erture-etc

(I compiled and uploaded Exiftool 9.82 which recently got some fixes on Unicode issues I reported)

VI. pfilesearch preferences window,
* if you could increase its width, it would be clearer to view which container are taken into account.
This is already done for pFilesearch 2.0

VII. Food for thoughs http://stefanstools.sourceforge.net/grepWin.html
Your specific thoughts are more valuable to me.

So you want some work ')
Good.

* STORED list of last 8(?) searched paths (also for pMusic advanced search)
* STORED list of last 8(?) file type match or exclusion (minus operator)
(Personnaly, I often do "*.htm*|*.txt" OR "*.htm*|*.xls|*.csv|*.txt" )
* search option skip new lines (\n \r )
* search option skip multiple skip blank (\t)
* match search option to search on apps only - let's dream that on day, we'll get voice recognition it will pipe to pfind to launch the app.
* In case Puppy goes to tablet have a portrait search were left and right pane are replace by horizontal one and larger buttons for touch screen input.
* I haven't tested if they are encoding issue such iso-latin1, utf-8, utf-16
* see also https://code.google.com/p/grepwin/issue ... %20Summary

>Your specific thoughts are more valuable to me.
Enough?

Possibly, next month I'll have some time to hack pfind code and see what I can do.

Thanks

[zigbert]

I was trying to change Default File Manager in preferences to exo-open and it wouldn't changed, kept getting this error.

Fixed in next release - thank you.

[zigbert]

V. A metatag search possibility.
Extremely slow, and I don't think it is suitable for pFind.
pMusic on the other hand is already made for this.

pMusic>Advanced search
How do search on image comments exif tag?

By default, pMusic stores metainfo to search-db when playing song.
To get all metainfo into the db at once, use the indexer tool. When done, searching for metainfo is speedy.

[zigbert]

* STORED list of last 8(?) searched paths (also for pMusic advanced search)

Be aware that pMusic share the same filesearch engine with pFind and pBurn - pFilesearch.

I really like the idea to store the last search options, but it requires a LOT of work Let's see what future brings...

Welcome to hack the code.

[zigbert]

* match search option to search on apps only - let's dream that on day, we'll get voice recognition it will pipe to pfind to launch the app.

This one should be easy if we are talking about gui-apps. They are all in /usr/share/applications/
Maybe this could be included as another group beside documents, images, ...

[zigbert]

* In case Puppy goes to tablet have a portrait search were left and right pane are replace by horizontal one and larger buttons for touch screen input.

It is not hard to solve for pFind, but first Puppy needs a mechanism to manage the gyro.

[don570]

Version 6.1 is working well in April64

geometry feature is cool.

_______________________________________

[zigbert]

Version 6.2
See main post


Changelog
- Preferences: show only available apps in the commands tab.
- Bugfix: Save preferences. (thanks to rg66)

[zigbert]

If we got fixed those pfind-6-related bugs we are ready to move on
- store search options to a history db
- search apps (this belongs to pfilesearch)

[smokey01]

zigbert, what will you use to create your history file?

Will it be text based or something like locate/slocate/mlocate?

[zigbert]

zigbert, what will you use to create your history file?

Will it be text based or something like locate/slocate/mlocate?

The history is not intended to keep the search-result, but the previous used find-commands.

Sigmund

[live]

@zigbert

Request for features:

1/ ability to search text on specific file type,
For instance "text_search" [AND] *.pdf does not do the job.
Or course, you can say that there are match profiles, but there will always be a file type not in the list or you want just for instance *.pdf and no other doc type to limit search.

2/ Pfind results add a column with extensions, so that one can sort of file type for instance txt, pdf, doc, etc.

Request for changes:
1/ Move the directory search directly under text search, as path may be quite long, it between searches it may be usefull to keep a direct eye contact on which path the search takes places

This was so in pfilesearch 1.28, thought the text area was too short.

2/ Provide the results as they come out.
Indeed, this is to cut long search, as sometimes you haven't the foggiest idea where your put your damn file and need to search from top root, but as soon as you see the right file you can stop the search.

3/ I would put "code files", just under documents, as they're a kind of doc.


I cast a look at the code to propose some modifications to send, as I'm not familiar with this environnement, which tool do you use to generate the GUI code?

Thanks for your work

[don570]

2/ Pfind results add a column with extensions, so that one can sort of file type for instance txt, pdf, doc, etc.

The SVG icons on left side are a good alternative.
For example: Image files are shown by clicking landscape icon.

___________________________________________

The feature I want is ---> When a text file on hit list is opened by Geany
(using the menu item that pfind supplies)

I want Geany to open the actual file rather than the temporary link.
That way the heading at the top of Geany window will have the true location
rather than the link's location.

_______________________________________________

[Pelo]

pFind 6.2 installed Toutou Wolx. Our french team didn't succed keeping pfind in TouTou Wolx (due to openbox, did they explain).
pFind installs without any problem.
topic France en français.

[BarryK]

zigbert,
After updating gtkdialog in Quirky, I also updated to your latest pBurn, pFind, etc. I then built Quirky.

Then I discovered there are no icons for pFind and Pschedule in the menu.

A bit of investigating, and I found the reason. Quirky does not have /usr/share/pixmaps/puppy folder.

I fixed those PETs, just using the old images in /usr/local/lib/X11/mini-icons, however, what would be the best solution going forward?

Um, I could put in /usr/share/pixmaps/puppy, but perhaps the PETs could have the icons in them?

[zigbert]

Barry
Yeah, I see - the icons are missing outside Woof-CE built systems.

- The mini-icons are on their way out of Woof-CE, so I never link icons that way anymore...
- Including an icon from /usr/share/pixmaps/puppy inside the pet will overwrite original icon in Woof-CE, and that is not good if stuff are improved at github.

I am not sure what would be the best solution?
I could of course offer 2 packages - one linking to mini-icons, but this doesn't sound like a great idea. Would it be possible to include a pinstall script that checks if /usr/share/pixmaps/puppy misses?

[BarryK]

Barry
Yeah, I see - the icons are missing outside Woof-CE built systems.

- The mini-icons are on their way out of Woof-CE, so I never link icons that way anymore...
- Including an icon from /usr/share/pixmaps/puppy inside the pet will overwrite original icon in Woof-CE, and that is not good if stuff are improved at github.

I am not sure what would be the best solution?
I could of course offer 2 packages - one linking to mini-icons, but this doesn't sound like a great idea. Would it be possible to include a pinstall script that checks if /usr/share/pixmaps/puppy misses?

Well, I suppose I can populate /usr/share/pixmaps/puppy at least with the icons for pFind, Pschedule and any other pets that use them.

[Iguleder]

Or, you can host WoofQ in GitHub, as a branch of woof-CE.