search

everard / rosewm

A lightweight Wayland Compositor (WLRoots-based)
GNU General Public License v3.0
7 stars 0 forks source link

How to launch and basic configuration? #2

Open lidgnulinux opened 2 years ago

lidgnulinux commented 2 years ago

hello, Any special way to launch rosewm from tty ? I tried directly run the binary : 

$ rosewm

and use dbus-run-session : 

$ dbus-run-session /usr/local/bin/rosewm

but it's not launched.

everard commented 2 years ago

Hi! No, there is no special way. You'll need to make sure that you have at least these 2 config files, though:

  1. $HOME/.config/rosewm/fonts
  2. $HOME/.config/rosewm/system_terminal

The fonts file must contain paths to font files which you want to use. The system_terminal file - null-character-separated list of command line arguments which could start a terminal emulator of your choice. Examples of such files are in the CONFIGURATION section of README.md

everard commented 2 years ago

And please bear in mind that this is still a work in progress:

  1. I haven't written documentation for users yet.
  2. I'm currently writing an overview for developers.
  3. This repo contains only the Window Manager itself, there are no secondary apps in here (no dmenu-like dispatcher, no panel, no screen locker, etc.)
lidgnulinux commented 2 years ago

Thanks @everard for the clear answer.

lidgnulinux commented 1 month ago

Hello, sorry to reopen the issue, it's two year later and I still can't launch rosewm. Could you give me a detail step to launch and the config ?

everard commented 1 month ago

Hi, sorry for the late reply. Attaching minimal config example (uses LiberationSans and FontAwesome fonts, kitty terminal) rosewm.zip

everard commented 1 month ago

You'll need to extract this archive into your .config directory, and then edit the "fonts" and "system_terminal" files. the "fonts" file contains full paths to the font files which are going to be used by the compositor.

The "system_terminal" file contains command which will be executed when user requests terminal execution (by default CMD+ENTER). The command must be null-terminated, meaning the command and its arguments are separated by the \x00 character.