unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: 54704@debbugs.gnu.org
Subject: bug#54704: [PATCH] 29.0.50; Broken code assistance for Scheme libraries
Date: Sat, 24 Dec 2022 14:15:46 +0200	[thread overview]
Message-ID: <83a63d5765.fsf@gnu.org> (raw)
In-Reply-To: <m21qoplk0z.fsf@me.com> (bug-gnu-emacs@gnu.org)

> Date: Sat, 24 Dec 2022 01:31:24 +0100
> From:  Rudolf Adamkovič via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Please see the attached patch that makes Emacs recognize R6RS/R7RS
> library files, as well as, makes Emacs recognize their members.

Thanks.

> ++++

The "+++" mark means that the manuals have been updated with this
information.  I don't think this is the case, and we don't have any
manuals for the Scheme mode, right?  So this should be "---" instead.

> +*** Auto-detection of Scheme library files

Heading lines in NEWS should end with a period.

> +Emacs now automatically enables the Scheme mode for R6RS library
> +sources ('.sls') and R7RS library definitions ('.sld').

"source files" and "library definition files", right?

> ++++
> +*** Imenu members for R6RS and R7RS library members

Same comments here.





  reply	other threads:[~2022-12-24 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  5:33 bug#54704: 29.0.50; Broken code assistance for Scheme libraries Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-24  0:31 ` bug#54704: [PATCH] " Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-24 12:15   ` Eli Zaretskii [this message]
2022-12-24 22:32     ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-26 12:49       ` Eli Zaretskii
2022-12-27  0:48         ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-27 14:00           ` Eli Zaretskii

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=83a63d5765.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54704@debbugs.gnu.org \
    --cc=salutis@me.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).