Skip to content

Associate file extensions #302

Closed
Closed

Description

@gdementen

I just tested associating a few file extensions with the editor. This mostly works and, contrary to what I thought, WITHOUT admin priviledges. There are a few oddities that I need to investigate whether they are issues with pixi or with the original menuinst code that conda uses (AFAICT, pixi uses rattler_menuinst which is just a port of menuinst to rust, so I suppose the behavior should be the same -- unsure what code (micro)mamba uses or wether they support menus/file association).

  • the icon is the "generic executable" one, not the one specified. A pity but not a blocker. Edit: This was specific to pixi and is fixed for their next release.
  • the files type appear in File Explorer as .<ext> LArray Editor.AssocFile.<ext> file which is quite strange/ugly/confusing but not a blocker. Edit: fixed in Pixi for their next release (I must still report it to menuinst)
  • running the editor with (a) file(s) as argument should open the File Explorer instead of loading them (because that's faster and we support a lot more formats that way): Open File Explorer for file(s) passed as command-line argument(s) #303
  • we should only associate files for which our users probably do not have a viewer installed: .h5, .hdf, .feather, .ipc, .arrow, .parquet, .ddb, .duckdb

Activity

  1. added this to the 0.36 milestone on Feb 2, 2026
  2. gdementen commented on Mar 10, 2026

    @gdementen
    CollaboratorAuthor

    requires #306

  3. modified the milestones: 0.36, 0.35.1 on Mar 20, 2026
  4. gdementen commented on Mar 20, 2026

    @gdementen
    CollaboratorAuthor

    I couldn't resist including this in the 0.35.1 milestone even if that's supposed to be a bug fix release because it seems to me like a low effort/low risk but high impact feature.

  5. self-assigned this
    on Mar 20, 2026
  6. alixdamman commented on Mar 20, 2026

    @alixdamman
    Contributor

    I am curious of how you manage file associations ? Is it via the meta.yaml file to build the conda package ?

  7. gdementen commented on Mar 20, 2026

    @gdementen
    CollaboratorAuthor

    via menuinst v2 which includes that capability in addition to creating shortcuts. So, it is not via meta.yaml but packagename.json in the conda recipe directory. I haven't updated to v2 yet, but this is the object of #306

  8. alixdamman commented on Mar 20, 2026

    @alixdamman
    Contributor

    Thanks for your reply

  9. added 2 commits that reference this issue on Mar 23, 2026
    32df96f
    ec8e55c
  10. added a commit that references this issue on Mar 26, 2026
    e8d6d68
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions