Pelo's ill-founded -- and who knows, malicious? -- comments are no way to
thank those, me included, who work so hard to build software repertoire
for the Puppy community.

As to the "required" items mentioned in the panel illustrated in this post
they are all in modern Puppies by default, except for replaceit, bcm and
aemenu-pango, which are in MRUF-lst's "execs" pet archive available here..

As to the browsers listed, Puppies offer at least one of them by default.
So "dependency hell", my eye!

You people are quite something! When are you going to stop hitting on
anyone trying to do something new just to compensate for your miserable
lives? When are you going to develop the instinct of checking facts before
sticking your foot in your mouth?

Posted: Sun 13 Aug 2017, 06:37 Post subject:
they are all in modern Puppies by default, except..

"they are all in modern Puppies by default, except for replaceit, bcm and
aemenu-pango, which are in MRUF-lst's "execs" pet archive available here.."
yes i agree. I told you i don't want installing a WM such aewm.. Only for MRU list, furthermore.
This WM is so complicated.. People, don't mind.. Try MRU.. I would'nt stop any try.. It is not in my mind, and if it was, i don't have such a power on other users
I Tried it just for helping musher0 with a feed back.. Apps have their own history listed, MTpaint for instance.. Perhaps some have not. But it's really not my cup of tea !

Memo.jpg

Description

Thesee three have their own recent used files

Filesize

54.83 KB

Viewed

190 Time(s)

_________________Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.

Posted: Sun 13 Aug 2017, 07:12 Post subject:
Re: they are all in modern Puppies by default, except..

Pelo wrote:

"they are all in modern Puppies by default, except for replaceit, bcm and
aemenu-pango, which are in MRUF-lst's "execs" pet archive available here.."
yes i agree. I told you i don't want installing a WM such aewm.. Only for MRU list, furthermore.
This WM is so complicated.. People, don't mind.. Try MRU.. I would'nt stop any try.. It is not in my mind, and if it was, i don't have such a power on other users
I Tried it just for helping musher0 with a feed back.. Apps have their own history listed, MTpaint for instance.. Perhaps some have not. But it's really not my cup of tea !

The above is what you should have said in the first place instead of lying.

In short, you don't like it and you don't have a need for it. Fine by me.
Except for the attack on my reputation.Some feedback, ah!

As to you having no power on other users, the posts at the bottom of the
previous page speak to the contrary.

I didn't answer Pelo because his comment made it so obvious that he did
not try this script. He wrote a lie.

You should have instead of polluting your alleged answer to me. It is not too late. Cut and paste your rant in a different post addressed to Pelo. It has nothing to do with me. I don't give a damn about your feud with Pelo. Keep me out of it. Your inelegant rant had no place in responding to me.

I saw in very early posts that aemenu was a dependency.
I saw here a screenshot that clearly stated that aemenu among others was a Requirement. Though your command of English is excellent, I fell compelled to remind you of the meaning of the word, just in case you had a momentary lapse, so here is a meaning I googled:
requirement: a thing that is compulsory; a necessary condition. [the emphasis is mine]
Any sane person understands that a requirement in this context meanss "it won't run". Either it is going to crash or will exit gracefully with or without a message.

I included a quote from Pelo's post simply because his report agreed with my expectation ("it won't run") and dare I say, every other person on this planet based on your own writing.

Based on the logical premise that MRUF|D-lst would not work in puppies without the Requirements, I offered the constructive suggestion to wit:

Quote:

consider packaging the requirements in MRUF|D, test for each prereq and offer to install it/them if missing. You know, given that option I think I would try it. And if I don't like, it's no sweat to uninstall. It is a lot easier than if I had to search for and install for each prereq, the version that is sure to work.

Your response was

Quote:

Everything you need to run MRUF-lst is included in the pets. While MRUF-
lst uses the stand-alone menu application that comes with aewm, it
is not dependent on the aewm window manager.

