BitHeaven/picom
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

rename: replace "compton" in the codebase

Browse Source 
leftovers:

1) config file path. Has to implement compatibility functionalities before
  we can change it.

2) links in man pages. Has to migrate the repo first.

3) _COMPTON_SHADOW, it has become a defacto standard, so we have to keep
   supporting it.

4) dbus names, undecided whether we should/could change it.

Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
This commit is contained in:
Yuxuan Shui
2019-10-23 19:27:30 +01:00
parent ed6a96dae9
commit 8ddbebb5d1
33 changed files with 172 additions and 139 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
.github/issue_template.md vendored
View File

@@ -13,12 +13,12 @@
### Environment
<!-- Tell us something about the desktop environment you are using, for example: i3-gaps, Gnome Shell, etc. -->
### Compton version
<!-- Put the output of `compton --version` here. -->
<!-- If you are running compton v4 or later, please also include the output of `compton --diagnostics` -->
### picom version
<!-- Put the output of `compton --version` or `picom --version` here. -->
<!-- If you are running compton v4 or later, please also include the output of `compton --diagnostics` or `picom --diagnostics` -->
<!-- Example: v1 -->
### Compton configuration:
### Configuration:
```
// Paste your configuration here
```
@@ -38,12 +38,12 @@
### Stack trace
<!--
If compton crashes, please make sure your compton is built with debug info, and provide a stack trace of compton when it crashed.
Note, when compton crashes in a debugger, your screen might look frozen. But gdb will likely still handle your input if it is focused.
If the compositor crashes, please make sure you built it with debug info, and provide a stack trace captured when it crashed.
Note, when the compositor crashes in a debugger, your screen might look frozen. But gdb will likely still handle your input if it is focused.
Often you can use 'bt' and press enter to get the stack trace, then 'q', enter, 'y', enter to quit gdb.
-->
<!-- Or, you can enable core dump, and upload the core file and the compton executable here. -->
<!-- Or, you can enable core dump, and upload the core file with the corresponding executable here. -->
### Other details
<!-- If your problem is visual, you are encouraged to record a short video when the problem occurs and link to it here. -->