unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "André A. Gomes" <andremegafone@gmail.com>
To: calcium <calcium@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: EXWM
Date: Mon, 03 Jan 2022 23:03:44 +0300	[thread overview]
Message-ID: <87r19od1sv.fsf@gmail.com> (raw)
In-Reply-To: <2409e017-bcc2-0937-2dbe-11654f7f9639@disroot.org> (calcium@disroot.org's message of "Sat, 1 Jan 2022 20:19:55 +0100")

calcium <calcium@disroot.org> writes:

> I was totally at lost when I started my emacs/exwm session and tried to `find-file' only to be redirected to an 'ido-find-file` with whom I don't know how to navigate.
>
> In the moment, it felt very intrusive for me and I was very afraid to be unable to control my emacs because I have set all my emacs's keybindings to non-standard keys ((in a modal way (à la vim) but using my own custom modals) and without honoring the `C-c' convetion.) and I don't know how to navigate emacs using the default key bindings.
>
> Luckly, this time (because packages can evolve to add more default key bindings), it was just the annoyance of ido that affected me.
>
>
> I was thankfully able to understand what was going on by finding the Guix-devel archive discussing this issue.
>
> I think that if we choose to keep things as they are, a simple fix that would help next users know what is going on without having to find an archived mailing list :
>
> a ) being more explicit in messages in both cases like :
>     (message "no \"~/.exwm\" elisp configuration found to setup exwm. "
>              "Falling back to executing the default config using `(exwm-config-default)'")
>     (message "executing the elisp found at \"~/.exwm\"")
> b ) while still keeping the explicit messages, creating the ~/.exwm file when it doesn't exist populated with guix's choice of default settings (so that the user can read and tweak his config)
>
> Because the message thrown by the snippet bellow is not enough at all.
>   
>
> (cond ((file-exists-p "~/.exwm") (load-file "~/.exwm"))
>        ((not (featurep (quote exwm)))
>         (require (quote exwm))
>         (require (quote exwm-config))
>         (exwm-config-default)
>         (message (concat "exwm configuration not found. "
>                          "Falling back to default configuration..."))))
>

I feel you (been there, felt that).

I tried, without success, to raise awareness about the issue (perhaps in
the archived thread you mention).  Sadly, no one agreed or tried to
prove me wrong.

I wrote a very simple and sane EXWM package definition, and you can find
it here:

https://git.sr.ht/~aadcg/aadcg-guix-channel/tree/master/item/packages/aadcg-emacs-xyz.scm#L147

I could send it as a patch, but without interest from the
developers/maintainers it makes little sense.


-- 
André A. Gomes
"Free Thought, Free World"


  reply	other threads:[~2022-01-03 20:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 19:19 EXWM calcium
2022-01-03 20:03 ` André A. Gomes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-04 14:33 EXWM André A. Gomes
2021-10-08  9:57 ` EXWM Arun Isaac
2021-10-08 10:21   ` EXWM Jan Nieuwenhuizen
2021-10-08 10:55     ` EXWM Arun Isaac
2021-10-10 13:16       ` EXWM Ludovic Courtès
2021-10-15  7:15         ` EXWM André A. Gomes
2021-10-15  6:54     ` EXWM André A. Gomes
2021-10-08 10:59 ` EXWM Arun Isaac
2021-10-15  7:38   ` EXWM André A. Gomes
2021-10-16 16:03     ` EXWM Arun Isaac
2021-10-18  5:29       ` EXWM Jan Nieuwenhuizen
2021-10-18 16:44         ` EXWM André A. Gomes
2021-10-20  7:27           ` EXWM Jan Nieuwenhuizen
2021-10-22 10:25             ` EXWM André A. Gomes
2021-10-22 10:37               ` EXWM Arun Isaac
2021-10-22 10:52                 ` EXWM André A. Gomes
2021-10-22 18:55               ` EXWM Ricardo Wurmus
2021-10-22 19:36                 ` EXWM André A. Gomes
2021-10-22 20:15                   ` EXWM André A. Gomes
2021-10-23 15:02                     ` EXWM André A. Gomes

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=87r19od1sv.fsf@gmail.com \
    --to=andremegafone@gmail.com \
    --cc=calcium@disroot.org \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).