diff --git a/Compiling.md b/Compiling.md index 93cf195..672af5d 100644 --- a/Compiling.md +++ b/Compiling.md @@ -1,7 +1,7 @@ ## Dependencies -See the [README](/jaagr/polybar/#dependencies) for a general list of dependencies. +See the [README](/polybar/polybar/#dependencies) for a general list of dependencies. -Click [here](/jaagr/polybar#getting-started) to check if polybar was already packaged for your distro. +Click [here](/polybar/polybar#getting-started) to check if polybar was already packaged for your distro. ### Build Dependencies The following dependencies are only needed during compilation, you can remove them, if you don't need them, after you built polybar @@ -67,7 +67,7 @@ or directly against the newest commit in the repository. **Release Archive** Download the release archive `polybar-.tar` over at our -[release page](https://github.com/jaagr/polybar/releases) and extract it with +[release page](https://github.com/polybar/polybar/releases) and extract it with `tar xvf polybar-.tar`. Now change into the extracted folder (generally `cd polybar`) @@ -79,7 +79,7 @@ To get the sources directly from the repository, run the following commands: changes, there may be bugs. ```sh # Make sure to type the `git' command as is to clone all git submodules too -git clone --recursive https://github.com/jaagr/polybar +git clone --recursive https://github.com/polybar/polybar cd polybar ``` @@ -89,7 +89,7 @@ folder where the polybar sources are located. To compile, run the following commands: -**Note:** If you are using anaconda, run `conda deactivate` before running `cmake`, also see the note on the [Known Issues page](/jaagr/polybar/wiki/Known-Issues#building-with-anaconda-installed) if that doesn't work. +**Note:** If you are using anaconda, run `conda deactivate` before running `cmake`, also see the note on the [Known Issues page](/polybar/polybar/wiki/Known-Issues#building-with-anaconda-installed) if that doesn't work. ```sh mkdir build diff --git a/Configuration.md b/Configuration.md index 8b4bf0f..9df9f92 100644 --- a/Configuration.md +++ b/Configuration.md @@ -111,7 +111,7 @@ exec = ${root.myscript-command} ## Bar settings -***Note*** For configuring multiple monitors automatically see https://github.com/jaagr/polybar/issues/763 +***Note*** For configuring multiple monitors automatically see https://github.com/polybar/polybar/issues/763 ~~~ dosini [bar/mybar] diff --git a/Debugging-your-Config.md b/Debugging-your-Config.md index 5fec439..dec9f2d 100644 --- a/Debugging-your-Config.md +++ b/Debugging-your-Config.md @@ -53,15 +53,15 @@ when you just drop 200 lines of configs on them with the comment "It doesn't wor ## Read the Documentation The above should have given you a specific location where your bar has issues. The next step should be to read on the -[Wiki](https://github.com/jaagr/polybar/wiki) about whatever component is not working. Most problems arise from incorrect +[Wiki](https://github.com/polybar/polybar/wiki) about whatever component is not working. Most problems arise from incorrect or incomplete configuration, so make sure you haven't missed some configuration option that could solve your issue. -Also consult the [Known Issues](https://github.com/jaagr/polybar/wiki/Known-Issues) page and search through the -[GitHub issues](https://github.com/jaagr/polybar/issues?utf8=%E2%9C%93&q=is%3Aissue) for people that had the same issue. +Also consult the [Known Issues](https://github.com/polybar/polybar/wiki/Known-Issues) page and search through the +[GitHub issues](https://github.com/polybar/polybar/issues?utf8=%E2%9C%93&q=is%3Aissue) for people that had the same issue. ## Ask for Help (if needed) If you completed all the steps above and weren't able to fix the issue yourself, it may be time to ask someone for help. -On our [SUPPORT.md](https://github.com/jaagr/polybar/blob/master/SUPPORT.md) page, you can find resources where you can +On our [SUPPORT.md](https://github.com/polybar/polybar/blob/master/SUPPORT.md) page, you can find resources where you can ask for help. When you finally do reach out, make sure to include the MVCE that you created above as well as precise instructions on how to reproduce your issue. diff --git a/Fonts.md b/Fonts.md index 8ab9e4a..078d174 100644 --- a/Fonts.md +++ b/Fonts.md @@ -1,4 +1,4 @@ -Make sure you read the [Configuration wiki page](/jaagr/polybar/wiki/Configuration) on how to define the list of fonts to use. +Make sure you read the [Configuration wiki page](/polybar/polybar/wiki/Configuration) on how to define the list of fonts to use. The sample config shipped with polybar uses the the following fonts by default: xorg's misc-fixed, [Unifont](http://unifoundry.com/unifont/index.html), and [siji](https://github.com/stark/siji). Siji on debian-based system won't work right away after you install it with their script, you need to make sure to run `sudo dpkg-reconfigure fontconfig-config` and enable bitmap fonts. @@ -7,7 +7,7 @@ On Ubuntu even that command doesn't work and you have to manually `sudo rm /etc/ In the example configurations in this wiki we try to use icons from siji or unifont or we use emojis (provided by for example Noto Color Emoji). If you find icons that are neither emojis nor from these fonts, please let us know. ## Fonts -If you don't explicitly set the font-index for a tag, the bar will iterate the font list and pick the first one that is able to draw the character. [Read more on the wiki page about Formatting](https://github.com/jaagr/polybar/wiki/Formatting) and about what tags allow you to define a specific font index. +If you don't explicitly set the font-index for a tag, the bar will iterate the font list and pick the first one that is able to draw the character. [Read more on the wiki page about Formatting](https://github.com/polybar/polybar/wiki/Formatting) and about what tags allow you to define a specific font index. **NOTE**: The `-font` property is a 1-based index of available fonts (which means that `*-font = 1` will use `font-0`). @@ -95,7 +95,7 @@ Icons can be provided in the form of text characters. Popular icon fonts include - [IcoMoon](https://icomoon.io/app/#/select/library) - Custom/Mixed Licenses - [Nerd Patched Fonts](https://github.com/ryanoasis/nerd-fonts) - Mixed Licenses -Most icon fonts make use of the Private Use Area unicode block and can conflict. Setting system priority via FontConfig may be preferable. After defining a font as explained above, [formatting tags](https://github.com/jaagr/polybar/wiki/Formatting#format-tags) can be used. Order of font definitions can also affect precedence. +Most icon fonts make use of the Private Use Area unicode block and can conflict. Setting system priority via FontConfig may be preferable. After defining a font as explained above, [formatting tags](https://github.com/polybar/polybar/wiki/Formatting#format-tags) can be used. Order of font definitions can also affect precedence. ### [GNOME Character Map](https://en.wikipedia.org/wiki/GNOME_Character_Map) `gucharmap` is a convenient utility for browsing selected fonts. Filter `View > By Unicode Block + Show only glyphs from this font` and navigate to Private Use Area. @@ -137,4 +137,4 @@ Usage: `perl test-fonts.pl "😀"` Note: maybe you need to install "Font::FreeType" module for the Script ``` $ perl -MCPAN -e 'install Font::FreeType' -``` \ No newline at end of file +``` diff --git a/Formatting.md b/Formatting.md index 458ccff..55fb8f6 100644 --- a/Formatting.md +++ b/Formatting.md @@ -1,5 +1,5 @@ -Make sure you read the [Configuration wiki page](https://github.com/jaagr/polybar/wiki/Configuration). +Make sure you read the [Configuration wiki page](https://github.com/polybar/polybar/wiki/Configuration). ## Formats @@ -152,7 +152,7 @@ you could use the foreground tag like this: ~~~dosini label-volume = %{F#f00}%percentage%%{F-}% ~~~ -**Pitfalls:** As described in [`#615`](https://github.com/jaagr/polybar/issues/615) using polybar variables inside +**Pitfalls:** As described in [`#615`](https://github.com/polybar/polybar/issues/615) using polybar variables inside format tags is not possible. So something like this **won't** work: ```dosini label = "Some text %{F${colors.foreground-alt}}Colored%{F-}" diff --git a/Home.md b/Home.md index 1cbaf34..ee6b342 100644 --- a/Home.md +++ b/Home.md @@ -13,7 +13,7 @@ This sample configuration may not be fully functional on your machine without mo [![](https://u.teknik.io/x32YI.png)](https://u.teknik.io/x32YI.png) -See the [Configuration wiki page](https://github.com/jaagr/polybar/wiki/Configuration) for more details on how to configure the bar. +See the [Configuration wiki page](https://github.com/polybar/polybar/wiki/Configuration) for more details on how to configure the bar. ## Running the app @@ -104,4 +104,4 @@ To allow other windows to be placed above the bar, or to avoid having the bar vi [bar/mybar] override-redirect = true wm-restack = i3 -~~~ \ No newline at end of file +~~~ diff --git a/Inter-process-messaging.md b/Inter-process-messaging.md index 7d6f29f..1999a7d 100644 --- a/Inter-process-messaging.md +++ b/Inter-process-messaging.md @@ -7,7 +7,7 @@ By default the project is built with a helper tool called `polybar-msg` used to ### Hook message for custom/ipc modules Format: `hook:module/` -See the [module wiki page](https://github.com/jaagr/polybar/wiki/Module:-ipc) for more details on how to setup message hooks. +See the [module wiki page](https://github.com/polybar/polybar/wiki/Module:-ipc) for more details on how to setup message hooks. ### Action message to simulate mouse action Format: `action:` diff --git a/Known-Issues.md b/Known-Issues.md index f11ef43..bbb89f4 100644 --- a/Known-Issues.md +++ b/Known-Issues.md @@ -59,29 +59,29 @@ Do the same thing for `PKG_CONFIG_PATH` (though this variable is often already e polybar with either the `build.sh` script or `cmake` and `make`. Make sure that you do a clean build (redownload all polybar sources). -This was reported in [`#502`](https://github.com/jaagr/polybar/issues/502), -[`#733`](https://github.com/jaagr/polybar/issues/733), [`#659`](https://github.com/jaagr/polybar/issues/659), -[`#1629`](https://github.com/jaagr/polybar/issues/1629) +This was reported in [`#502`](https://github.com/polybar/polybar/issues/502), +[`#733`](https://github.com/polybar/polybar/issues/733), [`#659`](https://github.com/polybar/polybar/issues/659), +[`#1629`](https://github.com/polybar/polybar/issues/1629) ## Huge Emojis **Problem:** When using the Noto Emoji font, Emojis appear extremely big on the bar. Setting the `size` property doesn't help. **Fix:** Add the `scale` property to the font definition in your config. For example `font-7 = NotoEmoji:scale=10`. The larger the number the smaller the Emojis. -This issue was discovered in [`#905`](https://github.com/jaagr/polybar/issues/905). +This issue was discovered in [`#905`](https://github.com/polybar/polybar/issues/905). ## Click Commands are not Executed **Problem:** Some `click-*` commands are not executed when the bar is clicked. This is a bug that is triggered by the `click-*` command producing output on `stdout` or `stderr`. **Workaround:** The `click-*` command must not produce any output, so redirect any output to `/dev/null`. This can be done by appending `>/dev/null 2>&1` to the `click-*` command (If you background the program with `&`, make sure that `&` is still at the very end). -This issue was discovered in [`#916`](https://github.com/jaagr/polybar/issues/916). +This issue was discovered in [`#916`](https://github.com/polybar/polybar/issues/916). ## With multiple modules of the same type, actions on those modules control the leftmost module **Problem:** This affects all modules that provide their internal mouse actions that change the module behaviour: * `internal/alsa` * `internal/date` -* `custom/menu` (Per it's [Wiki Page](https://github.com/jaagr/polybar/wiki/Module:-menu) you can already only define one menu per bar) +* `custom/menu` (Per it's [Wiki Page](https://github.com/polybar/polybar/wiki/Module:-menu) you can already only define one menu per bar) * `internal/mpd` * `internal/pulseaudio` * `internal/xbacklight` @@ -102,7 +102,7 @@ This issue occurs because `jsoncpp` changes the name of their `.so` file every r **Workaround:** If you want to explicitly set a module's (or parts of its) background to `background-0`, use a color that is almost the same. E.g. if `background-0` is `#FFFF00` use `#FFFF01`. -This behaviour was introduced in [`#831`](https://github.com/jaagr/polybar/pull/831), to resolve the issue described in [`#759`](https://github.com/jaagr/polybar/issues/759). There is no way to resolve this without some major code changes to the renderer. +This behaviour was introduced in [`#831`](https://github.com/polybar/polybar/pull/831), to resolve the issue described in [`#759`](https://github.com/polybar/polybar/issues/759). There is no way to resolve this without some major code changes to the renderer. ## `override-redirect` in i3 **Problem:** i3 and polybar sometimes interact quite weirdly and often `override-redirect = true` is needed to resolve it. This however makes i3 not reserve space for the polybar window, making other windows overlap polybar. There doesn't seem to be that much that we can do about this from polybar's side, because as soon as we need to use `override-redirect = true`, we can't tell i3 to reserve space for the polybar window. @@ -132,4 +132,4 @@ Note that it will not be installed via `apt` and thus to uninstall you'll need t Now you should be able to compile polybar without problems, just clear the build directory first. -This issue was discovered in [`#644`](https://github.com/jaagr/polybar/issues/644), you will find more details there. +This issue was discovered in [`#644`](https://github.com/polybar/polybar/issues/644), you will find more details there. diff --git a/Module:-alsa.md b/Module:-alsa.md index b200197..82db984 100644 --- a/Module:-alsa.md +++ b/Module:-alsa.md @@ -1,5 +1,5 @@ This module shows volume and mute state for ALSA mixers. Most of the module functionality should work as long as you are using an alsa backend, like pulseaudio-alsa. -If you use `pulseaudio` use the [`internal/pulseaudio`](https://github.com/jaagr/polybar/wiki/Module:-pulseaudio) module instead, even if it uses alsa as the backend. +If you use `pulseaudio` use the [`internal/pulseaudio`](https://github.com/polybar/polybar/wiki/Module:-pulseaudio) module instead, even if it uses alsa as the backend. **NOTE**: This module requires the project to be built with ALSA support. diff --git a/Module:-backlight.md b/Module:-backlight.md index 5e520b1..15850c3 100644 --- a/Module:-backlight.md +++ b/Module:-backlight.md @@ -1,4 +1,4 @@ -**If this module doesn't work for you, try to use [the new xbacklight module](https://github.com/jaagr/polybar/wiki/Module:-xbacklight)** +**If this module doesn't work for you, try to use [the new xbacklight module](https://github.com/polybar/polybar/wiki/Module:-xbacklight)** --- diff --git a/Module:-bspwm.md b/Module:-bspwm.md index a41ce91..ccfeef5 100644 --- a/Module:-bspwm.md +++ b/Module:-bspwm.md @@ -1,6 +1,6 @@ This module uses the bspwm ipc client to display information about available monitors, desktops and layout states. -See the [Configuration wiki page](https://github.com/jaagr/polybar/wiki/Configuration#global-wm-settings) for details on how to configure the `_NET_WM_STRUT_PARTIAL` values. This will allow you to update `padding_{top,bottom}` when the bar is launched. +See the [Configuration wiki page](https://github.com/polybar/polybar/wiki/Configuration#global-wm-settings) for details on how to configure the `_NET_WM_STRUT_PARTIAL` values. This will allow you to update `padding_{top,bottom}` when the bar is launched. ### Accessible workspace cycling @@ -154,4 +154,4 @@ counter=0 bspc query -D --names | while read -r name; do printf 'ws-icon-%i = "%s;"\n' $((counter++)) $name done -~~~ \ No newline at end of file +~~~ diff --git a/Module:-github.md b/Module:-github.md index 13eba1a..f840984 100644 --- a/Module:-github.md +++ b/Module:-github.md @@ -32,4 +32,4 @@ format =