unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: sirgazil <sirgazil@zoho.com>
Cc: 39888@debbugs.gnu.org
Subject: bug#39888: [Feature Request] Add a guile-mode
Date: Thu, 21 Jan 2021 17:15:10 +0100	[thread overview]
Message-ID: <874kja8dwx.fsf@gnus.org> (raw)
In-Reply-To: <170a1a30f8d.cea910e265266.2024994101319861714@zoho.com> (sirgazil@zoho.com's message of "Tue, 03 Mar 2020 13:23:03 -0500")

sirgazil <sirgazil@zoho.com> writes:

> In essence, I would like to have, by default, what is already provided
> by the following Emacs-related projects:
>
> + geiser
> + paredit
> + rainbow-delimiters
> + flycheck (Guile Studio has a Guile Scheme checker)
>
> Additionally, I'd like to have the following features that I think are missing:
>
> + Warn about unused imported modules.
> + Make symbols of newly imported modules available automatically for
> auto-complete, show symbol documentation, jump to definition, etc.
>
> So, when visiting a Guile Scheme file, I'd like to have these tools
> available automatically, as if I were using an IDE.

This feature request (if I understand it correctly) is about adding more
packages to the Emacs tree -- but we don't really do that for packages
like this that are already in some ELPA or other.  (But with the
gnu-elpa package, Emacs will offer to load packages automatically, which
may help.)

The other part of the request (warn about unused modules) etc are
somewhat vague, and probably won't lead to any progress by having open
in the Emacs issue tracker, so I'm closing this feature request.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-01-21 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 18:23 bug#39888: [Feature Request] Add a guile-mode sirgazil via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-21 16:15 ` Lars Ingebrigtsen [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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=874kja8dwx.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=39888@debbugs.gnu.org \
    --cc=sirgazil@zoho.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/emacs.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).