Bug 405882 - Kile does not accept file paths as parameter as before
Summary: Kile does not accept file paths as parameter as before
Status: RESOLVED FIXED
Alias: None
Product: kile
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.9.92
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-26 09:38 UTC by josmi9966
Modified: 2019-03-31 06:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description josmi9966 2019-03-26 09:38:35 UTC
This was possible before but for some reason seems to have been removed: kile cannot be invoked from the command line with some parameter that identifies the file or project to open. Instead a URL has to be passed.

This is an absurd and extremely user-unfriendly regression, since starting kile simply with a path is the most natural way to use it, and would conform to how basically all other programs from cat to pycharm work on Linux. 

If somebody has really strong feelings about the need to support URLs instead, then why not use -- again in standard Linux fashion -- option flags, e.g. -f somefilepath versus -u someurl?

Not supporting file paths from the command line leaves only two options: clumsily having to convert file paths to URLs, where the frequent use-case of using a relative file path makes things even more awkward, or clicking many times through the file open dialig within kile (since kile also does not start the file picking at the current directory, but always at the home directory level which is super annoying as well).
Comment 1 Michel Ludwig 2019-03-31 06:39:28 UTC
This has been fixed already in commit a843341e234460894a125c07df42cc7da0fa444e.