all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: indent with emacs batch mode
Date: Sun, 08 Jan 2017 16:48:06 +0300	[thread overview]
Message-ID: <87vatp1x49.fsf@gmail.com> (raw)
In-Reply-To: <87lgumd0ro.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 07 Jan 2017 22:21:31 +0100")

Ricardo Wurmus (2017-01-07 22:21 +0100) wrote:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Alex Kost <alezost@gmail.com> skribis:
>>
>>> Since a user knows what file (s)he wants modify, I think it is better to
>>> avoid starting the REPL, so it will be *much faster*.  After all, I
>>> would do it like this:
>>
>> Sounds cool!  (The only downside is that it would indent the whole file
>> so the submitter might have to undo indentation changes in other parts
>> of the file before committing.)
>
> But we’re using “indent-sexp”, which only indents the expression that
> belongs to the matched package name.

Right, Ludo you missunderstood: only the specified package will be
indented.

>> What about committing it as a script, say
>> etc/devel/indent-scheme-code.sh, and mention it under “Submitting
>> Patches” and “Formatting Code”?
>
> Sounds good to me.  Alex, would you like to do it?

Sorry, I wouldn't :-)

-- 
Alex

      reply	other threads:[~2017-01-08 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 15:29 indent with emacs batch mode Ricardo Wurmus
2017-01-07  5:59 ` Alex Kost
2017-01-07  7:25   ` Ricardo Wurmus
2017-01-08 13:32     ` Alex Kost
2017-01-12 14:01       ` Ludovic Courtès
2017-05-28 16:54         ` Andreas Enge
2017-01-07 21:17   ` Ludovic Courtès
2017-01-07 21:21     ` Ricardo Wurmus
2017-01-08 13:48       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vatp1x49.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.