From: Feng Shu <tumashu@163.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Suggest improve emacs setting in 'The Perfect Setup'
Date: Sun, 08 Jan 2023 06:43:41 +0800 [thread overview]
Message-ID: <87tu1255k2.fsf@163.com> (raw)
In-Reply-To: <875ydjir4j.fsf@gmail.com> (Simon Tournier's message of "Fri, 06 Jan 2023 17:07:08 +0100")
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi,
>
> Thanks for sharing. Interesting to see other config.
>
>
> On Fri, 30 Dec 2022 at 08:54, Feng Shu <tumashu@163.com> wrote:
>
>> ;; ** Let geiser-guile use 'guix repl'
>> (setq geiser-guile-binary (list "guix" "repl" "-L" eh-geeguix-dir))
>
> Be careful, this can bite you. :-) Guile is run with --no-auto-compile
> so the debugger is probably not working as expected. See [1,2].
>
> 1: https://yhetil.org/guix/86o7ss1u49.fsf@gmail.com2: https://yhetil.org/guix/87lenve3t2.fsf@gnu.org
>
>
>> ;; ** Get guix dir installed by 'guix pull'.
>> (defun eh-guix-dir ()
>> (file-name-as-directory
>> (cl-find-if
>> (lambda (dir)
>> (file-exists-p (expand-file-name "guix.scm" dir)))
>> (directory-files
>> (expand-file-name "~/.cache/guix/checkouts/")
>> t))))
>
> Well, I do not know what you do with this but if you manually write in
> this directory, then “guix pull” could be then broken.
I just read tempel templates and copyright.el from this directory.
maybe I should read them from another dir, but I do not know where,
in "~/.config/guix/current/share" seem can not find them.
>
>
> Cheers,
> simon
--
prev parent reply other threads:[~2023-01-07 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 0:54 Suggest improve emacs setting in 'The Perfect Setup' Feng Shu
2022-12-31 23:17 ` Joshua Branson
2023-01-01 19:53 ` Feng Shu
2023-01-01 20:35 ` jbranso
2023-01-01 21:05 ` Feng Shu
2023-01-02 21:36 ` jbranso
2023-01-03 1:18 ` Feng Shu
2023-06-08 22:08 ` Mekeor Melire
2023-01-06 16:07 ` Simon Tournier
2023-01-07 22:43 ` Feng Shu [this message]
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=87tu1255k2.fsf@163.com \
--to=tumashu@163.com \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).