From: Alex Kost <alezost@gmail.com>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: guix emacs mode
Date: Sat, 29 Oct 2016 12:07:45 +0300 [thread overview]
Message-ID: <87h97vy13y.fsf@gmail.com> (raw)
In-Reply-To: 87funglqri.fsf@we.make.ritual.n0.is
ng0 (2016-10-28 10:19 +0000) wrote:
> Alex Kost <alezost@gmail.com> writes:
>
>> ng0 (2016-10-28 08:30 +0000) wrote:
[...]
>>> Different issue, but somehow related: Could we move the emacs
>>> specific settings into an emacs mode if emacs modes can detect
>>> some common structure or however we specify that the current file
>>> which is edited is guix and not guile/scm alone?
>>
>> Sorry, I don't understand the question. What does «move the emacs
>> specific settings into an emacs mode» mean?
>
> I don't understand much, well to be honest: nothing, on how modes
> in emacs work. I meant that we maybe could move whatever the
> .dir-locals.el sets into some external modules/files/set if
> possible at all.
Ah, now I see. The purpose of ".dir-locals.el" is to set some variables
locally for the current project (the contents of the current directory).
I think it doesn't make sense to move dir-locals anywhere, as it is used
to set up emacs (to set fill-column, to disable TABs, etc.) when you
edit guix code from a git checkout.
> It probably works for gentoo .ebuild because
> they have a different file extension than bash, but at their core
> it is bash (if I don't mix it up right now). The sentence below
> looks like this will not work at all for guix.
>
>> Also there is no difference between some guix ".scm" file and a usual
>> guile ".scm" file.
--
Alex
prev parent reply other threads:[~2016-10-29 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 21:31 vim modelines for guix repository ng0
2016-10-23 5:14 ` Efraim Flashner
2016-10-23 16:20 ` ng0
2016-10-28 8:30 ` guix emacs mode (was: Re: vim modelines for guix repository) ng0
2016-10-28 9:47 ` guix emacs mode Alex Kost
2016-10-28 10:19 ` ng0
2016-10-29 9:07 ` Alex Kost [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h97vy13y.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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/guix.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).