Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

%U is null when launchBrowser is false and launchCommand is set #1065

Closed
cgty opened this issue Mar 19, 2018 · 1 comment
Closed

%U is null when launchBrowser is false and launchCommand is set #1065

cgty opened this issue Mar 19, 2018 · 1 comment

Comments

@cgty
Copy link
Contributor

cgty commented Mar 19, 2018

I used to use the following .ungitrc to start ungit server and launch chromium without the browser toolbars.

{
  "debug": true,
  "launchCommand": "chromium-browser --app=%U",
  "launchBrowser": false
}

It was working in the previous versions of ungit (I can't recall the exact version I used before).

With the latest version, when I run ungit within a git repository, the output is as follows:

## Ungit started ##

Took 635ms to start server.
Running custom launch command: chromium-browser --app=null

And an empty chromium window (with toolbars) is launched.

If I set launchBrowser to true, %U is correctly set and chromium is launched with the correct configuration. But the default browser is also launched -as expected-, which makes it an unusable workaround.

I think adding || config.launchCommand to this line might fix this issue, but I haven't tested it myself.

} else if (override || config.launchBrowser) {

I can test & verify it locally and send a PR if my approach is right.

versions
ungit: 1.4.13
node: v8.9.4
npm: 5.6.0
os: linux

@ylecuyer
Copy link
Contributor

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants