{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibeddmtujdqxaluqnd2zwfar2udrnp2zo25cqo5bcnpcbxanefk7m",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mmrgjq3nglx2"
  },
  "path": "/viewtopic.php?t=33433&p=274727#p274727",
  "publishedAt": "2026-05-26T16:35:13.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Thanks. Problem solved. No bugs in either Epyrus or Pale Moon.\n> It has to do with the desktop, XFCE in my case.\n> There are menus (and corresponding .desktop files) from which PM is started/invoked.\n> Possibly more than one. One has to make sure that PM is invoked with argument %u\n> e.g. as \"/opt/palemoon/palemoon %u\".\n\nOhh... that actually makes sense. I know that in various shell scripts and maybe various menu configurations, you had to use a special character like that to indicate that you want whatever was typed after the initial argument. I think my issue was that when I would test it, I would point Epyrus directly at a compiled copy of the Pale Moon executable sitting in another directory that had no menu entry, and never imagined others were using OS/Desktop-level menu entries. That would explain it, I was never testing the fancier desktop integration stuff like having the OS know what Pale Moon and Epyrus are from menu entries and then making associations from those, I always hunted for the executable to make the association because I never had it in the normal menu system anyway.\n\nIt does explain why it would have been hard for me to find this bug. I just wasn't testing the same thing at all...\n\n* * *",
  "title": "Epyrus • Re: Get a link in a message to open in PM? (SOLVED)",
  "updatedAt": "2026-05-26T16:35:13.000Z"
}