Well musher0, it is a requirement or it isn't. Make up your mind. Stop speaking out of both sides of your mouth. You are just being insincere, dishonest, untruthful, false, deceitful, duplicitous, lying, mendacious; hypocritical. Did you not post a host of screenshots with the aewn window manager? What do you suppose those who download MRUF|D-lst expect to see? Something different? If you were "selling" something differeny, why have you never once posted a screenshot that shows MRUF|D-lst without the aemenu window manager? NOT ONCE! Why? Because it wasn't meant to be. And the "Requirement" blurb tells us it isn't meant to be. Now you come with this CYA nonsense .

You have excluded aemenu and others. That was the issue in my post. Since you don't seem to read so well, let me repeat.

Quote:

Maybe you would consider packaging the requirements in MRUF|D, test for each prereq and offer to install it/them if missing. You know, given that option I think I would try it. And if I don't like, it's no sweat to uninstall. It is a lot easier than if I had to search for and install for each prereq, the version that is sure to work. What's your reaction when you try to install a program and there are missing dependencies? Duh!

The provisioning of "most recently used" functionality is a useful one. I have often wished I had it. That is what brought me to look at the thread after 11 months of ignoring it. But with your attitude and egocentricity, I'd rather do without. My loss, you say? Yes! Integrity I have. Can't say the same about you.

Quote:

Kauler has included this app in his 64-bit Quirky-8.3 "xerus"

But, have you seen it in his Quirky? With or without aewm window manager? I'll bet my last Canadian silver dollar that Barry includes everything and does not ask his users to go pck up the pieces. That's the difference between a professional and a hack._________________B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM

Pelo's ill-founded -- and who knows, malicious? -- comments are no way to
thank those, me included, who work so hard to build software repertoire
for the Puppy community.

Why are you telling me this. Address it to Pelo. You know @Pelo, don't you? Use it. Read my lips. I don't give a damn about you and Pelo.

Quote:

As to the "required" items mentioned in the panel illustrated in this post
they are all in modern Puppies by default, except for replaceit, bcm and
aemenu-pango, which are in MRUF-lst's "execs" pet archive available here..

As to the browsers listed, Puppies offer at least one of them by default.

With all this knowledge, why the Required blurb Christian? Who wrote it? Not me! Do you know?
You are just trying to CYA, post facto. Get outta here. You are too duplitious for my liking.

Quote:

So "dependency hell", my eye!

No! To hell with Requirements, it means nothing!

Quote:

You people are quite something! When are you going to stop hitting on
anyone trying to do something new just to compensate for your miserable
lives?

You know nothing about me and my life. On the other hand, you are showing all how silly, paranoid, manipulative untruthful and self-centered you are.

Quote:

When are you going to develop the instinct of checking facts before
sticking your foot in your mouth?

What facts? The fact that you stated that aemenu and others were required and then you retract that need ; the fact that no puppy has aemenu OOTB. Those facts I can agree on. Now, you whiner, please, pretty please tell us what facts you are speaking of.

Help me out -- as a native English speaker -- instead of bashing me.
Please tell me what the right words would be.

What is the difference, in computer terms, between "required" and
"dependency"?

In my mind, they are not the same.

A "dependency" is a library the user needs to add to an app for the
app to run. The understanding in the Linux world AFAIK being that the user
has to go fetch this library from an outside repository.

bcm, aemenu-pango and replaceit are not dependencies in that sense:
they are not libraries, they are complete utilities by themselves,
and they are offered right here for download, alongside the main script.

I did mention the "required version" ofsome utilities, because older Puppies:
-- do not have the real less by developer Greenwood; they have the
stripped-down less utility in busybox
-- and they have lesser versions of bash and urxvt.

If the user's Puppy does not have them, or an adequate version of them,
how do you say to the user: "Use a newer version of Puppy if you wish to
run this script. Otherwise it won't run properly."

I did mention some data files as "required" because if they are empty or
non-existent, some sub-menus in MRUF-lst will not show. MRUF-lst relies
on the program's history or configuration file (if the history is in the config
file) rather than on the program itself.

~~~~~~~

