From: Oleg Pykhalov <go.wigust@gmail.com>
To: 27758@debbugs.gnu.org
Subject: [bug#27758] [PATCH] gnu: Add emacs-aggressive-indent-mode.
Date: Tue, 18 Jul 2017 20:29:18 +0300 [thread overview]
Message-ID: <20170718172918.6888-1-go.wigust@gmail.com> (raw)
* gnu/packages/build-tools.scm (emacs-aggressive-indent-mode): New variable.
---
gnu/packages/emacs.scm | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
index 43de13057..b5b5315fb 100644
--- a/gnu/packages/emacs.scm
+++ b/gnu/packages/emacs.scm
@@ -5200,3 +5200,30 @@ src block.")
"@code{emacs-emamux} lets Emacs interact with the @code{tmux} terminal
multiplexer.")
(license license:gpl3+)))
+
+(define-public emacs-aggressive-indent-mode
+ (package
+ (name "emacs-aggressive-indent-mode")
+ (version "1.8.3")
+ (source (origin
+ (method url-fetch)
+ (uri (string-append
+ "https://github.com/Malabarba/aggressive-indent-mode"
+ "/archive/" version ".tar.gz"))
+ (file-name (string-append name "-" version ".tar.gz"))
+ (sha256
+ (base32
+ "093qn49bi39050clqdj6rjw0h9dh93qsajb029axcbah7m1c9aws"))))
+ (build-system emacs-build-system)
+ (home-page "https://github.com/Malabarba/aggressive-indent-mode")
+ (synopsis "Emacs minor mode that keeps your code always indented")
+ (description
+ "@code{electric-indent-mode} is enough to keep your code nicely aligned
+when all you do is type. However, once you start shifting blocks around,
+transposing lines, or slurping and barfing sexps, indentation is bound to go
+wrong.
+
+@code{aggressive-indent-mode} is a minor mode that keeps your code always
+indented. It reindents after every change, making it more reliable than
+electric-indent-mode.")
+ (license license:gpl3+)))
--
2.13.2
next reply other threads:[~2017-07-18 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 17:29 Oleg Pykhalov [this message]
2017-07-19 5:49 ` [bug#27758] Switch to elpa Oleg Pykhalov
2017-07-19 6:32 ` Jan Nieuwenhuizen
2017-07-19 7:56 ` Oleg Pykhalov
2017-07-19 8:59 ` bug#27758: " Jan Nieuwenhuizen
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=20170718172918.6888-1-go.wigust@gmail.com \
--to=go.wigust@gmail.com \
--cc=27758@debbugs.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.
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).