Classic confinement request for FAT

A key feature of fat is “Open with external command,” which allows a developer to open the file they are currently inspecting in any command-line tool of their choice (e.g., vim, nvim, less, etc.). This behavior is user-configurable via the fatrc file, allowing users to integrate fat seamlessly into their personal development environment and workflow.

This functionality is impossible under strict confinement. We have tested this and the security policy correctly blocks the execution of arbitrary host commands with a “Permission denied” error.

We also investigated alternatives as suggested by the documentation for unsupported use cases. The standard xdg-open mechanism is not a viable solution because it is designed to launch default GUI handlers and does not support our core requirement: allowing the user to specify and launch an arbitrary, often terminal-based, application.

For fat to fulfill its purpose as an effective developer tool that integrates with a user’s command-line ecosystem, classic confinement is a necessity.

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

This request has been added to the queue for review by the @reviewers team.

Hello @Zuhaitz-dev!

Given the snap’s functionality and the category it falls under, classic confinement makes sense to me.

What do the other @reviewers think?