unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: "Ricardo G. Herdt" <r.herdt@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: Indentation with inline comments in Emacs
Date: Mon, 18 Apr 2022 14:09:16 +0000	[thread overview]
Message-ID: <P_PzNQjAs7QCWbu_IWbM8JPVe4lz4Ytis_bcXWiajSuLLzgtgsb0yYiz3VSd42pnR34m4cWZn0y-Z1nXEtBbV946__A4CVXwP3F2mBP9H_I=@protonmail.com> (raw)
In-Reply-To: <ac0b73e48075801fd357dd8cbe5248da@posteo.de>


[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]

On Monday, April 18th, 2022 at 1:33 PM, Ricardo G. Herdt <r.herdt@posteo.de> wrote:

> actually the doc-strings are available during runtime using '(ice-9
> documentation)', so theoretically it is not restricted to Emacs. In fact
> I have been working on my spare time on a LSP server for scheme
> (together with a emacs-lsp and a VS Code extension), and documentation
> of guile functions was quite straight-forward to implement. It's not yet
> ready for prime time though.

That sounds great.

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

  reply	other threads:[~2022-04-18 14:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 12:12 Indentation with inline comments in Emacs Zelphir Kaltstahl
2022-04-16 14:57 ` Jérémy Korwin-Zmijowski
2022-04-17 10:49   ` Zelphir Kaltstahl
2022-04-17 13:44     ` Luis Felipe
2022-04-18 10:48       ` Zelphir Kaltstahl
2022-04-18 13:33         ` Ricardo G. Herdt
2022-04-18 14:09           ` Luis Felipe [this message]
2022-04-18 14:05         ` Luis Felipe
2022-04-17  3:03 ` Taylan Kammer
2022-04-17 11:06   ` Zelphir Kaltstahl
2022-04-17 14:58     ` Maxime Devos
2022-04-18 10:49       ` Zelphir Kaltstahl

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='P_PzNQjAs7QCWbu_IWbM8JPVe4lz4Ytis_bcXWiajSuLLzgtgsb0yYiz3VSd42pnR34m4cWZn0y-Z1nXEtBbV946__A4CVXwP3F2mBP9H_I=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=guile-user@gnu.org \
    --cc=r.herdt@posteo.de \
    /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).