From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: znavko@disroot.org, zimoun <zimon.toutoune@gmail.com>,
help-guix <help-guix@gnu.org>
Subject: Re: How to configure emacs for editing config.scm again?
Date: Thu, 03 Dec 2020 20:40:56 +0100 [thread overview]
Message-ID: <C75FCF7C-4243-4EF5-8406-B8D423E5982F@korwin-zmijowski.fr> (raw)
In-Reply-To: <070d923c9bc3025e1d201dc07a7fb1b8@disroot.org>
Maybe the Paredit extension can ne what you are looking for !
Jérémy
Le 3 décembre 2020 19:55:58 GMT+01:00, znavko@disroot.org a écrit :
>Thank you!
>
>I want emacs brushes my code making indents and auto-completing it closing parentheses.
>It does not do nothing now. Only highlights it.
>
>Could you please tell how to force emacs work deeply with my code :)
>for it becomes wonderful for further copy-pasting here in Guix Help :)) ??
>
>
>November 29, 2020 9:43 PM, "zimoun" <zimon.toutoune@gmail.com> wrote:
>
>> Hi,
>>
>> On Sun, 29 Nov 2020 at 13:16, znavko--- via <help-guix@gnu.org> wrote:
>>
>>> Hello! I have lost my way of search how to configure emacs
>>> for editing config.scm with Scheme highlight mode and parentheses
>>> completion.
>>
>> I do not know what you want exactly.
>>
>> These lines fix “M-x run-geiser” using Guile as default. And highlight
>> some Scheme code with Paredit as parenthesis tools.
>>
>> --8<---------------cut here---------------start------------->8---
>> (setq geiser-active-implementations '(guile))
>> (with-eval-after-load 'scheme
>> (add-hook 'scheme-mode-hook 'enable-paredit-mode))
>> --8<---------------cut here---------------end--------------->8---
>>
>> Hope that helps,
>> simon
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
next prev parent reply other threads:[~2020-12-03 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 13:16 How to configure emacs for editing config.scm again? znavko--- via
2020-11-29 21:36 ` zimoun
2020-12-03 18:55 ` znavko
2020-12-03 19:40 ` Jérémy Korwin-Zmijowski [this message]
2020-12-10 15:12 ` zimoun
2021-01-01 21:36 ` znavko
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=C75FCF7C-4243-4EF5-8406-B8D423E5982F@korwin-zmijowski.fr \
--to=jeremy@korwin-zmijowski.fr \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
--cc=znavko@disroot.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).