As to my paragraphs about pelo, they are telling the truth and they'll stay.
This is not "my" opinion; it is not a "rant"; there is a consensus about this
among French-speaking members.

(self-censored)

I see chasing away users and developers of particular linguistic community
as causing damage to the entire Puppy community.

-- Choice of font sizes removed because it created "kerning" problems.
Font size is set at 15. If you have an absolute need, you can edit it
directly in a file named "Size" at /usr/local/MRUF-lst/share/MRUF.

-- I have added a couple of new code lines for better centering of some
main titles and separators.

-- The sub-routine for checking the "xbel" file, which used to be at the
beginning of the main MRUF-lst script, has been transfered to the
MRUF-lst-gtkrc.sh launcher script in /usr/bin.

-- The CleanMplayerHistory.sh script has been removed, this function
now being handled in the main script. (Please never forget to make
back-ups beforehand.)

-- Smaller code edits deriving from the above.

-- I added a lighter GTK2 theme, Finery, with which this version boots,
from url=https://www.gnome-look.org/p/1079653[/url]. The theme
illustrated there is FineryDark, but it has a light counterpart, Finery, in
the archive.

The previous dark theme, PeLo
url=https://www.gnome-look.org/p/1080034[/url], is still in the decor
archive, available to those who liked it.

(Sorry there is nothing doing with the https URLs today.)

This addition explains the larger decor archive. (Attached.)

-- You'll find screen shots of this version a couple of posts above,
illustrating use on the jwm, icewm and wmx window managers.

-- In addition to the attached, you will need the execs-32 file,
available here, or the execs-64 file, available here.

answer in forum francophone to Musher0 topic, french forum, with french Slaxen
The first versions were downloaded more 500 times, MRU has been improved a lot. Try it ! What i could help better ?_________________Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.

As requested by B.K. Johnson, here is a little script to check if you have
the utilities and version numbers required by MRUF-lst.

It's without any bling, but it will inform you.

Unzip in /root/my-applications/bin, make executable and run in console
by typing < Checks.sh > (without the chevrons).

No checks are done for the browsers: that, the user has to know already
if (s)he's reading this post.

IHTH.

~~~~~~~~~~~~

Code:

#!/bin/sh
# /root/my-applications/bin/Checks.sh
# (or other suitable "bin" directory)
#
# Checking if you have the requirementsfor MRUF-lst.
# Thanks to B.K. Johnson for pointing out this need.
#
# (c) musher0, 2017-08-17. GPL3.
####
clear
echo "
Checking for MRUF-lst requirements.
-----------------------------------
"
for i in sfs_load replaceit aemenu-pango bcm;do echo;which $i;echo;done
echo "
# If the file name is listed, you have the utility.
# Hit Return to continue."
read
clear
echo
ls -d /usr/local/apps/UExtract
echo "
# If the directory name is listed, you have the utility.
# Hit Return to continue."
read
clear
for i in bash file less;do echo;$i --version |head -n 3;done
echo "
# These utils show their version number.

# Bash has to be v. 4.2 or higher.
# less must NOT be the busybox one.
(It would say 'BusyBox' on the 1st line.)
# Lesser version numbers of less and file are ok.

# Hit Return to continue."
read
clear
urxvt -h
echo "# Urxvt has no parm. to list its version number. It is on the first
line above. It has to be v.9.2 or higher."
read
clear
echo "
That's it.
The check for the utilities required by MRUF-lst
is now complete.
"

I wrote the script above in leafpad, and it doesn't show up in the list of
scripts in the MRUF-lst. Why? Because leafpad doesn't have a history file,
and is not scanned by the recently-used.xbel "mechanism".

The same will be true for similar, simple, programs.

MRUF-lst doesn't and cannot check all activity on a computer. Nor would
I want it to.

It is simply a convenient (IMO) interface grouping in one place as many
program histories as possible (those who have one), so you don't have to
look here, there and everywhere in your directory hierarchy to find a file
you recently viewed or used or listened to.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum