Skip to content

[FEAT] Override custom floo actions #7

Description

@keyvizsla

Is your feature request related to a problem? Please describe.
Sometimes I just want to look into one of my projects because I might know that I have already fixed a specific issue there that I am now facing on the current project I am working on. In such a case I only want to quickly jump to the old project, check out what I need, jump back and fix my issue.
Therefore, it is undesirable to spin up a full development environment should I have created a .floo file in one of the projects I am jumping between.

Describe the solution you'd like
I would like to be able to tell floo to not perform the configured .floo actions for a selected project/fireplace.
Instead when I press CTRL+<Enter> (instead of the regular <Enter>, floo should not perform its regular actions, but instead only yield a cd of my shell into the directory of said project, i.e. perform the standard action as if I had not placed a .floo file in the target directory in the first place minus the sourcing of environment variables.

Describe alternatives you've considered
I have also considered not only performing the directory change but also the environment sourcing, however the more likely use case is that I just need to grab something quick from the project directory and then go back to whatever I was doing, so people wouldn't want to have to deal with an altered environment just for that.

Please comment on this issue if you would like to tackle it so that we can properly assign you the work and prevent duplicated efforts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions