Findnrun 4.0.3 - a progressive finder - updated 2020-04-06

Filemanagers, partitioning tools, etc.
Message
Author
step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

Findnrun 4.0.3 - a progressive finder - updated 2020-04-06

#1 Post by step »

Latest version 4.0.3 released 6 April 2020
scroll down for screenshots

* Move help folder to a more standard path.

>Downloads Page

Old Release Announcements

4.0.2 released 24 January 2019

Release 4.0.2 is a recommended bug-fix upgrade for all users.

* Fix: Selected command not started (involves plugin use only).

4.0.1 released 13 January 2019

Release 4.0.1 is a recommended bug-fix upgrade for all users.

* Critical fix: Built-in fuzzy search displays no results if only search-filenames is enabled in default configuration.
* Fix: Built-in fuzzy search used even though disabled on pristine start.
* Fix: Fuzzy search engine choice displayed incorrectly in About dialog text.
* Update: user documentation and translation template.

4.0.0 released 3 January 2019

Release 4.0.0 is a recommended feature upgrade for all users.

Release highlights: * Faster, better, alternative fuzzy and exact search engine using the optional fzf external binary. * Now plugins can call the built-in and fzf search engines.

* New: integrate external search engine `fzf` for exact and fuzzy search
* New: start-up dialog to download/install `fzf`
* New: user preference `TERMINAL_PROGRAM` (defaultterm)
* Change: UI rename "Consider word case" to "A ≠ a"
* Change: UI "Show all icons" and "A ≠ a" swap places
* Change: Toggling "A ≠ a" no longer requires a restart
* Change: Toggling search details no longer requires a restart when `fzf` is used
* Fix: `findnrun-formatter -s` splits lines on spaces
* Fix: Run in terminal saves history to `.hist-` instead of `.hist-$ID`
* Fix: Null `FNR*` variables when saving drain invocation history
* Update: credits
* Update: user and plugin documentation
* Update: translation template
* Plugin: New: plugins can call the built-in and fzf search engines
* Plugin: New: plugin Helper Functions
* Dev: extend help system to allow directly opening any markdown file

Old Release Announcements

3.1.0 released 16 December 2018

Release 3.1.0 is a recommended feature upgrade for all users.

Release highlights: A new fuzzy search mode (off by default), a new configurable hotkey F6, and a configuration menu that reveals all previously hidden settings (hotkey re-assignment is still hidden in the configuration file ~/.findnrunrc). Press F10 in the main window to see hotey settings. Press F10 again to access the configuration menu, or click the new menu symbol "☰".

* New: add fuzzy search (SEARCHFUZZY setting), off by default
* New: add Options menu.
* New: fuzzy search checkbox in the main window
* New: hidden setting `FUZZY_MATCH_FIELD_BONUS`
* New: hotkey `F6` clears the search input field
* Change: remove user setting SEARCHCOMPLETE
* Fix: work around "&" in .desktop comment field
* Fix: did not show icon for `.DirIcon` files
* Fix: restart did not reset the search input field
* Update: screenshots
* Update: credits
* Update: user and plugin documentation
* Update: translation template
* Plugin dev: update `findnrun-formatter`
* Dev: add desktop file lister (debug level 1)

3.0.0 released 19 October 2018

Findnrun 3.0.0 is a recommended feature upgrade for all users.

Release highlights:
* Faster program start.
* Huge speed increase "Showing all icons".
* New: Dash compatible out-of-the-box (sh, bash and ash too).
* New: Hotkey help - hotkey F10 lists hotkey assignments.
* New: Save results - hotkey F4 saves search results to a file or command pipe defined via `RDR` in file ~/.findnrunrc.
* New: Run in terminal - hotkey F5 starts selected item in a terminal window.
* New: Run in terminal - UI button to run command entry field in a terminal window.
* New: Icon theme support - icons honor the GTK2 icon theme, if any, e.g. in file ~/.gtkrc-2.0:

Code: Select all

    gtk-icon-theme-name="Clarity"
* New: Icon theme support - override GTK2 icon theme name with new preference GTK_ICON_THEME_NAME in file ~/.findnrunrc.
* New: Source property - Add INIT_<source> to built-in and plugin source declarations.
* New: display fallback icon when no app icon exists.
* New: Allow icon names (not just paths) for built-in and plugin sources.
* Changed: Move icons from /usr/share/doc/findnrun to /usr/share/icons.
* Changed: Use icon name 'findnrun' for all sub-windows but Help.
* Changed: Reject non- Type=Application .desktop files.
* Changed: Variables XCLIP (preferences.md) and FNRSAVEFLT (plugin-dev.md) are no longer supported.
* Fix: No window auto-close after hotkey F12.
* Fix: wrong XDG_DATA_HOME initialization.
* Fix: `yad --progress` still visible after main window exit.
* Fix: Regex search fails for _Shell Completion_ source.
* Several UI messages added and changed (translations needed).
* Help and documentation files updated (translations needed).
* i18n translation template (.pot file) updated.
* Plugins: New INIT_<source>, _Saving Search Results_.

