all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Olivier Dion via <help-guix@gnu.org>
To: Jake Shilling <shilling.jake@gmail.com>, jgart <jgart@dismail.de>,
	Guix Help <help-guix@gnu.org>
Subject: Re: geiser-edit-symbol-at-point
Date: Fri, 11 Nov 2022 12:10:10 -0500	[thread overview]
Message-ID: <874jv5o1sd.fsf@laura> (raw)
In-Reply-To: <87fsepzbe1.fsf@gmail.com>

On Fri, 11 Nov 2022, Jake Shilling <shilling.jake@gmail.com> wrote:
> Personally, I only use scheme for my guix configuration and I dont't
> think Geiser is missing anything for that perpose. After all, I want my
> dotfiles to always be evaluated within the global guile environment for
> my user.
>
> At the same time, I think that having tooling issolate some files from
> the global environment is important for any code base that is going to
> be distributed to other users. (e.g. I want SLIME/Cider to only think
> about modules that are available within the declared dependencies of a
> particular project). Of course, containerize a particular project fairly
> effectively with direnv or dir-locals.el.
>
> If I were using scheme for anything more serious, I would probably want
> something more like SLIME/Cider, but for my use case there's nothing
> missing.

I see.  Thanks for you input!

-- 
Olivier Dion
oldiob.dev


  reply	other threads:[~2022-11-11 17:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  1:35 geiser-edit-symbol-at-point jgart
2022-11-11  1:39 ` geiser-edit-symbol-at-point jgart
2022-11-11  1:44 ` geiser-edit-symbol-at-point jgart
2022-11-11 14:31   ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 16:17     ` geiser-edit-symbol-at-point Olivier Dion via
2022-11-11 16:47       ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 17:10         ` Olivier Dion via [this message]
2022-11-11 18:40     ` geiser-edit-symbol-at-point jgart
2022-11-11 20:43       ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 21:42         ` geiser-edit-symbol-at-point jgart
2022-11-11 21:45           ` geiser-edit-symbol-at-point jgart
2022-11-11 22:06           ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 22:15             ` geiser-edit-symbol-at-point jgart
2022-11-12  0:07               ` geiser-edit-symbol-at-point jgart
2022-11-12  0:12                 ` geiser-edit-symbol-at-point jgart
2022-11-12 15:48                   ` geiser-edit-symbol-at-point Jake Shilling
2022-11-14 15:01                     ` geiser-edit-symbol-at-point jgart
2022-11-14 15:16                       ` geiser-edit-symbol-at-point Jake Shilling
2022-11-14 22:38                         ` geiser-edit-symbol-at-point jgart
2022-11-15  1:31                           ` geiser-edit-symbol-at-point Jake Shilling

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874jv5o1sd.fsf@laura \
    --to=help-guix@gnu.org \
    --cc=jgart@dismail.de \
    --cc=olivier.dion@polymtl.ca \
    --cc=shilling.jake@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.