From: Alex Kost <alezost@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add emacs-clojure-mode
Date: Thu, 19 May 2016 11:54:47 +0300 [thread overview]
Message-ID: <878tz61l7s.fsf@gmail.com> (raw)
In-Reply-To: <CAJ98PDyC88XNBymw5b_E-dM6dAvFn+Fdss-VBRNiw=PRNw52jg@mail.gmail.com> (catonano@gmail.com's message of "Wed, 18 May 2016 17:09:43 +0200")
Catonano (2016-05-18 18:09 +0300) wrote:
> From 6dc8470baf3493a93da3e3358136e5c9860d4e3a Mon Sep 17 00:00:00 2001
> From: humanitiesNerd <catonano@gmail.com>
> Date: Wed, 18 May 2016 15:41:47 +0200
> Subject: gnu: Add emacs-clojure-mode
^
This is a nitpick of course, but we put a period here...
> * gnu/packages/emacs.scm (emacs-clojure-mode): New variable
^
... and here.
> ---
> diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
> index 32ed722..fb07bc7 100644
> --- a/gnu/packages/emacs.scm
> +++ b/gnu/packages/emacs.scm
> @@ -1612,3 +1612,41 @@ It is built on top of the custom theme support in Emacs 24 or later.")
> (license license:gpl3+)))
>
>
> +(define-public emacs-clojure-mode
> + (package
> + (name "emacs-clojure-mode")
> + (version "5.3.0")
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/clojure-emacs/clojure-mode.git")
> + (commit "8ef7127da214cb7fd4b47fc943462f2a8bfb8f85")))
Is there a reason to use 'git-fetch'? I think a usual 'url-fetch' is
fine as there is:
<https://github.com/clojure-emacs/clojure-mode/archive/5.3.0.tar.gz>.
> + (file-name (string-append name "-" version "-checkout"))
> + (sha256
> + (base32
> + "1x7nl5wzcah9hnlj5jfd3y5604w60zcqcw1nn6vw335c2vzzissj"))))
> + (build-system emacs-build-system)
> + (home-page "http://github.com/clojure-emacs/clojure-mode")
> + (synopsis "Major mode for Clojure code")
> + (description
> + "Provides font-lock, indentation, navigation and basic refactoring for the
We use full sentences for descriptions, like this: "This emacs package
provides ..."
> +Clojure programming language (http://clojure.org).
Since we use texinfo to format descriptions, it is better to write:
@uref{http://clojure.org, Clojure programming language}
> +
> +Using clojure-mode with paredit or smartparens is highly recommended.
I think this description is too verbose. I would remove all the text
below.
> +
> +Here are some example configurations:
> +
> + ;; require or autoload paredit-mode
> + (add-hook 'clojure-mode-hook #'paredit-mode)
> +
> + ;; require or autoload smartparens
> + (add-hook 'clojure-mode-hook #'smartparens-strict-mode)
> +
> +See inf-clojure (http://github.com/clojure-emacs/inf-clojure) for
> +basic interaction with Clojure subprocesses.
> +
> +See CIDER (http://github.com/clojure-emacs/cider) for
> +better interaction with subprocesses via nREPL.
> +")
> + (license license:gpl3+)))
--
Alex
next prev parent reply other threads:[~2016-05-19 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 15:09 [PATCH] gnu: Add emacs-clojure-mode Catonano
2016-05-19 8:54 ` Alex Kost [this message]
2016-05-19 10:20 ` Catonano
2016-05-24 8:51 ` Alex Kost
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=878tz61l7s.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=catonano@gmail.com \
--cc=guix-devel@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 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.