Version 2.5.0 released 24 August 2018

Findnrun 2.5.0 is a recommended feature upgrade for all users.
Release highlights:
* Faster application start thanks to new translation lookup method, new icon caching algorithm, and optimized plugin validation.
* New progress dialog for long scans.
* Change: yad replaces Xdialog for sub-dialogs.
* Updated German (63%) and Italian (100%) translations.
* Fix: single quote in plugin code was invalid.
* Fix: some documentation typos.
* New translation tools.

Version 2.4.1 released 13 September 2017

Findnrun version 2.4.1 is a recommended upgrade for German users.
Release highlights: Updated German translation (thanks L18L).

Version 2.4.0 released 6 September 2016

Findnrun version 2.4.0 is a recommended upgrade for all users.
Release highlights: The main window displays more configuration settings. Open the configuration file for editing directly from the main window. Symbolic links to .desktop files are supported (thanks SFR). Updated Italian translation (thanks xanad).

Version 2.3.0 released 1 August 2016
Findnrun version 2.3.0 is a recommended upgrade for all users.
Release highlights: Find applications installed by `wine`. Update Italian translation.

Version 2.2.0 released 2016-06-13
Findnrun version 2.2.0 is a recommended upgrade for all users.
Release highlights: New features, a new plugin, and some bugs fixes.

Version 2.1.1 Released 2015-04-25
Findnrun version 2.1.1 adds German and Italian translations, and fixes some minor issues. Recommended upgrade for all users.

Version 2.1.0 Released 2015-03-11
Findnrun version 2.1.0 is a bug-fix, compatibility and documentation release. Recommended upgrade for all users.

Version 2.0.0 Released 2015-01-24
Findnrun version 2.0.0 is a major new release. Main new features since version 1.10.6 include plugin support, hotkeys, improved icon GTK compatibility, faster search, and many minor improvements and bug fixes. Significant new plugins include the Shell Completion bundled plugin, and the Filmstrip demo plugin.

Last edit:Sun 13 Jan 2019, 13:12 - All times are UTC - 4
Attachments
findnrun-3.1.0-main-fuzzy-completion.png
Main window open on _Application Finder_ fuzzy search results. GTK2 theme 'Windows10Light' and GTK2 icon theme 'Clarity' on Fatdog64.
(23.94 KiB) Downloaded 607 times
findnrun-3.1.0-custom-hotkeys.png
Hotkeys - Some default and some custom assignments are mixed together.
(30.68 KiB) Downloaded 604 times
findnrun-3.1.0-options-menu.png
Options menu
(18.93 KiB) Downloaded 610 times
Last edited by step on Mon 06 Apr 2020, 15:25, edited 26 times in total.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#2 Post by step »

Reserved
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#3 Post by step »

This post is for translators

Version 2.1.0 significantly improves the translation kit. Reading the tutorial is recommended. Feedback is welcome.

Tutorial: Translations Demystified - explains what and how to translate Findnrun. Required reading for all translators, beginners and experts alike.

Some new things that need your attention:
  • When you start translating please let me know, so I can (1) keep you better informed of late-breaking news concerning translations, and (2) update the translation status at the bottom of this post.
  • The name "Find'N'Run" disappears from the script and documentation - except when it refers to the earlier script by FSR and L18L.
    Now please consistently use "Findnrun" - as you can see in the updated markdown documentation.
  • The tag line "Find and run applications very quickly" equally disappears from the script and .desktop file. The new tag line "Find applications and more" is a compromise between what we had before and my view of Findnrun as a "progressive finder" extensible to different data types by means of plugins. I kept the reference to "applications" because I reckon that most people will care for that one feature.
  • You really need to use the reference .pot template file, which is built using this script.
  • HTML documentation is discontinued. L18L's posts >1, >2 stimulated a transition to markdown format. This project is a testbed for mdview, a tiny but powerful markdown viewer that comes standard with Fatdog64-701, and is also available as a Woof-CE build recipe.
  • Until bugfixes are backported, you need to download and use the custom mdview version available from Findnrun's download page. See the Tutorial for instructions.
Translating Help Files

