-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
Version info
- OS: [e.g. macOS 10.14, Windows 10, Ubuntu 18.04]
- Build: [e.g. 1062 - type "About" in the command palette]
Description
When Sublime merge is executed as
+ exec systemd-run --user --unit smerge --slice smerge.slice --property=CollectMode=inactive-or-failed --property=OOMScoreAdjust=300 --same-dir /usr/bin/smerge -- "$@"
it does not do anything. -h
works, though:
$ journalctl --follow
systemd[5102]: Created slice smerge.slice - Slice /smerge.
systemd[5102]: Started smerge.service - /usr/bin/smerge --.
systemd[5102]: Started smerge.service - /usr/bin/smerge --.
systemd[5102]: Started smerge.service - /usr/bin/smerge --.
systemd[5102]: Started smerge.service - /usr/bin/smerge -- -h.
smerge[808806]: Sublime Merge build 2112
smerge[808806]: Usage: smerge path Open the given repository
smerge[808806]: or: smerge search query Search for commits in the current repository
smerge[808806]: or: smerge blame file [line] Blame the given file in the current repository
smerge[808806]: or: smerge log file Show the file history in the current repository
smerge[808806]: or: smerge mergetool Opens the merge tool for the given files
smerge[808806]: [--no-wait] [base] left right [-o merged]
smerge[808806]: -n or --new-window: Open a new window
smerge[808806]: --launch-or-new-window: Only open a new window if the application is running
smerge[808806]: -b or --background: Don't activate the application
smerge[808806]: --safe-mode: Launch using a sandboxed (clean) environment
smerge[808806]: -h or --help: Show help (this message) and exit
smerge[808806]: -v or --version: Show version and exit
Steps to reproduce
Steps to reproduce the behavior:
- Open repository ...
- Run command ...
- Click on ...
Expected behavior
A description of what you expected to happen.
Debug Information
The Sublime Merge debug information can be used to narrow down the cause of an issue.
It can be collected with the following steps:
- Open Sublime Merge
- Open the repository where the bug occurs
- Navigate to
Help > Debug Information
via the application menu - Before sharing, please redact any information that's sensitive such as file paths, git user information, remote URLs etc.
This section may be omitted/removed.
Screenshots
If applicable, add screenshots to help explain your problem. This section may be omitted/removed.
Metadata
Metadata
Assignees
Labels
No labels