unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: "guile-user" <guile-user@gnu.org>
Subject: Re: Geiser vs. guile-mode?
Date: Thu, 20 Feb 2020 19:01:37 -0500	[thread overview]
Message-ID: <170650cb9cf.efeb26959270.2176808306828065230@zoho.com> (raw)
In-Reply-To: <871rqoc1r6.fsf@gnus.jao.io>

Hi Jose,

 ---- On Thu, 20 Feb 2020 17:50:05 -0500 Jose A. Ortega Ruiz <jao@gnu.org> wrote ----
 > On Tue, Feb 18 2020, sirgazil wrote:
 > 
 > > 2. Immediate availability of new symbols after importing a module.
 > 
 > I'm not sure what you mean here by "importing a module".  Loading or
 > compiling a given module makes transitively availabe all the symbols in
 > modules it imports, provided you're in the context of a module where
 > they're visible.  If you mean automatically loading a module when you
 > open its file in emacs, that's just
 > 
 >     (add-hook 'geiser-mode-hook #'geiser-compile-current-buffer)
 > 
 > But possibly you mean something else?

By importing a module I mean adding it to (use-modules ...) while working on a Guile Scheme file.

But now that you mention opening a file, I think the complete behavior I would expect would be that doing the following,

1. Visit path/to/file.scm
2. M-x run-guile

would make symbols of all existing modules in (use-modules ...) to become available for autocomplete, autodoc, etc. And

3. Add more modules to (use-modules ...) during my work

would also make the symbols of the new modules available for autocomplete, etc.

Currently, I have to evaluate the buffer manually (C-c C-b) for these things to happen.



  reply	other threads:[~2020-02-21  0:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 15:18 Geiser vs. guile-mode? Pierre Neidhardt
2020-02-04 16:16 ` Jérémy Korwin-Zmijowski
2020-02-04 16:40   ` Pierre Neidhardt
2020-02-07 13:50     ` Pierre Neidhardt
2020-02-07 16:19       ` Jérémy Korwin-Zmijowski
2020-02-07 16:30         ` Matt Wette
2020-02-07 17:50           ` sirgazil
2020-02-07 22:24             ` Matt Wette
2020-02-08 18:14               ` Ricardo Wurmus
2020-02-08 18:59                 ` Matt Wette
     [not found]                   ` <F5513F8F-F6A8-4AAC-8AF3-C91991CE8E40@korwin-zmijowski.fr>
2020-02-13  9:38                     ` Jérémy Korwin-Zmijowski
2020-02-18 23:53             ` sirgazil
2020-02-19 14:16               ` Ricardo Wurmus
2020-02-20 14:24                 ` sirgazil
2020-02-20 22:50               ` Jose A. Ortega Ruiz
2020-02-21  0:01                 ` sirgazil [this message]
2020-02-21  1:44                   ` Jose A. Ortega Ruiz
2020-02-21  8:41                     ` Arne Babenhauserheide
2020-02-21 22:57                       ` Jose A. Ortega Ruiz
2020-02-08 16:30         ` Pierre Neidhardt
2020-02-07 23:44       ` Jose A. Ortega Ruiz
2020-02-14  8:38       ` Pierre Neidhardt

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=170650cb9cf.efeb26959270.2176808306828065230@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=guile-user@gnu.org \
    --cc=jao@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.
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).