As I mentioned I hope for at least some of the markdown documentation to be translated.
Since the target is the end-user, the goal is to translate all end-user help files, which are:
CREDITS.md
hotkey.md
index.md
install.md
install-require.md
issues.md
plugin-list.md
plugin.md
preference.md
running.md
screenshots.md

The reference .pot file combines all window and dialog messages with the text extracted from the above list of .md files. Other .md files have been excluded. So, translating the pot text set is all that's needed.

Q: Is mdview available for your puppy OS?
A: Fatdog64-702 comes with mdview built-in and also as a gslapt package. For other puppies I know that Woof-CE includes an mdview build recipe but I don't know which puppies actually build it. Unofficial 32- and 64-bit builds can be downloaded from the findnrun release page. Those builds are meant for translators and include some necessary patches. End users should instead install an official mdview version >= 2016.04.26.

Translation Status

I have "volunteered" the names of all previous translators. Feel absolutely free to turn this incredible offer down if you can't help. :)

* Chinese, 1.6.10, icake
* French, 1.6.10, ASRI
* German, 2.4.1, L18L
* Italian, 2.4.1, xanad
* Spanish, 1.6.10, Nelson Morales

Last edit: Wed 13 September 2017, 11:32 All times are UTC - 4
Last edited by step on Wed 13 Sep 2017, 15:33, edited 8 times in total.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

User avatar
SFR
Posts: 1800
Joined: Wed 26 Oct 2011, 21:52

#4 Post by SFR »

Hey Step

Glad to see FNR is evolving. :)

Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#5 Post by step »

Thanks SFR, I stand on the shoulders of giants :)
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

#6 Post by L18L »

step wrote:@L18L I don't know if the findnrun script is ready to show translated markdown or if I need to change it. Can you please advise me?
Append messages from .md files to your findnrun.pot:

Code: Select all

cd /usr/share/doc/findnrun; for f in $(ls *.md); do [ "$f" != "TRANSLATING.md" ] && mdview --po $f >> bla ; done; msguniq bla >> /usr/share/doc/nls/findnrun/findnrun.pot; rm bla
Note
- excluded TRANSLATING because of some errors (and translators translate from English thus no translation)
-No
%%textdomain findnrun
in .md file necessary

- Partially translated using momanager see screeny

This answers your question: scripts are ready to run translations.
Attachments
doc_findnrun.png
(31.87 KiB) Downloaded 1549 times

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

#7 Post by L18L »

@step
my post of yesterday was a shot too quick.
Scripts are ready to run translations but I did not care about your detailled request.

The usual way to create a pot file from several source files is using xgettext parameter --files-from=<file>

Thus, for mdview we should use also a file:

Code: Select all

cd /usr/share/doc/findnrun
echo "hotkey.md index.md install.md issues.md no-help.md plugin.md preference.md running.md CREDITS.md examples/filmstrip/README.md" > translate
Create .pot file:
Re-create your original -pot file using xgettext; then run

Code: Select all

cd /usr/share/doc/findnrun; for f in $(cat translate); do mdview --po $f >> bla ; done; msguniq bla >> /usr/share/doc/nls/findnrun/findnrun.pot; rm bla

Looking into multi-field.tap.sh,
why TEXTDOMAIN="findnrun-plugin-multi" ?
I would use one TEXTDOMAIN for all.
Re-create your pot file using xgettext <list of files>

ALTERNATIVELY:
Let me know if you want to use the automatic (puppy momanager) solution for dynamically creating pot file.
- Insert %%textdomain findnrun in each .md file that can be translated
- Use export TEXTDOMAIN=findnrun in the scripts
- Do not distribute any findnrun.pot, it will be created dynamically
The only thing I would have to add to momanger is: make use of xgettext parameter -c
and momanager will do all the work. 8)


LICENSE.md
Why not just a link to one of http://www.gnu.org/licenses/
and translators can additionally link to an existing unofficial translation from
http://www.gnu.org/licenses/translations.html if available.

Other notes might follow when translation starts ....

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#8 Post by step »

L18L wrote:@step
my post of yesterday was a shot too quick.
Scripts are ready to run translations but I did not care about your detailled request.
Thanks for your answers! I'm consolidating them in a script that creates the .pot file. I'll post about it when it's done.

Looking into multi-field.tap.sh,
why TEXTDOMAIN="findnrun-plugin-multi" ?
I would use one TEXTDOMAIN for all.
Re-create your pot file using xgettext <list of files>
No, I want separate TEXTDOMAINs because plugin development is separate from findnrun. This way a plugin developer has all the freedom to localize the plugin the way he wants, and the findnrun development/localization track isn't encumbered.
Findnrun automatically uses gettext from a plugin TEXTDOMAIN as long as the text domain name follows the rule "findnrun-plugin-"<plugin name>. Currently, this is used to show translated plugin titles in the status bar and for nothing else. Finally, plugins can load gettext messages from their own TEXT domain, it's their option.
ALTERNATIVELY:
Let me know if you want to use the automatic (puppy momanager) solution for dynamically creating pot file.
Thanks for the offer, but not now I think. I prefer to get a stable i18n release cycle before I start changing tools again.
LICENSE.md
Why not just a link to one of http://www.gnu.org/licenses/
and translators can additionally link to an existing unofficial translation from
http://www.gnu.org/licenses/translations.html if available.
Good idea. But the license terms themselves say that a license file must be included with the software. Providing just the link to an online copy of the license doesn't meet the terms. Can't the translator simply replace the English license text with the corresponding translation from http://www.gnu.org/licenses/translations.html, if available?
Other notes might follow when translation starts ....
When you do start the translation let me know and I'll update the 'translation status' post.
Thanks for your feedback and help.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

User avatar
LazY Puppy
Posts: 1934
Joined: Fri 21 Nov 2014, 18:14
Location: Germany

#9 Post by LazY Puppy »

Hi.

I have tried version 2.0.0, though I couldn't let it search for anything else than .desktop files.

How does all the other stuff work (Images, Filmstrips etc.)?
Any additions needed?
Any Guide available to set it up?

Thanks
RSH

"you only wanted to work your Puppies in German", "you are a separatist in that you want Germany to secede from Europe" (musher0) :lol:

No, but I gave my old drum kit away for free to a music store collecting instruments for refugees! :wink:

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#10 Post by step »

@RSH - You should at least be able to search for shell commands. After findnrun starts and shows desktop applications, press F3 - it should change the list to shell commands. If it doesn't then we need to troubleshoot:
1. What puppy version are you running on?
2. Do you or did you have another version of findnrun installed? Which version?
3. Attach contents of your ~/.findnrunrc file.

Filmstrip documentation is located in /usr/share/doc/findnrun/examples/filmstrip/README.md. Open with mdview (preferred) or a text editor.
Here's a link to the online version of Filmstrip README.md

Findnrun user documentation is located in /usr/share/doc/findnrun/. Open by pressing F1 in findnrun main window, or open file index.md directly with mdview or a text editor.

Thanks for trying, keep feedback coming.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

#11 Post by L18L »

step wrote:When you do start the translation let me know and I'll update the 'translation status' post.
started...

Code: Select all

#: /usr/share/doc/findnrun/index.md:52
msgid "[2] Markdown files can be confortably read as plain text files. To browse markdown files install the `mdview` package."
This comfort can apply only for English as the plain text files are and stay English only.
The comfort of translation (if exists) can be gotten only by using mdview.
But the license terms themselves say that a license file must be included with the software. Providing just the link to an online copy of the license doesn't meet the terms. Can't the translator simply replace the English license text with the corresponding translation from http://www.gnu.org/licenses/translations.html, if available?
The license tells another story about translations
Suggest to embed the content of LICENSE.md into
%%nopot yes
and
%%nopot no
to prevent it from being gettexted.

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#12 Post by step »

L18L wrote:
step wrote:When you do start the translation let me know and I'll update the 'translation status' post.
started...
OK, thanks, post updated.

Code: Select all

#: /usr/share/doc/findnrun/index.md:52
msgid "[2] Markdown files can be confortably read as plain text files. To browse markdown files install the `mdview` package."
This comfort can apply only for English as the plain text files are and stay English only.
The comfort of translation (if exists) can be gotten only by using mdview.
Good points. I will change those sentences in the markdown files. So non-English readers have one additional motivation for installing mdview! :)
Suggest to embed the content of LICENSE.md into
%%nopot yes
and
%%nopot no
to prevent it from being gettexted.
Actually I was just going NOT to include the contents of LICENSE.md into findnrun.pot - but I will still add those fences to the .md file, as you recommend.

I am going to push a few i18n updates to github today. Including the unified .pot file. I hope that won't upset your translation too much. Thanks for your help!
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Findnrun 2.0.0 - a progressive finder

#13 Post by L18L »

step wrote:I am going to push a few i18n updates to github today. Including the unified .pot file. I hope that won't upset your translation too much.
No worries, updates are part of life.
Translations of updates are not lost, they are mostly marked fuzzy.
You have more work with updating your static findrun.pot.

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

