How to show MRU Most Recently Used Documents on Start Menu?

[LazY Puppy]

Hmm, I did?

Can't remember.

Can you show me what you meant by 96 characters?

This is extremely abnormal and judging from your screenshot your start menu is heavily customized.

Yes, for the average user it is.

Though, it is not for me, as I'm heavily developing stuff and I want to have immediate access to all progs and files.

[musher0]

@all:

I have updated my first post in this script (3rd post on page 1) to inform the
potential user that development is on-going and that there is a much newer
MRUF script available.

For the record, I would also like to point out that OP "johnywhy" asked for
a possible integration of the MRUD's to "his Puppy menu". We readers may
infer that it is a jwm menu, but "johnywhy" did not specify the WM.

BFN

[MochiMoppel]

Hmm, I did?
Can't remember.

No need to remember anything, a look into your script is sufficient
File create-recently-used-jwm-submenu, starting line 63:

Code: Select all

# The following lines to translate UTF-8 XML code to regular accented characters; 
# you may comment these lines if you are using only English.
# Traduction du codage XML pour les accents. 
$R "%C2%A0" " " 
$R "%C2%A1" "¡"
$R "%C2%A2" "¢"
$R "%C2%A3" "£"
$R "%C2%A4" "¤"
$R "%C2%A5" "¥"
$R "%C2%A6" "¦"
$R "%C2%A7" "§"
$R "%C2%A8" "¨"
$R "%C2%A9" "©"
$R "%C2%AA" "ª"
$R "%C2%AB" "«"
$R "%C2%AC" "¬"
$R "%C2%AD" " " 
$R "%C2%/recently-used-files-array" "®"
$R "%C2%AF" "¯"
$R "%C2%B0" "°"
$R "%C2%B1" "±"
$R "%C2%B2" "²"
$R "%C2%B3" "³"
$R "%C2%B4" "´"
$R "%C2%B5" "µ"
$R "%C2%B6" "¶"
$R "%C2%B7" "·"
$R "%C2%B8" "¸"
$R "%C2%B9" "¹"
$R "%C2%BA" "º"
$R "%C2%BB" "»"
$R "%C2%BC" "¼"
$R "%C2%BD" "½"
$R "%C2%BE" "¾"
$R "%C2%BF" "¿"
$R "%C3%80" "À"
$R "%C3%81" "

[musher0]

Ahem.
That comes verbatim from my 2nd or 3rd version of the MRUF, I think...
RSH kept the comments in French, too! Typos and all! (hehe)
I'm flattered!

@Lazy Puppy:
At the time, I thought those foreign characters conversions were
necessary, but experience has proven that in fact they are not needed.

IHTH.

[musher0]

Hello all.

To hold my end of the bargain and convince people that this organic
discussion about building a MRUF/MRUD sub-menu in the start menu
IS in line with the question of the OP (q.v., BTW):

Lazy Puppy has his own way of doing things in his "T.O.P.L.E.S.S."
Puppy, I'm sure.
~~~~~~~~~~~~~~
Edit, late evening, Sept. 23 2016:
(Please see his posts above.)

As well, MochiMoppei is now offering another option for integrating
a MRUF sub-menu to jwm >= v.2.3.
~~~~~~~~~~~~~~

But here's how to integrate my MRUF script into jwm's menu:

• Open a terminal
  Open the jwm menu template by typing:

  Code: Select all

  geany /etc/xdg/templates/_root_.jwmrc &

  Search for the entry "Help"; there is a "separator" right over it.
  Make a line space between the separator and the "Help" entry.
  In this new space, on this new line, copy and paste this line:

  Code: Select all

  <Program label="M.R.U.F." icon="/usr/local/share/pixmaps/mrudicon2-48x-trnsprnt.png">exec /usr/local/bin/MRUF-lst-0.9.5.4.sh</Program>

  Save the document.
  Exit geany
  
  You're still in terminal, so type

  Code: Select all

  fixmenus;jwm -restart

