Skip to content

Not working with linked folders #10

@LukMas

Description

@LukMas

I've started using the plugin because I find it really useful. Thank you!

I've a small request.

I use intellij within a container created with Distrobox (https://distrobox.it).
The container has a custom home folder, created within my host home folder. This allows to add software and configuration files that are local to the container without clogging up the host home. When I'm finish with the container (or the container is broken) I simply remove it, with all the configurations, and the host remain clean.

Also, I've created a container where I've installed node, npm and angular cli.
In the container I've copied the .desktop file that starts intellj idea and exported to the host. In this way I've a 'new' instance of idea that, while running within the host, it uses the container as base directory. This allows to use all the software that exists only in the container (https://blog.niklas.tech/intellij-and-java-on-immutable-linux).

Then I've created a link from a folder of the host, where I've cloned my angular project, to the custom home of the container. I could have avoided this step and directly cloned the project within the container home (but this avoids to clone it every time I remove the container).

Anyway, idea is smart enough to be able to manage the linked project within the container and open the console in the correct home.

The problem with the plugin is that every time I use the shortcut, instead of opening the file within the custom home (also, the link that goes to the container home), it opens the original file. Because the project is created from the container home:

  • the tab with the file is yellow because is not recognized as part of the project
  • trying to change it triggers a box that asks me if I would like to accept to change a file that is not a project file

I've found a solution creating the project from the host folder instead of the container one. But this has the side effect that the terminal runs within that folder, while I would like to have it running within the container one.

Is there a way to solve the problem opening the file from the link within the correct path (also, the container custom home)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions