sqrtminusone/sqrtminusone.github.io
1
0
Fork 0
mirror of https://github.com/SqrtMinusOne/sqrtminusone.github.io.git synced 2025-12-11 00:03:02 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions

feat(exwm): remove draft

Browse source
This commit is contained in:
Pavel Korytov 2022-01-03 13:55:59 +03:00
parent 6c2deadadb
commit 2d82debae7
2 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
content/posts/2022-01-03-exwm.md
View file

@ -3,7 +3,7 @@ title = "Using EXWM and perspective.el on multi-monitor setup"
author = ["Pavel Korytov"]
date = 2022-01-03
tags = ["emacs", "exwm"]
draft = true
draft = false
+++
I wrote about [Emacs and i3](https://sqrtminusone.xyz/posts/2021-10-04-emacs-i3/) integration around two months ago. Shortly after however, I decided to give EXWM another try, mainly because my largest reservation - lack of performance - seems to have been resolved by updates to the native compilation since my first attempt. Or I may have lost some sensitivity to that issue. Regardless, the second dive into EXWM thus far feels successful, and I think it's the right time to share some of my thoughts on the subject.
@ -118,11 +118,11 @@ To pull this off for various Emacs apps, it is necessary to open the right EXWM
As I said above, using perspectives in EXWM makes a lot of sense. Because all the EXWM workspace share the same buffer list (sans X windows), and because Emacs becomes the central program (for instance, it can't be easily closed), it is only natural to split the buffer list.
Another aspect of using EXWM is that it becomes very easy to work with code on multiple monitors. While it may signify some issue with the code in question if such need arises, having that possibility is still handy and it's not something easily replicable on other tiling WMs. `perspective-exwm` also presents some features here, for instance, `M-x perspective-exwm-copy-to-workspace` can be used to copy the current perspective to the adjacent monitor.
Another aspect of using EXWM is that it becomes very easy to work with code on multiple monitors. While it may signify issues with the code in question if such need arises, having that possibility is still handy and it's not something easily replicable on other tiling WMs. `perspective-exwm` also presents some features here, for instance, `M-x perspective-exwm-copy-to-workspace` can be used to copy the current perspective to the adjacent monitor.
Also, in my opinion, Emacs apps like [EMMS](https://www.gnu.org/software/emms/) and [elfeed](https://github.com/skeeto/elfeed) deserve to be on the same "level" as "proper" apps like a browser. On other tiling WMs, something like that can be done with Emacs daemon and multiple Emacs frames, but in EXWM this seems natural without much extra work.
Also, in my opinion, Emacs apps like [EMMS](https://www.gnu.org/software/emms/) and [elfeed](https://github.com/skeeto/elfeed) deserve to be on the same "level" as "proper" apps like a browser. On other tiling WMs, something like that can be done with Emacs daemon and multiple Emacs frames, but with EXWM and perspectives this seems natural without much extra work.
As for switching between X windows and perspectives, I've ended up preferring having one perspective for all X windows in the workspace, at least if these windows are full-fledged apps. For instance, all my messengers go to the workspace 3 to the perspective "comms", and I switch between them with `M-x perspective-exwm-cycle-exwm-buffers-<forward|backward>`, bound to `s-[` and `s-]`. For switching perspectives, I've bound `s-,` and `s-.`:
As for switching between X windows and perspectives, I ended up preferring to have one perspective for all X windows in the workspace, at least if these windows are full-fledged apps. For instance, all my messengers go to the workspace 3 to the perspective "comms", and I switch between them with `M-x perspective-exwm-cycle-exwm-buffers-<forward|backward>`, bound to `s-[` and `s-]`. For switching perspectives, I've bound `s-,` and `s-.`:
```emacs-lisp
(setq exwm-input-global-keys

8
org/2022-01-03-exwm.org
View file

@ -4,7 +4,7 @@
#+DATE: 2022-01-03
#+HUGO_TAGS: emacs
#+HUGO_TAGS: exwm
#+HUGO_DRAFT: true
#+HUGO_DRAFT: false
I wrote about [[https://sqrtminusone.xyz/posts/2021-10-04-emacs-i3/][Emacs and i3]] integration around two months ago. Shortly after however, I decided to give EXWM another try, mainly because my largest reservation - lack of performance - seems to have been resolved by updates to the native compilation since my first attempt. Or I may have lost some sensitivity to that issue. Regardless, the second dive into EXWM thus far feels successful, and I think it's the right time to share some of my thoughts on the subject.
@ -102,11 +102,11 @@ To pull this off for various Emacs apps, it is necessary to open the right EXWM
** Some workflow notes
As I said above, using perspectives in EXWM makes a lot of sense. Because all the EXWM workspace share the same buffer list (sans X windows), and because Emacs becomes the central program (for instance, it can't be easily closed), it is only natural to split the buffer list.
Another aspect of using EXWM is that it becomes very easy to work with code on multiple monitors. While it may signify some issue with the code in question if such need arises, having that possibility is still handy and it's not something easily replicable on other tiling WMs. =perspective-exwm= also presents some features here, for instance, =M-x perspective-exwm-copy-to-workspace= can be used to copy the current perspective to the adjacent monitor.
Another aspect of using EXWM is that it becomes very easy to work with code on multiple monitors. While it may signify issues with the code in question if such need arises, having that possibility is still handy and it's not something easily replicable on other tiling WMs. =perspective-exwm= also presents some features here, for instance, =M-x perspective-exwm-copy-to-workspace= can be used to copy the current perspective to the adjacent monitor.
Also, in my opinion, Emacs apps like [[https://www.gnu.org/software/emms/][EMMS]] and [[https://github.com/skeeto/elfeed][elfeed]] deserve to be on the same "level" as "proper" apps like a browser. On other tiling WMs, something like that can be done with Emacs daemon and multiple Emacs frames, but in EXWM this seems natural without much extra work.
Also, in my opinion, Emacs apps like [[https://www.gnu.org/software/emms/][EMMS]] and [[https://github.com/skeeto/elfeed][elfeed]] deserve to be on the same "level" as "proper" apps like a browser. On other tiling WMs, something like that can be done with Emacs daemon and multiple Emacs frames, but with EXWM and perspectives this seems natural without much extra work.
As for switching between X windows and perspectives, I've ended up preferring having one perspective for all X windows in the workspace, at least if these windows are full-fledged apps. For instance, all my messengers go to the workspace 3 to the perspective "comms", and I switch between them with =M-x perspective-exwm-cycle-exwm-buffers-<forward|backward>=, bound to =s-[= and =s-]=. For switching perspectives, I've bound =s-,= and =s-.=:
As for switching between X windows and perspectives, I ended up preferring to have one perspective for all X windows in the workspace, at least if these windows are full-fledged apps. For instance, all my messengers go to the workspace 3 to the perspective "comms", and I switch between them with =M-x perspective-exwm-cycle-exwm-buffers-<forward|backward>=, bound to =s-[= and =s-]=. For switching perspectives, I've bound =s-,= and =s-.=:
#+begin_src emacs-lisp :tangle no :noweb-ref exwm-keybindings
(setq exwm-input-global-keys
`(