From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Guile text editor
Date: Wed, 28 Nov 2018 19:54:30 +0200 [thread overview]
Message-ID: <20181128175430.GD28059@macbook41> (raw)
In-Reply-To: <878t1d15hv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
On Wed, Nov 28, 2018 at 06:22:52PM +0100, Ludovic Courtès wrote:
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > On Wed, Nov 28, 2018 at 11:59:15AM +0100, Pierre Neidhardt wrote:
> >> I suspect most Guix developers use Emacs with the Geiser mode for enhanced
> >> Scheme integration.
> >>
> >> A segfault on "C-x u"? (you mean undo?) Very strange. Can you reproduce a
> >> specific recipe? Is it just in Guile files? What minor modes are you running?
> >> Is it terminal or graphical Emacs?
> >>
> >> Note that if you have a US QWERTY layout, you might prefer "C-/" to undo.
> >>
> >
> > I use vim with no highlighting. We also have edi as a code editor. I
> > haven't tried it out too much though, or with guix.
>
> I believe Vim provides syntax highlighting and autoidenting for Scheme,
> as well as paredit.vim:
>
> https://www.gnu.org/software/guix/manual/en/html_node/Formatting-Code.html
vim does have a scheme module, in
$out/share/vim/vim81/syntax/scheme.vim, and guix's code base gets
recongized as scheme code. I meant that when I have my cursor over a
parenthesis it highlights the other side, but that they're not color
coded or something.
The indenting does work fairly well with the default scheme.vim that
learning vimscript for the purpose of creating a guix.vim has been
backburnered for more than 2 years.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-28 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 10:22 Guile text editor znavko
2018-11-28 10:59 ` Pierre Neidhardt
2018-11-28 11:08 ` Efraim Flashner
2018-11-28 12:00 ` znavko
2018-11-28 12:15 ` Pierre Neidhardt
2018-11-28 17:22 ` Ludovic Courtès
2018-11-28 17:54 ` Efraim Flashner [this message]
2018-11-28 12:34 ` Catonano
2018-11-28 16:12 ` znavko
2018-11-29 12:31 ` Joshua Branson
2018-12-02 4:28 ` Maxim Cournoyer
2018-11-28 12:45 ` hub.lombard
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=20181128175430.GD28059@macbook41 \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=ludo@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).