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

Update links to git repo 

Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
This commit is contained in:
Yuxuan Shui 2019-10-24 19:24:38 +01:00
parent 43b21731f8
commit 634903727a
No known key found for this signature in database
GPG Key ID: 37C999F617EA1A47
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -21,7 +21,7 @@ Currently new backends features better vsync with the xrender backend, improved
New backend features will only be implemented on the new backends from now on, and the old backends will eventually be phased out after the new backends stabilizes.
To test the new backends, add the `--experimental-backends` flag to the command line you used to run compton. This flag is not available from the configuration file.
To test the new backends, add the `--experimental-backends` flag to the command line you used to run picom. This flag is not available from the configuration file.
To report issues with the new backends, please state explicitly you are using the new backends in your report.
@ -47,7 +47,7 @@ In the end, we picked `picom` (a portmanteau of `pico` and `composite`) as our n
### Migration
Following the [deprecation process](https://github.com/yshui/compton/issues/114), migration to the new name will be broken into 3 steps:
Following the [deprecation process](https://github.com/yshui/picom/issues/114), migration to the new name will be broken into 3 steps:
1. All mentions to `compton` will be updated to `picom` in the code base. `compton` will still be installed, but only as a symlink to `picom`. When `picom` is launched via the symlink, a warning message is printed, alerting the user to migrate. Similarly, the old configuration file names and dbus interface names will still be accepted but warned.
2. 3 major releases after step 1, the warning messages will be prompted to error messages and `picom` will not start when launched via the symlink.
@ -57,7 +57,7 @@ The dbus interface and service names are unchanged, so no migration needed for t
## Change Log
See [Releases](https://github.com/yshui/compton/releases)
See [Releases](https://github.com/yshui/picom/releases)
## Build
@ -134,7 +134,7 @@ Default install prefix is `/usr/local`, you can change it with `meson configure
### Code
You can look at the [Projects](https://github.com/yshui/compton/projects) page, and see if there is anything interests you. Or you can take a look at the [Issues](https://github.com/yshui/compton/issues).
You can look at the [Projects](https://github.com/yshui/picom/projects) page, and see if there is anything interests you. Or you can take a look at the [Issues](https://github.com/yshui/picom/issues).
### Non-code

2
man/picom-trans.1.asciidoc
View File

@ -77,7 +77,7 @@ picom-trans -c -- -5
BUGS
----
Please submit bug reports to <https://github.com/yshui/compton>.
Please submit bug reports to <https://github.com/yshui/picom>.
SEE ALSO
--------

4
man/picom.1.asciidoc
View File

@ -456,13 +456,13 @@ $ picom --backend glx --vsync
BUGS
----
Please submit bug reports to <https://github.com/yshui/compton>.
Please submit bug reports to <https://github.com/yshui/picom>.
Out dated information in this man page is considered a bug.
RESOURCES
---------
Homepage: <https://github.com/yshui/compton>
Homepage: <https://github.com/yshui/picom>
SEE ALSO
--------