Akete - FARR-specific file associations

Purpose

  FARR enables customization of the browser and/or file explorer used to "launch" URLs and files/folders respectively.  This plugin generalizes this idea for files based on filename extensions.  

  The original motivation for this plugin was to enable one to make use of and transport file associations without getting involved with the registry -- e.g. for portable application types of settings -- well, at least for files launched via FARR :)

Usage

  Basic Instructions

    To customize the handling for a specific file extension, first ensure that FARR's "Program Options -> Lists -> User Variables" setting has an [Akete] section.  

    Then create a line in that section of the form:

      <extension>=<executable-path>

    where <extension> stands for the (typically 3-letter) file extension in question and <executable-path> is an appropriate path to an appropriate executable.

    For example, to handle PDF files using SumatraPDF, one might use the following sort of text (assuming here that SumatraPDF.exe is the name of the executable and that it lives in D:\Apps\):

      [Akete]
      pdf=D:\Apps\SumatraPDF.exe

    If all goes well, FARR should now launch all files that end in '.pdf' using SumatraPDF. 

  Experimental Features

    openwith<something>

      Instead of a file extension (the <extension> part), specifying a string of the form openwith<something> (no angle brackets) configures Akete to recognize openwith<something> as a keyword.  For example, suppose the [Akete] section looks like:

        [Akete]
        openwithsumatra=D:\Apps\SumatraPDF.exe

      Subsequently, FARR should use D:\Apps\SumatraPDF.exe to open files specified in the FARR window if +openwithsumatra (i.e. FARR's keyword mechanism is used) is also specified.  One application of this idea is in making aliases for opening particular files with specific applications.

    multiple executable paths

      Instead of a single executable path (the <executable-path> part), specifying a |-separated (the vertical bar or pipe character) list of executable paths configures Akete to be prepared to augment a result's context menu with multiple options for opening the result in question.  An example [Akete] section is:

        [Akete]
        pdf=P:\Apps\SumatraPDFPortable\SumatraPDFPortable.exe|P:\Apps\PDFV_Portable\PDFXCview.exe

      Note that Akete will use the first executable path to handle ordinary launches (e.g. by pressing the Enter key after typing a string in the FARR window).

      If an empty string is specified as the first executable path (i.e. start the value with a | character), Akete will not attempt to handle launching for the given extension.  This allows the context menu augmentation to be configured without interfering with FARR's launching of files with a given extension.  An example [Akete] section is:

        [Akete]
        pdf=|P:\Apps\SumatraPDFPortable\SumatraPDFPortable.exe|P:\Apps\PDFV_Portable\PDFXCview.exe

    "file extension duplication" / "executable path reuse"
    
      Instead of an executable path (the <executable-path> part), specifying a file extension configures Akete to reuse the <executable-path> of the specified file extension (assuming there is one).  Only one level of indirection is supported.  An example [Akete] section where the extensions txt and doc share the same <executable-path> portion might be:
      
        [Akete]
        txt=C:\Windows\System32\notepad.exe
        doc=txt

    default paths for context menu

      Instead of a file extension (the <extension> part), specifying an asterisk character (*), and then specifying a multiple executable paths value for the <executable-path> part configures Akete to be prepared to augment a result's context menu with additional paths above and beyond what it would otherwise display.  This provides a list of "default" applications which are always listed in a result's context menu.  An example [Akete] section is:

        [Akete]
        *=C:\Windows\System32\notepad.exe|P:\emacs\bin\runemacs.exe|C:\Program Files\Windows NT\Accessories\wordpad.exe

Bugs

  Probably ;)

Credits

  Thanks go out to:

    mouser
    ecaradec
    phitsc
    Plugin authors that provided source and/or comments on the forums
    DC Forums participants
    DC Supporters