Re: Findnrun 2.0.0 - a progressive finder

#14 Post by step »

L18L wrote: No worries, updates are part of life.

You have more work with updating your static findrun.pot.
Panta rei! I build findnrun.pot with this script.

I just uploaded the updated version.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Re: Findnrun 2.0.0 - a progressive finder

#15 Post by L18L »

step wrote: I build findnrun.pot with this script.

Code: Select all

msguniq --no-wrap --no-location "${FPOT}.tmp"
I (and all translators) do need locations.
- see context
- see what is no more actual (no context - no more needed)

please use headers ## and ### not just ** **
ex:
35 msgid "**Packages**"
381 msgid "Packages"

if ### packages there is one translation only.


Let the flow continue.

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

Re: Findnrun 2.0.0 - a progressive finder

#16 Post by step »

L18L wrote: I (and all translators) do need locations.
- see context
- see what is no more actual (no context - no more needed)
Of course. Script updated to add locations. .pot file updated. I also moved some paragraphs across files to delete duplications.
please use headers ## and ### not just ** **
ex:
35 msgid "**Packages**"
381 msgid "Packages"

if ### packages there is one translation only.
I try to minimize unnecessary duplications as much as possible. The one you listed is the only one that I'm going to keep. The reason why is that where "**Packages**" occurs a level 3 header style would be "too much". The whole page comprises essentially three short paragraphs, and I don't want to add three headers between the paragraphs. In HTML I could use H5 or H6 headers instead, but mdview is limited to level 3 headers, so we have to live by that limitation and make the best of it. But again, "Packages" is the only such case I found.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

User avatar
LazY Puppy
Posts: 1934
Joined: Fri 21 Nov 2014, 18:14
Location: Germany

#17 Post by LazY Puppy »

step wrote:@RSH - You should at least be able to search for shell commands. After findnrun starts and shows desktop applications, press F3 - it should change the list to shell commands. If it doesn't then we need to troubleshoot:
1. What puppy version are you running on?
2. Do you or did you have another version of findnrun installed? Which version?
3. Attach contents of your ~/.findnrunrc file.

Filmstrip documentation is located in /usr/share/doc/findnrun/examples/filmstrip/README.md. Open with mdview (preferred) or a text editor.
Here's a link to the online version of Filmstrip README.md

Findnrun user documentation is located in /usr/share/doc/findnrun/. Open by pressing F1 in findnrun main window, or open file index.md directly with mdview or a text editor.

Thanks for trying, keep feedback coming.
Hi step.

Thanks for the reply.

@1.
I'm running findnrun in different Puppies (some are remastered, some not) from Lucid-528-4 up to Vivid beta2.

@2.
I'm running findnrun as a RoxApp from my external RoxApps Directory by a Menu Entry in a Menu Pipe. If there is a findnrun installed the it was done by the Puppy Creator/Builder. Currently I'm running tahr 6.0.2; findnrun seems not to be installed here.

@3.
Currently I don't have a ~/.findnrunrc file as I'm still running 1.10.8. Haven't tested yet the new 2.0.0 again.

Though I did run into another different issue related to the symbolic links made to icons. That symbolic links are placed in /root/.icons.

I wanted to give this a different location (e.g. /root/.findnrun/.icons as /root/.icons contains the Mouse Cursor Themes)

So I replaced .icons by .findnrun/.icons inside the findnrun script.

No success!

The symbolic links still appearing in /root/.icons.

What am I doing wrong here?
RSH

"you only wanted to work your Puppies in German", "you are a separatist in that you want Germany to secede from Europe" (musher0) :lol:

No, but I gave my old drum kit away for free to a music store collecting instruments for refugees! :wink:

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#18 Post by step »

LazY Puppy wrote:What am I doing wrong here?
I don't know, sorry. Please note that I can only support findnrun 1.10.6 and 2.0.0, which can change the icon path by setting the path in file ~/.findnrun. FSR supports version 1.8.0 in his Find'N'Run thread, I think. Interim versions aren't supported.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Re: Findnrun 2.0.0 - a progressive finder

#19 Post by L18L »

step wrote:..Script updated to add locations. .pot file updated...
downloaded https://github.com/step-/find-n-run/blo ... ndnrun.pot

Code: Select all

# file findnrun.pot
findnrun.pot: HTML document, UTF-8 Unicode text, with very long lines
#
:roll:

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#20 Post by step »

@L18L, for downloading use the raw page.

When you're viewing a page on github, press the "raw" button then right click and save the raw page.

Please, did I write the html page link somewhere? I can't remember if I did and where.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

Post Reply