From: Bone Baboon <bone.baboon@disroot.org>
To: Gary Johnson <lambdatronic@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Start Xorg server using xinit manually
Date: Mon, 22 Mar 2021 23:22:23 -0400 [thread overview]
Message-ID: <871rc6wo40.fsf@disroot.org> (raw)
In-Reply-To: <874kh33zhu.fsf@disroot.org>
Gary Johnson writes:
> I run EXWM under Guix System.
It is good to hear that someone else is able to successfully use EXWM
with Guix.
> You don't need to manually start Xorg
> with xinit, startx, or any other command. First, make sure that you are
> installing emacs and emacs-exwm into your packages list. Also make sure
> that your services list includes %desktop-services. Here's a skeleton
> operating-system definition to build off of:
>
> (operating-system
> ...
> (packages (cons* nss-certs ; HTTPS access
> emacs
> emacs-exwm
> %base-packages))
>
> (services (cons* whatever-else
> you-want
> %desktop-services)))
>
> Start by installing this operating-system definition with the usual
> `sudo guix system reconfigure my-config.scm`.
>
> Then update your $HOME/.xsession file to include this at the end:
>
> # Start Emacs with the script here: /run/current-system/profile/bin/exwm
> exwm
>
> Finally, update $HOME/.exwm to include all your EXWM-specific Emacs Lisp
> code.
>
> When you reboot your machine, you'll be presented with a simple
> graphical login screen. Just type in your username and password for the
> user account with the updated $HOME/.xsession and $HOME/exwm files and
> log in. X will start up, your $HOME/.xsession file will be read, which
> will launch exwm. This will start up a full screen emacs instance that
> evaluates your $HOME/.exwm file and then your $HOME/.emacs.d/init.el
> file.
>
> That's all there is to it. Now you've got a fully graphically enabled
> Emacs instance running as a tiling window manager over X.
Thank you for the detailed instructions.
When I follow the instruction and boot I am taken to vt7 which has only
a blinking cursor. I never get a graphical login for X. The system is
responsive and I can switch to other virtual terminals.
On vt1 there is output like this:
New session c1 of user gdm.
Removed session c1.
New session c2 of user gdm.
Removed session c2.
New session c3 of user gdm.
Removed session c3.
...
next prev parent reply other threads:[~2021-03-23 3:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 22:05 Start Xorg server using xinit manually Bone Baboon
2021-03-21 23:05 ` jbranso
2021-03-21 23:21 ` nylxs
2021-03-22 17:14 ` Leo Famulari
[not found] ` <a03873e7-122d-fa50-21df-295112a5ede5@optonline.net>
2021-03-23 2:39 ` Leo Famulari
2021-03-21 23:58 ` Bone Baboon
2021-03-22 2:55 ` Joshua Branson
2021-03-22 16:49 ` Gary Johnson
2021-03-22 18:34 ` Vincent Legoll
2021-03-22 18:42 ` Leo Famulari
2021-03-23 3:22 ` Bone Baboon [this message]
2021-03-23 8:02 ` Sergiu Ivanov
2021-03-24 21:42 ` Bone Baboon
2021-03-23 18:37 ` Gary Johnson
2021-03-26 20:41 ` Bone Baboon
2021-03-28 17:30 ` Gary Johnson
2021-03-24 21:48 ` Bone Baboon
2021-03-22 3:29 ` Vladimir Sedach
2021-03-24 22:18 ` Bone Baboon
2021-03-25 15:20 ` Gary Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rc6wo40.fsf@disroot.org \
--to=bone.baboon@disroot.org \
--cc=help-guix@gnu.org \
--cc=lambdatronic@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).