Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#60039 - [code] Can't use command line options

Attached to Project: Community Packages
Opened by Ariel AxionL (axionl) - Thursday, 13 September 2018, 03:14 GMT
Last edited by Filipe Laíns (FFY00) - Wednesday, 19 September 2018, 18:22 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Filipe Laíns (FFY00)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

The code on [community-testing] cannot receive command-line options.

https://code.visualstudio.com/docs/editor/command-line

Additional info:
* package version(s)

community-testing/code 1.27.1-6

* config and/or log files etc.

Default

Steps to reproduce:

run `code --version` on the terminal.

The version information is not output, but the program window is opened directly.
This task depends upon

Closed by  Filipe Laíns (FFY00)
Wednesday, 19 September 2018, 18:22 GMT
Reason for closing:  Fixed
Comment by Slavi Pantaleev (s.pantaleev) - Thursday, 13 September 2018, 06:23 GMT
In addition to that, when you do `code /some/path`, Visual Studio Code is not started in the background, but rather keeps your terminal window busy until you quit the program.

I remember there being some fixes for this same thing in the AUR packages.
Comment by Filipe Laíns (FFY00) - Thursday, 13 September 2018, 14:34 GMT
I am aware. I can't patch that.

Regarding to the CLI problem, that will probably only get fixed after the electron issue.

Loading...