Allow file as command line argument

[Jan Smith]

When invoking kile from my working directory using something like "kile main.tex" the error "Unknown host main.tex: Host not found" is raised.

This always worked in previous versions and is an unnecessary and user-unfriendly change of behaviour. In most cases kile will be used to work on a file or project in the current directory and it should be easy to run it for that purpose, making it use a specific file or directory initially.

Kile also crashes with a segementation fault when invoking with the command "kile ."

If kile is started from inside a directory without an argument and one then tries to open a file from the current directory, the open file dialog does NOT show the current directory but one has to start from the home directory which is extremely annoying.

All in all the behaviour of kile for starting working on some file in a directory has degraded so much as to make it unusable.

[Vasimos (vasimos)]

SUMMARY

In Kile version 2.9.91 when I try to open an existing tex file from command line, relative paths are not recognized.

STEPS TO REPRODUCE

kile file.tex

OBSERVED RESULT

I get the error message:

Unknown host file.tex: Host not found

EXPECTED RESULT

File should open in editor (worked in previous versions)

SOFTWARE/OS VERSIONS
Windows:
MacOS:
Linux/KDE Plasma: Kubuntu 18.04
(available in About System)
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION

Kile version 2.9.91

Using

kile ./file.tex

leads to segmentation fault.

Using absolute path works.

An extensive discussion of the bug, but no indication of a bug report appeared here:

https://askubuntu.com/questions/1069743/open-a-file-from-the-command-line

[Michel Ludwig (michel-ludwig)]

Hi, please upgrade to Kile 2.9.92.

This bug has been fixed already.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Weis (martin-weis-newsadress)]

This behaviour hits me recently, upgraded to bionic LTS from 16.04 LTS. Did not experience this before.

There is an askubuntu about it with more details:
https://askubuntu.com/questions/1069743/open-a-file-from-the-command-line

This should be fixed, as it is clearly a bug not to be able to open files from command line, man states:
kile [ generic-options ] [ --line line ] [ --new ] [ file ]

This is the currently shipped version that I use:

LANG=C apt-cache policy kile
kile:
  Installed: 4:2.9.91-4
  Candidate: 4:2.9.91-4
  Version table:
 *** 4:2.9.91-4 500
        500 http://ftp-stud.hs-esslingen.de/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status

[Christian Leichsenring (christian-leichsenring)]

Is there an upstream bug report for this since clearly nobody's reading this?