Skip to content
This repository has been archived by the owner on Sep 8, 2022. It is now read-only.

feature: allow define direct command for any other browser than built-in one #93

Open
edmundlaugasson opened this issue Dec 28, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@edmundlaugasson
Copy link

Feature Request

Specifications:

  • App Version: 27.4.0
  • OS: Linux

Description:

Currently is problematic to guess, what kind of alias to use or whether bash aliases are supported at all (#1241 ).
Hereby I propose to add a chapter into Preferences, where we can configure web browsers to be used.
Currently it is even not seen, which browsers are supported, unless you activate its asking on every adding and then you can see them.
That chapter in Preferences should allow to define either used bash aliases (in case of Linux or other UNIX-like system) and also direct path (to make webcatalog non-dependent on path env variable) or direct run command (e.g. flatpak run org.chromium.Chromium in case of Flatpak version of Chromium web browser). Sometimes we need to run from script the app, e.g. in case of FreePlane, FreeMind we need to run bash script, but it could be any file, that has executable permission in Linux. Sometimes it may require interpreter beforehand (e.g. bash script.sh, python script.py), but sometimes also additional parameters. Sometimes that executable file is in user's path, sometimes not. So, the run commands may vary and be quite complex sometimes (e.g. to run Flatpak apps, there are multiple options, same may apply in other cases).

Additional Context

Nowadays quite often there are used other package managing systems than built-in, because built-in are quite often outdated. Newer or even newest version of apps are available via Flatpak, Snap, AppImage, etc. or even direct binary or even kind of script extracted in storage device.

@quanglam2807 quanglam2807 added the enhancement New feature or request label Jan 19, 2021
@quanglam2807 quanglam2807 transferred this issue from webcatalog/webcatalog-legacy Feb 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants