Link Hints Extensions? Topic is solved

[fatboy]

Good Day folks,

For a year or so have I been using Pentadactyl, tweaking away and going crazy with keybindings. However, I am trying a new approach lately where I use the normal browser interface + Dorando Keyconfig Extension and it's working wonderfully. However, there is one feature from pentadactyl and tridactyl (on Firefox) I am missing most, and that is the ability to press f for follow, and have all the links light up with hint keys.

I came across this on the firefox addons store and was wondering if there is an old version somewhere, or an alternative that I could install?
https://addons.mozilla.org/en-US/firefo ... /versions/

Thank You

[Kris_88]

Maybe Vimfx.
https://web.archive.org/web/20181018010 ... on-history

[fatboy]

Thanks for the suggestion, I downloaded it and it installed on Palemoon. However, the old version I installed does not have the follow/hint function

[fatboy]

Vimperator seems to work on Palemoon and Basilisk, nice! It feels lighter and faster than pentadactyl
https://github.com/vimperator/vimperator-labs

Now I just need to figure out how to get it to work on Sealion.

[fatboy]

Even though vimperator works on Pale Moon and Basilisk, it's quite buggy. It doesn't read it's config file on linux ~/.vimperatorrc and also doesn't read themes placed in ~/.vimperator/colors/theme_name.vimp, ugh.
It also doesn't save settings set in browser to a file, so after a restart you are back at square one again

[deChat]

Thanks for the suggestion, I downloaded it and it installed on Palemoon. However, the old version I installed does not have the follow/hint function

If you mean the version suggested by Kris_88 (vimfx-0.20.15-fx.xpi), it actually has the follow/hint function, but it's not compatible with v32.4.0 of Pale Moon.

I use a much earlier version (vimfx-0.5.17-fx.xpi) obtained via CAA, but I added the following lines to the install.rdf file (just above the targetApplication lines for Firefox:

Code: Select all

    <em:targetApplication><!-- Pale Moon -->
        <Description>
            <em:id>{8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}</em:id>
            <em:minVersion>31.0</em:minVersion>
            <em:maxVersion>33.*</em:maxVersion>
            </Description>
    </em:targetApplication>

This version of VimFx doesn't have the full panoply of features that later versions do, but it has the important ones. Combined with the built-in keyboard shortcuts and a bit of Dorando tweaking, I have over 90% of what I want for complete keyboard-centric browsing with Pale Moon. Getting that last ~10% seems like it might be a bear, though.

[fatboy]

If you mean the version suggested by Kris_88 (vimfx-0.20.15-fx.xpi), it actually has the follow/hint function, but it's not compatible with v32.4.0 of Pale Moon.

I use a much earlier version (vimfx-0.5.17-fx.xpi) obtained via CAA, but I added the following lines to the install.rdf file (just above the targetApplication lines for Firefox:

Code: Select all

    <em:targetApplication><!-- Pale Moon -->
        <Description>
            <em:id>{8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}</em:id>
            <em:minVersion>31.0</em:minVersion>
            <em:maxVersion>33.*</em:maxVersion>
            </Description>
    </em:targetApplication>

This version of VimFx doesn't have the full panoply of features that later versions do, but it has the important ones. Combined with the built-in keyboard shortcuts and a bit of Dorando tweaking, I have over 90% of what I want for complete keyboard-centric browsing with Pale Moon. Getting that last ~10% seems like it might be a bear, though.

Oh wow, that is cool, thanks for the suggestion. Do you compile vimfx yourself? Where do I find the rdf file for an installed xpi file?
I have tweaked my dorando keyconfig a lot recently, and the only thing I need now is only the follow hint functionality haha. Is there a way to get vimfx to do only that?

[deChat]

Do you compile vimfx yourself?

Nooooo.... I downloaded the version I mentioned from caa:addon/vimfx/versions (after installing the Classic Add-ons Archive extension)

Where do I find the rdf file for an installed xpi file?

The install.rdf file is inside the .xpi file. You download the .xpi to your local disk, then open it with an application like 7-zip. In 7-zip, you can edit the install.rdf file by right-clicking on it and then selecting "Edit" After you add the lines for Pale Moon (which are in my earlier post), you close the edit window and click "Yes" to update the install.rdf file inside the .xpi file.

I have tweaked my dorando keyconfig a lot recently, and the only thing I need now is only the follow hint functionality haha. Is there a way to get vimfx to do only that?

Yes, but tbh it's probably better to find another old Firefox extension that just provides follow hint functionality (and edit its install.rdf file) vs. using VimFx, since the version I suggested adds ~50 keyboard shortcuts (and thus has the memory overhead to support those shortcuts).

However, it IS possible to remove or change those VimFx shortcuts, if you want. You do this by using the "?" shortcut to show all of the possible VimFx shortcuts, and selecting those that you want to change or delete.

[deChat]

@fatboy: I forgot to mention another built-in alternative to link hints that I discovered recently. It doesn't require the installation of any extensions because it's already part of the Pale Moon (and Firefox) code.

The keyboard shortcut ' (single quotation mark) brings up a "Quick find (links only)" dialog bar that allows you to search for links on the current page. You can type in the characters that correspond to the link you want to open, and then press the ENTER key to open the link. That might work out better for you in certain cases vs. using VimFx or a similar extension. (Personally, I use whichever is most convenient depending on the situation and the webpage I'm on.)

[moonbat]

Why are you using monstrously huge fonts in your reply?

[fatboy]

@fatboy: I forgot to mention another built-in alternative to link hints that I discovered recently. It doesn't require the installation of any extensions because it's already part of the Pale Moon (and Firefox) code.

The keyboard shortcut ' (single quotation mark) brings up a "Quick find (links only)" dialog bar that allows you to search for links on the current page. You can type in the characters that correspond to the link you want to open, and then press the ENTER key to open the link. That might work out better for you in certain cases vs. using VimFx or a similar extension. (Personally, I use whichever is most convenient depending on the situation and the webpage I'm on.)

