hyprwm/hyprland-wiki
1
0
Fork 0
mirror of https://github.com/hyprwm/hyprland-wiki.git synced 2024-11-22 04:35:59 +01:00
Code Issues Projects Releases Packages Wiki Activity

pages: Be more generic instead of using "I" and "We"

Browse source
This commit is contained in:
Antonino Scordino 2022-10-21 16:03:44 +02:00
parent 840d8f1f82
commit ff0bbf9904
No known key found for this signature in database
GPG key ID: F20FDE4C896FC2CB
9 changed files with 26 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
pages/Configuring/Binds.md
View file

@ -191,12 +191,10 @@ including OBS, Discord, Firefox, etc.
See the [`pass` dispatcher](./Dispatchers/#dispatchers) for keybinds.
e.g.:
Let's take OBS as example: the "Start/Stop Recording" keybind is set to
<key>SUPER</key> + <key>F10</key>, and you want to make it work globally.
I've set the "Start/Stop Recording" keybind in OBS to <key>SUPER</key> +
<key>F10</key>, and I want it to be global.
Simple, add
Simply, just add
```ini
bind = SUPER,F10,pass,^(com\.obsproject\.Studio)$
@ -256,7 +254,7 @@ submap=reset
this case, `escape`)
If you get stuck inside a keymap, you can use `hyprctl dispatch submap reset` to
go back. If you do not have a terminal open, tough luck buddy. I warned you.
go back. If you do not have a terminal open, tough luck buddy. You have been warned.
You can also set the same keybind to perform multiple actions, such as resize
and close the submap, like so:

2
pages/Configuring/Configuring-Hyprland.md
View file

@ -1,6 +1,6 @@
The config is located in `~/.config/hypr/hyprland.conf`.
I recommend you copy the `examples/hyprland.conf`, but you can also edit the
It is recommended to copy the `examples/hyprland.conf`, but you can also edit the
autogenerated config.
By removing the line `autogenerated=1` you'll remove the yellow warning.

8
pages/Configuring/Environment-variables.md
View file

@ -1,7 +1,7 @@
We have [previously mentioned](../Getting-Started/Quick-start/#wrapping-the-launcher-recommended) using a wrapper to launch Hyprland. Whether you
start Hyprland through TTY or a Display Manager, it is recommended to use a wrapper.
As such, you can pass certain environment variables to improve Wayland compatibility, or
simply change certain aspects of your desktop.
As [previously mentioned](../Getting-Started/Quick-start/#wrapping-the-launcher-recommended), it's
useful using a wrapper to launch Hyprland. Whether you start Hyprland through TTY or a Display
Manager, it is always suggested to use one. As such, you can pass certain environment
variables to improve Wayland compatibility, or simply change certain aspects of your desktop.
Please avoid putting those environment variables in /etc/environment. That will cause all
sessions (including Xorg ones) to pick up your wayland-specific environment on traditional

5
pages/Configuring/Uncommon-tips-&-tricks.md
View file

@ -31,9 +31,10 @@ submap=reset
## Window Dancing
Some XWayland games like Rhythm Doctor and Friday Night Funkin' mods like to move the windows by themselves, but that often doesn't work by default.
Some XWayland games like Rhythm Doctor and Friday Night Funkin' mods like to move
the windows by themselves, but that often doesn't work by default.
To configure this, I'll be using Rhythm Doctor as an example.
For example, if you want to configure Rhythm Doctor, you'd have to:
1. Set input rules
```ini

5
pages/Contributing and Debugging/_index.md
View file

@ -63,7 +63,7 @@ bugs.
When Hyprland crashes, use `coredumpctl` and then `coredumpctl info PID` to see
the dump. See the instructions below for more info about `coredumpctl`.
I also recommend the amazing command
You can also use the amazing command
```sh
watch -n 0.1 "cat /tmp/hypr/$(echo HYPRLAND_INSTANCE_SIGNATURE)/hyprland.log | grep -v \"arranged\" | tail -n 40"
@ -83,8 +83,7 @@ Hyprland can run nested in a window. For that, make sure you did the following:
- removed ALL `exec=` and `exec-once=` keywords from your debug config
(`hyprlandd.conf`)
- set a resolution and are not using `preferred`
- made sure no keybinds overlap (I recommend using a different mod for your
keybinds altogether)
- made sure no keybinds overlap (use a different mod for your keybinds altogether)
Once you launch, the display will probably be completely garbled. To fix that,
in the parent, do a `hyprctl clients` and note the size of the window. Make sure

4
pages/FAQ/_index.md
View file

@ -28,8 +28,8 @@ variable.
# My external monitor is blank / doesn't render / receives no signal (laptop)
For Radeon graphics - unfortunately, it's a bug in wlroots, and I can't
do much about it other than wait for the wlroots devs to fix it:
For Radeon graphics - unfortunately, it's a bug in wlroots, and not much
can be done other than waiting for the wlroots devs to fix it:
[https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3451](https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3451)
For Nvidia graphics - unfortunately, it's a wlroots issue as well, most likely due to Nvidia's

8
pages/Getting Started/Quick-start.md
View file

@ -1,6 +1,6 @@
After you have installed Hyprland, you can either launch it from a TTY with
wAfter you have installed Hyprland, you can either launch it from a TTY with
`Hyprland` or from a login manager. Although login managers aren't officially
supported, I recommend `SDDM`, as it's been working flawlessly with wayland
supported, you might want to use `SDDM`, as it's been working flawlessly with wayland
compositors.
It is recommended you have `kitty` installed for terminal access, (example and
@ -34,7 +34,7 @@ exec Hyprland
```
You can add as many exported envvars as you need (Nvidia users might need a
lot), but I recommend having _at least_ the shown two.
lot), but it' recommended to have _at least_ the shown two.
You should now launch Hyprland with `wrappedhl` instead of `Hyprland`. Make sure
to copy your `.desktop` file in `/usr/share/wayland-sessions/` and edit it if you use a
@ -54,7 +54,7 @@ the desktop file on updates. If you manually build Hyprland, consider using `sud
Once you log in, you'll be greeted with a yellow warning that will give you some
basic keybind info of your pregenerated config.
I recommend you use the config provided in `examples/hyprland.conf` though.
It's better to use the config provided in `examples/hyprland.conf` though.
Paste it into `~/.config/hypr/hyprland.conf`

3
pages/Useful Utilities/Color-Pickers.md
View file

@ -1,6 +1,7 @@
Color pickers are useful for quickly grabbing a color of _something_ on your screen.
We recommend our own solution, which, so far, seems to be the only one that doesn't suck.
It's preferred using _hyrpwm_'s own solution, which, so far, seems to be the only one that
doesn't suck.
# Hyprpicker

8
pages/Useful Utilities/Status-Bars.md
View file

@ -50,8 +50,8 @@ your module this way:
## Clicking on workspace doesn't work!
On the `wlr/workspaces` module, add `"on-click": "activate"`. That's the purpose of
the `sed` command we had to apply before building: the default way to select a
workspace by clicking uses the `swaymsg`'s way, furthermore it is required to edit
the `sed` command used before building: the default way to select a workspace by
clicking uses the `swaymsg`'s way, furthermore it is required to edit
this function to make it work with `hyprctl`.
# Eww
@ -64,8 +64,8 @@ by manually compiling. In the latter case, you can follow the
## Configuration
After you've successfully installed Eww, you can move onto configuring it. There
are a few examples listed in the [Readme](https://github.com/elkowar/eww). We
highly recommend you also read through the
are a few examples listed in the [Readme](https://github.com/elkowar/eww). It's also
highly recommend to read through the
[Configuration options](https://elkowar.github.io/eww/configuration.html).
{{< hint type=important >}}