unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jake Shilling <shilling.jake@gmail.com>
To: Olivier Dion <olivier.dion@polymtl.ca>, jgart <jgart@dismail.de>,
	Guix Help <help-guix@gnu.org>
Subject: Re: geiser-edit-symbol-at-point
Date: Fri, 11 Nov 2022 11:47:18 -0500	[thread overview]
Message-ID: <87fsepzbe1.fsf@gmail.com> (raw)
In-Reply-To: <877d01o47o.fsf@laura>

[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]


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. 

On 2022-11-11 11:17, Olivier Dion wrote:

> On Fri, 11 Nov 2022, Jake Shilling <shilling.jake@gmail.com> wrote:
>> I don't really have anything helpful to add, except that I believe
>> geiser doesn't work the way SLIME or LSP does, where there's some
>> process parsing a project with semantic awareness. Instead it just
>> launches guile (or some other repl) and parses the prompt string. As far
>> as I know it is really just sending text back and forth between a
>> scheme-mode buffer and a runing repl.
>
> Would this kind of tool be more useful than Geiser?  I find that
> auto-parsing of the project could really help refactoring stuff and jump
> to definition without having to evaluate every module.  The REPL can
> stay there for on the fly modification of the program of course, but
> perhaps a communication would be necessary between the auto-parser and
> the REPL.  What do you think?

-- 
Best regards,
Jake Shilling

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2022-11-11 16:47 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       ` Jake Shilling [this message]
2022-11-11 17:10         ` geiser-edit-symbol-at-point Olivier Dion via
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

  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=87fsepzbe1.fsf@gmail.com \
    --to=shilling.jake@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.de \
    --cc=olivier.dion@polymtl.ca \
    /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).