aboutsummaryrefslogtreecommitdiff
path: root/tinywl
diff options
context:
space:
mode:
authorKirill Primak <vyivel@eclair.cafe>2023-11-14 19:46:04 +0300
committerKirill Primak <vyivel@eclair.cafe>2023-11-14 19:46:04 +0300
commit6cf0bb4b1920e89204668c3c207aa392fc82fba7 (patch)
tree213b429778b9e12adbdb69ed97fa04e95acc2e7c /tinywl
parent73a387d3b691e4fba7f91919d71780ce6c50a971 (diff)
tinywl: don't use "I"/"my" in docs
Diffstat (limited to 'tinywl')
-rw-r--r--tinywl/tinywl.c18
1 files changed, 7 insertions, 11 deletions
diff --git a/tinywl/tinywl.c b/tinywl/tinywl.c
index 3ced9342..e3e8f237 100644
--- a/tinywl/tinywl.c
+++ b/tinywl/tinywl.c
@@ -385,9 +385,9 @@ static void process_cursor_resize(struct tinywl_server *server, uint32_t time) {
* toplevel on one or two axes, but can also move the toplevel if you resize
* from the top or left edges (or top-left corner).
*
- * Note that I took some shortcuts here. In a more fleshed-out compositor,
- * you'd wait for the client to prepare a buffer at the new size, then
- * commit any movement that was prepared.
+ * Note that some shortcuts are taken here. In a more fleshed-out
+ * compositor, you'd wait for the client to prepare a buffer at the new
+ * size, then commit any movement that was prepared.
*/
struct tinywl_toplevel *toplevel = server->grabbed_toplevel;
double border_x = server->cursor->x - server->grab_x;
@@ -909,10 +909,8 @@ int main(int argc, char *argv[]) {
server.scene_layout = wlr_scene_attach_output_layout(server.scene, server.output_layout);
/* Set up xdg-shell version 3. The xdg-shell is a Wayland protocol which is
- * used for application windows. For more detail on shells, refer to my
- * article:
- *
- * https://drewdevault.com/2018/07/29/Wayland-shells.html
+ * used for application windows. For more detail on shells, refer to
+ * https://drewdevault.com/2018/07/29/Wayland-shells.html.
*/
wl_list_init(&server.toplevels);
server.xdg_shell = wlr_xdg_shell_create(server.wl_display, 3);
@@ -938,10 +936,8 @@ int main(int argc, char *argv[]) {
* when the pointer moves. However, we can attach input devices to it, and
* it will generate aggregate events for all of them. In these events, we
* can choose how we want to process them, forwarding them to clients and
- * moving the cursor around. More detail on this process is described in my
- * input handling blog post:
- *
- * https://drewdevault.com/2018/07/17/Input-handling-in-wlroots.html
+ * moving the cursor around. More detail on this process is described in
+ * https://drewdevault.com/2018/07/17/Input-handling-in-wlroots.html.
*
* And more comments are sprinkled throughout the notify functions above.
*/