Hi deChat, thank you for the suggestions.

I am trying to replicate what you did with your rdf file, but with a newer version 0.20.15, the latest version found in CAA.
The extension is installed, but the 'f' binding isn't working?

Here is my install.rdf file:

Code: Select all

<?xml version="1.0" encoding="utf-8"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:em="http://www.mozilla.org/2004/em-rdf#">

  <Description about="urn:mozilla:install-manifest">
    <em:name>VimFx</em:name>
    <em:id>VimFx@akhodakivskiy.github.com</em:id>
    <em:homepageURL>https://github.com/akhodakivskiy/VimFx</em:homepageURL>
    <em:version>0.20.15</em:version>
    <em:bootstrap>true</em:bootstrap>
    <em:multiprocessCompatible>true</em:multiprocessCompatible>
    <em:type>2</em:type>

    <em:targetApplication><!-- Pale Moon -->
        <Description>
            <em:id>{8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}</em:id>
            <em:minVersion>31.0</em:minVersion>
            <em:maxVersion>33.*</em:maxVersion>
            </Description>
    </em:targetApplication>

    <!-- Firefox -->
    <em:targetApplication>
      <Description>
        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
        <em:minVersion>45.0</em:minVersion>
        <em:maxVersion>*</em:maxVersion>
      </Description>
    </em:targetApplication>

    <em:description>Vim keyboard shortcuts for Firefox</em:description>

    <em:creator>Anton Khodakivskiy (@akhodakivskiy)</em:creator>

    <em:developer>Simon Lydell (@lydell)</em:developer>

    <em:contributor>Wang Zhuochun (@zhuochun)</em:contributor>
    <em:contributor>Alan Wu (@XrXr)</em:contributor>
    <em:contributor>Heidi Xu – icon design</em:contributor>

    <em:translator>Frank Hase (@Kambfhase) – de</em:translator>
    <em:translator>Benedikt (@benediktg) – de</em:translator>
    <em:translator>@just-barcodes – de</em:translator>
    <em:translator>@interleaved – de</em:translator>
    <em:translator>@strel – es</em:translator>
    <em:translator>Mickaël RAYBAUD-ROIG (@m-r-r) – fr</em:translator>
    <em:translator>Yoppy Halilintar (@comepradz) – id</em:translator>
    <em:translator>Carlo Bertoldi (@cbertoldi) – it</em:translator>
    <em:translator>Kaoru Esashika (@pluser) – ja</em:translator>
    <em:translator>@HJTP – nl</em:translator>
    <em:translator>Átila Camurça Alves (@atilacamurca) – pt-BR</em:translator>
    <em:translator>Anton Khodakivskiy (@akhodakivskiy) – ru</em:translator>
    <em:translator>Nicholas Guriev (@mymedia2) – ru</em:translator>
    <em:translator>Zakhar Pilipchuk (@harius) – ru</em:translator>
    <em:translator>Andreas Lindhé (@lindhe) – sv-SE</em:translator>
    <em:translator>Simon Lydell (@lydell) – sv-SE</em:translator>
    <em:translator>Wang Zhuochun (@zhuochun) – zh-CN</em:translator>
    <em:translator>@mozillazg – zh-CN</em:translator>
    <em:translator>@av2000ii – zh-CN</em:translator>
    <em:translator>Robert Wang (@cyberrob) – zh-TW</em:translator>
    <em:translator>Salas (@leVirve) – zh-TW</em:translator>

    <em:localized>
      <Description>
        <em:locale>de</em:locale>
        <em:description>Vim Tastenbefehle für Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>es</em:locale>
        <em:description>Atajos de teclado de Vim para Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>fr</em:locale>
        <em:description>Utiliser les raccourcis clavier de Vim dans Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>id</em:locale>
        <em:description>Shortcut keyboard Vim untuk Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>it</em:locale>
        <em:description>Comandi Vim per Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>ja</em:locale>
        <em:description>Vimキーボードショートカット for Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>nl</em:locale>
        <em:description>Vim sneltoetsen voor Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>pt-BR</em:locale>
        <em:description>Atalhos do Vim para o Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>ru</em:locale>
        <em:description>Горячие клавиши в стиле Vim</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>sv-SE</em:locale>
        <em:description>Vim tangentbordskommandon för Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>zh-CN</em:locale>
        <em:description>使用 VIM 快捷键操控 Firefox</em:description>
      </Description>
    </em:localized>
    <em:localized>
      <Description>
        <em:locale>zh-TW</em:locale>
        <em:description>使用 VIM 快速鍵操作 Firefox</em:description>
      </Description>
    </em:localized>

  </Description>
</RDF>

[Moonchild]

Why are you using monstrously huge fonts in your reply?

Because they clearly haven't read the forum rules or choose to not adhere to them, and don't apply common sense.

app.php/rules#rule-1e

[deChat]

Why are you using monstrously huge fonts in your reply?

Because they clearly haven't read the forum rules or choose to not adhere to them, and don't apply common sense.

app.php/rules#rule-1e

My apologies. I set the fonts to "Large" to compensate for my weak eyes (which helps me proofread the preview), but you're right, I should not use them in my actual post per the forum rules. Sorry.

[deChat]

I am trying to replicate what you did with your rdf file, but with a newer version 0.20.15, the latest version found in CAA.
The extension is installed, but the 'f' binding isn't working?

As I posted in my first reply to this thread (viewtopic.php?f=46&t=30278&p=243522#p243383), vimfx-0.20.15-fx.xpi (version 0.20.15) is NOT compatible with v32.4.0 of Pale Moon. Modifying the install.rdf file won't fix that incompatibility.

In many cases, the latest version of an extension in the CAA won't work, because the version of Firefox targeted by that extension version is too different from the version of Pale Moon that you want to use it with. In such cases, I try the earlier archived versions, but it becomes a matter of trial and error and there are no guarantees that the legacy extension will work as intended or that there will be no problems when using it on Pale Moon. It's completely a "use-at-your-own-risk" situation.

The version of VimFx I suggested (version 0.5.17) does work with v32.4.0.1 of PM and has the 'f' binding for link hints. You might even want to use the earliest version that has that feature (or an even simpler/smaller extension), since you posted that you only need the link hints feature and version 0.5.17 has many additional shortcut keybindings that might conflict with what you've set up in Dorando.

[fatboy]

Oooh, now I understand, I thought you meant the newer versions will only work if you add that piece of code.

I am on Linux and am having issues editing the xpi file, the reason is, I would open the xpi file in xarchiver, then open the install.rdf file with my text editor, but then it would be saved to the /tmp directory.
I then tried extracting the xpi, editing the rdf file, then zipping it again, but no luck.

[jars_]

Maybe this Hit-a-Hint
"Space" for hints, you can customize the set of letters and numbers, as well as correct the appearance via css.

[moonbat]

I then tried extracting the xpi, editing the rdf file, then zipping it again, but no luck.

You must've made the mistake of including the top level folder containing your extracted files in the zip/xpi. If you extracted your files into 'folder/' then be sure to go inside the folder and then adding all files to the zip. So when you open the zip after creating it, the first thing you see must be install.rdf, chrome.manifest and all those files, not the folder above that contains them.

[deChat]

I am on Linux and am having issues editing the xpi file, the reason is, I would open the xpi file in xarchiver, then open the install.rdf file with my text editor, but then it would be saved to the /tmp directory.
I then tried extracting the xpi, editing the rdf file, then zipping it again, but no luck.

As moonbat mentioned, you have to be careful not to change the folder/directory structure of the .xpi archive.

The simplest way for me to modify the install.rdf file without screwing things up is to open the archive in Windows with 7-zip, then right-click on the install.rdf file and select Edit from the context menu. When I'm done editing and close the editing application, I get a prompt asking me if I want to save the changes to the archive, which I agree to.

afaik, there is no official GUI version of 7-Zip for Linux with which you can do what I do in Windows. But I bet there are GUI versions of other archive utilities in Linux that can be used in the way I use 7-Zip in Windows, to edit the install.rdf file without risking messing up the .xpi archive.

[Raava]

I am on Linux and am having issues editing the xpi file, the reason is, I would open the xpi file in xarchiver, then open the install.rdf file with my text editor, but then it would be saved to the /tmp directory.
I then tried extracting the xpi, editing the rdf file, then zipping it again, but no luck.

Here is the article on "Editing an add-on to change its compatibility" on kb.mozillazine.org: http://kb.mozillazine.org/Editing_an_ad ... patibility

Like deChat and moonbat already mentioned, you have to make sure the folder structure of your updated zip file is the same than the original.

On Linux, I recommend this:

Extract the whole xpi telling the extracting program to conserve the existing folder structure
Edit the install.rdf
Compress the folder into a zip conserving the folder structure and rename that zip into e.g. my_updated_extention-name.xpi when the original is called extention-name.xpi

Use a terminal program to verbosely list the contents of the original xpi and your updated xpi.

Alternatively, extract the original xpi into a different folder telling your program that extracts the xpi to extract the folder structure as well, e.g. into /other/folder/extention-name/

Extract your updated extension the same way (extracting the folder structure as well) into /other/folder/my_updated_extention-name/


compare the file and folder hierarchies in /other/folder/extention-name/ and /other/folder/my_updated_extention-name/


Both need to be the same aside from a different install.rdf


If the folder structures differ between the two folders, try again, you must have made a mistake somewhere.


HTH

[fatboy]

Thank you all for the input.

So I downloaded 0.5.17 from the CAA repo, extracted the XPI file, edited the install.rdf file, compressed it again in the same order as it extracted. The compression into the new xpi file succeeded, it also installs for Pale Moon. However, the extension is not working as it should? I press "f" and nothing happens?