When the update is finished, right-click on any empty part of the screen,
and you should now see the MRUF sub-menu entry just above the Help
entry (see attached picture).

Done. IHTH

[musher0]

To integrate my MRUF script in the wmx menu,

• open a terminal
  type

  Code: Select all

  rox ~/.wmx /usr/local/bin

  drag the script MRUF-lst-0.9.5.4.sh from the /usr/local/bin directory
  to the /root/.wmx directory as an absolute link. (See attached picture.)

That's it.

Middle-click and you can now see the new MRUF entry in the wmx menu.
(Please see 2nd picture.)

BFN.

[musher0]

To incorporate the MRUF script in the icewm menu:

• open a terminal
  type

  Code: Select all

  geany /etc/xdg/templates/_root_.icewm_menu

  Go to the "Help" line; there's a separator above it.
  Create a line space between those two lines.
  In that line space, copy and paste the following line:

  Code: Select all

  prog "M.R.U.D" "/usr/local/share/pixmaps/mrudicon2-48x.png" MRUF-lst

  Save.
  Exit geany.

You're still in terminal, so type

Code: Select all

restartwm

icewm recycles and you're done.

IHTH

[LazY Puppy]

Ahem.
That comes verbatim from my 2nd or 3rd version of the MRUF, I think...
RSH kept the comments in French, too! Typos and all! (hehe)
I'm flattered!

No, I don't think so.

The original file I copied the shown section from is locally existing at least from the middle of 2014. I had this already built into L.A.S.S.I.E. 003, which I never published as I started T.O.P.L.E.S.S. before finishing L.A.S.S.I.E. 003.

And again: no, I did NOT change anything on that part of the original file.

Sorry, I can't remember correctly, though L.A.S.S.I.E. 002 was published at April 02 2014. Right after that I started development of L.A.S.S.I.E. 003 and began to include my menu pipes from openbox ready made for JWM. So I think I have its original file at least since the middle of 2014.

And yes, I kept the comments and the typos, as I was informed once by PM about some bashing of my person in my back by others using PM's, because I'd removed some comments sometimes from some code parts using in my earlier scripts and developments. There was also some bashing in may back when I changed my user name to LazY Puppy, as most people just did not notice, it's still just me: RSH.

Edit:

Sorry, found out right now, musher0 has made his first post in this here topic at Thu 11 Oct 2012. So, it could be possible that the original file was indeed from musher0! I just wasn't aware of this date.

And a few posts below that post from musher0 there is stu91 (which is originally stu90, mentioning und using the term menu pipe (openbox). Funny!

[Semme]

Hey, I'm starting a JohnyWhy hate club. Who's in? :mrgreen:

[musher0]

Ahem.
That comes verbatim from my 2nd or 3rd version of the MRUF, I think...
RSH kept the comments in French, too! Typos and all! (hehe)
I'm flattered!

No, I don't think so.

The original file I copied the shown section from is locally existing at least from the middle of 2014. I had this already built into L.A.S.S.I.E. 003, which I never published as I started T.O.P.L.E.S.S. before finishing L.A.S.S.I.E. 003.

And again: no, I did NOT change anything on that part of the original file.

Sorry, I can't remember correctly, though L.A.S.S.I.E. 002 was published at April 02 2014. Right after that I started development of L.A.S.S.I.E. 003 and began to include my menu pipes from openbox ready made for JWM. So I think I have its original file at least since the middle of 2014.

And yes, I kept the comments and the typos, as I was informed once by PM about some bashing of my person in my back by others using PM's, because I'd removed some comments sometimes from some code parts using in my earlier scripts and developments. There was also some bashing in may back when I changed my user name to LazY Puppy, as most people just did not notice, it's still just me: RSH.

Edit:

Sorry, found out right now, musher0 has made his first post in this here topic at Thu 11 Oct 2012. So, it could be possible that the original file was indeed from musher0! I just wasn't aware of this date.

And a few posts below that post from musher0 there is stu91 (which is originally stu90, mentioning und using the term menu pipe (openbox). Funny!

Please see here? (4 Nov. 2012) I had previously taken it from this site.

It does not matter to me anyway, this material is General Public Licence.
It's meant to be incorporated in apple or raspberry pies, eaten with
spaghettis, sprinkled on salads, dissolved in couscous or rice, etc., etc.

My point is: later I discovered that those conversions were unnecessary.

BFN.

[LazY Puppy]

Code: Select all

files=$( tac "${file_path}" |  awk -v MAX="$maximum_entries" -v PR="$pre" -v MI="$mid" -v PO="$post" 'BEGIN {
    RS="</bookmark>";
    FS="<info>";
}
(NR == MAX) {exit}
!/<bookmark/ {next}
!/href=[\"'\'']file:\/\// {next}
# $1 is the command, $2 the file path
{
    sub(/^.*exec=\"\&apos\;/,"",$1)
    sub(/\&apos\;.*$/,"",$1)
    sub(/ *%./,"",$1)
    sub(/^.*file:\/\//,"",$2)
    sub(/[\"'\''].*$/,"",$2)
    gsub(/%22/,"\\"",$2)
    gsub(/%3C/,"\\<",$2)
    gsub(/%3E/,"\\>",$2)
    name=$2
    sub(/^.*\//,"",name)
    gsub(/_/,"__",name)
    gsub(/\&apos;/,"\\&apos;\\"\\&apos;\\"\\&apos;",$2)
    print (PR name MI $1 " '"'"'" $2 "'"'"'" PO)
}' )

# use perl to decode urlencoded characters
files=$(perl -MURI::Escape -e 'print uri_unescape($ARGV[0]);' "$files")

This is how it is done in the script posted by stu90/91. Original author is: Copyright (C) 2010 John Crawley.

From looking at the post you linked and the posts below, it seems I added at least those lines that has the recently-used* in it. Sure, there was a reason to do so, though I can't recall.

[musher0]

Perhaps you need an xbel file for your reasons!!!
(We would all need one!)

[musher0]

Hello all.

I just edited my post above concerning integration of a MRUF script
to jwm in light of Mochi Moppei offering a new way to achieve it.

Best regards.

[musher0]

Hello people.

We now have the needed executables (attached) to build a 64-bit MRUF-lst
in a perhaps not so-distant future.

Many thanks to:
-- RSH/Lazy Puppy for compiling aemenu-pango-64 and replaceit-64;
-- Peter van Eerten, of BaCon fame (via vovchik), for compiling bcm-tahr-64.

BFN.

[musher0]

Hello all.

Here is version 0.9.5.5, for 32-bit Puppies. Same caveats as for
previous version. (The part in bold, here.)

Changes:
-- The script now detects changes in size for itself (useful in development)
and for the 'xbel' file. It then updates automatically when you call it from
terminal or click on the icon. The manual update entry line is still in the
menu, if you wish to use it.

I thought it would be a good compromise between freshness of menu and
frustration of the user. In other words, this menu now refreshes when it
needs to, no more, no less.

-- the xdg-open and defaulthandler files have been re-edited in view of
certain problems reported at boot-up under jwm. (I never had this
problem using the wmx WM, which is my default WM.)

If you have problems with that, 1) un-install my script and 2) use the two
one-liners below to restore pristine xdg-open and defaulthandler files.

Code: Select all

cp -f /initrd/pup_ro2/usr/local/bin/xdg-open /usr/local/bin/xdg-open
cp -f /initrd/pup_ro2/usr/local/bin/defaulthandler /usr/local/bin/defaulthandler

If you still have problems with the *.desktop files loading in jwm, please
try using this corrective script for the autostart directory. If that does not
cure the behavior, look elsewhere; your Puppy system may have some
other problem: system-wise, this MRUF script provides customized,
improved (IMO), xdg-open and defaulthandler files, and that's it.

-- History access has been added for:
--- gmplayer and sqlite (if you have them on your Puppy system) and
--- the "noX" terminal (history for the initial black console)

-- The menu entry marked "1st prompt" in the "Bash & System" sub-
menu will bring you there (it's convenient if you need it, I think).

-- On the subject of media players:
--- I had no luck testing with norgo's latest smplayer pet;
--- Another test with vlc went fine. I felt that vlc didn't need a menu entry,
though, since its history is correctly recorded in the 'xbel' file. One can
recall the music pieces played in vlc from the 'xbel' general files menu.

-- Geany, gmplayer and mtpaint now grouped under their own "Apps"
sub-menu instead of appearing at 1st level.

Finally, a reminder of this script's famous "accordeon feature": if you
don't have one of the above applications, its sub-menu won't show.

Any constructive comments welcome. That's all for now. TWYL.

[B.K. Johnson]

This was written before musher0's last post which I had the opportunity to barely glance at. I don't know the extent to which that post impacts what I say here or vice versa. But my remarks stand.

There are some software developers who think shouting to the world: there is nothing wrong with my script absolves them of all responsibility. But every sane, non-irrational developer knows the correct code is not everything. There is the environment in which your software runs - software and hardware. That is why M$ spends so much time, energy and money testing software with a multitude of hardware, and testing that their software runs co-operatively with other programs in the system ecology.

I directed musher0 to a problem in my tahrpup system, where *.desktop files were being loaded into leafpad at startup. He was less than kind, and arrogant after he presumably read it. Now we have the incongruity of him offering a solution to a problem that has no relation to his software; he is just being helpful. His software runs ok with WM and he boasts:

WM (sic wmx) doesn't need this solution since it doesn't have the problem.

and

Other WM's may not need it.

and acknowledges that the solution he proffers is for jwm systems only. This clearly shows that his testing was confined to wmx; he was unconcerned about the behaviour of his software in puppies that do not use wmx.

And when I report that I have problems with tahr-605 on which he hasn't tested his software, he cries out it's not my software. # Goal: Solve the problem of *.desktop files in /root/.config/autostart
# loading as text in the text viewer under jwm.

Is he now painfully aware of his responsibility as a developer? Does he have any regrets about his smug, condesending and supersilious behaviour (I am repeating myself aren't I). I don't think so. Just look at how he chooses to introduce the offer -"FWIW".

I am not badgering you, so don't like a little boy run to "papa" to have me banned. You were blind to the issue raised in your thread. Perhaps you'll see this one. It is a serious issue.

So musher0 has provided a work-around kludge. We still do not yet know (at this writing) why the *.desktop files were opened in leafpad. Clearly, wmx and jwm handle *.desktop files differently. Barry's defaulthandler which you tossed may have been needed. We know from experience how jwm handles them. We don't even know if wmx does. But notice the arrogance. jwm has been puppy's default window manager for a long, long time and is likely used in many systems. Instead of fixing his software to work with the standard window manager, his application must remain untouched, the window manager he uses must remain but the standard window manager in the majority of puppies must be modified. How gratuitous (tongue firmly planted in my cheek). Or is it a "face-saving" action. wmx is an old, (2014) window manager, considered "experimental" by the author and not actively developed. If you want to experiment with something from way out in left field, go ahead. But don't foist it on the community like this.

[musher0]

This was written before musher0's last post which I had the opportunity to barely glance at. I don't know the extent to which that post impacts what I say here or vice versa. But my remarks stand.

There are some software developers who think shouting to the world: there is nothing wrong with my script absolves them of all responsibility. But every sane, non-irrational developer knows the correct code is not everything. There is the environment in which your software runs - software and hardware. That is why M$ spends so much time, energy and money testing software with a multitude of hardware, and testing that their software runs co-operatively with other programs in the system ecology.

I directed musher0 to a problem in my tahrpup system, where *.desktop files were being loaded into leafpad at startup. He was less than kind, and arrogant after he presumably read it. Now we have the incongruity of him offering a solution to a problem that has no relation to his software; he is just being helpful. His software runs ok with WM and he boasts:

WM (sic wmx) doesn't need this solution since it doesn't have the problem.

and

Other WM's may not need it.

and acknowledges that the solution he proffers is for jwm systems only. This clearly shows that his testing was confined to wmx; he was unconcerned about the behaviour of his software in puppies that do not use wmx.

And when I report that I have problems with tahr-605 on which he hasn't tested his software, he cries out it's not my software. # Goal: Solve the problem of *.desktop files in /root/.config/autostart
# loading as text in the text viewer under jwm.

Is he now painfully aware of his responsibility as a developer? Does he have any regrets about his smug, condesending and supersilious behaviour (I am repeating myself aren't I). I don't think so. Just look at how he chooses to introduce the offer -"FWIW".

I am not badgering you, so don't like a little boy run to "papa" to have me banned. You were blind to the issue raised in your thread. Perhaps you'll see this one. It is a serious issue.

So musher0 has provided a work-around kludge. We still do not yet know (at this writing) why the *.desktop files were opened in leafpad. Clearly, wmx and jwm handle *.desktop files differently. Barry's defaulthandler which you tossed may have been needed. We know from experience how jwm handles them. We don't even know if wmx does. But notice the arrogance. jwm has been puppy's default window manager for a long, long time and is likely used in many systems. Instead of fixing his software to work with the standard window manager, his application must remain untouched, the window manager he uses must remain but the standard window manager in the majority of puppies must be modified. How gratuitous (tongue firmly planted in my cheek). Or is it a "face-saving" action. wmx is an old, (2014) window manager, considered "experimental" by the author and not actively developed. If you want to experiment with something from way out in left field, go ahead. But don't foist it on the community like this.

BKJ?

I apologize for any inconvenience caused by a previous version of my
script that sent *.desktop files to leafpad instead of running them. On my
set up, believe me or not, only the script did that, not my window
manager (abbreviation: WM) on boot-up. I had done that, as mentioned
in the script, "to play it safe".

Some facts:
-- you say the cause is unknown but Mochi Moppei has seen it and tried to
explain it to you ḩere

-- the wmx window manager has been around since 1999 and is now at
version 8 (published in 2014). It is far from experimental;

-- any tester must use due diligence;

-- a developer is free to create any script on any Puppy base;

-- it is impossible for a Puppy developer to test his script on all Puppies,
because there are literally dozens of Puppy Linux variants. Furthermore,
not all Puppies work on all hardware.

If you weren't seeing red so much, you'd see the facts as they are.

For the rest, you can think of me personally what you want -- just stay
away from slander.

Best regards.

[B.K. Johnson]

musher0 wrote:

I apologize for any inconvenience caused by a previous version of my
script that sent *.desktop files to leafpad instead of running them.

You are apologising for the wrong thing, for it is acknowledged that software will have bugs. But finally, an acknowledgement of sorts. I leave you to figure out what the right thing is.

On my
set up, believe me or not, only the script did that, not my window
manager (abbreviation: WM) on boot-up. I had done that, as mentioned
in the script, "to play it safe".

Huh! "only the script did that" Is it not the script, the assertion that it is perfect, that I should not blame it for my experience and that I should go find other reasons for my woes, the basis of these posts between us? And was it not in your modification of a script (xdg-open) that the error was found? The WM is a side issue that emerged because of your declared hatred for jwm, your refusal to test your applet in a jwm environment and offering a special gratuitous fix for jwm users to obscure the real issue.

Could you please desist from calling your window manager WM? Don't take ownership of your window manager by giving it a name that's different from that given by the authors. Use WM for the generic. Your WM is either wm2 or wmx. I suppose it would be ok to use a redundant wmx WM, but why?

-- you say the cause is unknown but Mochi Moppei has seen it and tried to
explain it to you ḩere

Mochi's post was on Sept 21. If you thought that was the solution, why did you 2 days later offer solve-autostart.sh. Hmm! He gave a solution he thought would/should work, not an explanation. As I responded to MM, gxmessage did not work for me. So it was not solved; the cause was still unknown. I don't consider myself a coder, but I know that almost none of the .desktop files have MIME settings. Therefore, I was unsure of that line. My recent post in the icons missing thread tells what is wrong and required to restore my tahr-6.0.5 tray icons.

-- the wmx window manager has been around since 1999 and is now at
version 8 (published in 2014). It is far from experimental;

wm2 started in 1996. wmx came later as an add-on feature set. Neither start date nor 8th issue means it's not experimental. But I was not rendering a personal opinion when I wrote that. This is taken from the wmx website:

wmx is a window manager for X. It's based on wm2, and it retains a similar look and feel, but it's intended to provide an experimental vehicle for features that fall comfortably outside the scope of the manifesto for the original wm2.

Download the current (eighth) source release.

I have enbolden experimental. Why do you bring up these side issues? You appear to be a one-man band playing with wm2/wmx.

-- any tester must use due diligence;

Why keep harping on this. That is not the issue for I did not complain. I brought an observation to your attention. But you are so defensive with your software that you barely read it. It took you less than 2 minutes to read, understand and respond to my post - from the time mine was sent until you sent your reply. Response to the second also took under 2 mins. Dare I say, not sufficient time to fully comprehend. Sadly, it shows.

-- a developer is free to create any script on any Puppy base;

So, why tell me this? Where did I infer that I wanted to prevent you from doing anything? As I wrote to someone recently: Stop setting up strawmen.

The so-called typical "attacking a straw man" argument creates the illusion of having completely refuted or defeated an opponent's proposition by covertly replacing it with a different proposition (i.e. "stand up a straw man") and then refuting that false argument ("knock down a straw man") instead of the original ...

You are clutching at straws.
A drowning man will clutch at a straw.
Prov. When you are desperate, you will look for anything that might help you, even if it cannot help you very much.

-- it is impossible for a Puppy developer to test his script on all Puppies,
because there are literally dozens of Puppy Linux variants. Furthermore,
not all Puppies work on all hardware.

Well, there is one we can agree on. But that is what I have been saying, but obviously, your reading/understanding betrays you. And if you believe what you say, then (1) you should expect bug reports (2) you should be amenable to accepting them and (3) be anxious to help the user collaboratively solve the problem. Instead, you respond with diatribes like:

Anything else you want to blame my script with?

It seems that 2016 will be a bad year for apple cider in Canada.
Please blame my script for that too.

If you weren't seeing red so much, you'd see the facts as they are.

Speak for yourself. Samples:

If you try
to take advantage of me or to prove me a lesser person

-- if you feel that my script is the source of
all woes in your computer life at present:

What facts? The ones I just refuted? As RSH would say:NONSENSE! NONSENSE! NONSENSE!
If there is anyone with reason to see red, it is you. Loss of confidence. Diminution of esteem by the community. So red, that you had to get a community member (I think unwarranted) suspended and then gloat about it; so red that you literally begged to receive some attribution for MochiMoppel's most-recently-used when there was none. Me, I had nothing to be angry about. My system was working with a little inconvenience of closing pages and manually installing the tray apps 2/3 times a day. In fact, I have been laughing ever since your response to my first post, seeing you going through contortions to extricate yourself from responsibility.

I want to stop laughing now. No matter what you say now would be new and worthy of a response. So consider this my last hurrah. I have purged MRUF_lst from my system. I have no intent to use any version of it. I am outta here and won't be back.

[musher0]

@BKJ

GPL3 contains this:[quote]15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE
THE PROGRAM “AS IS

[mfb]

To all,

To read the truth, the whole truth and nothing but the truth, as it relates to ASD, download the file here:
http://murga-linux.com/puppy/viewtopic. ... 863#924863
With his well known charm, musher0 should follow his own recent advice and put that in his pipe and smoke it.

More than half a century ago Lord Chief Justice Goddard said, by way of obiter dictum in a U.K. case,
"it is more important that the law be certain than it be just"; yet at times it is neither certain nor just.

As regards the other matter, I score it B.K. Johnson 100 and musher 0.