all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 28830@debbugs.gnu.org
Subject: [bug#28830] [PATCH] gnu: Add emacs-ggtags.
Date: Mon, 16 Oct 2017 06:51:31 +0100	[thread overview]
Message-ID: <20171016065131.4e838899@cbaines.net> (raw)
In-Reply-To: <87o9pa3xti.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3003 bytes --]

On Sat, 14 Oct 2017 12:04:09 +0300
Oleg Pykhalov <go.wigust@gmail.com> wrote:

> From bcd267046dc0ab8e87356519d3e3c60a96f7d5a4 Mon Sep 17 00:00:00 2001
> From: Oleg Pykhalov <go.wigust@gmail.com>
> Date: Sat, 14 Oct 2017 12:03:23 +0300
> Subject: [PATCH] gnu: Add emacs-ggtags.
> 
> * gnu/packages/emacs.scm (emacs-ggtags): New variable.
> ---
>  gnu/packages/emacs.scm | 45 +++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 45 insertions(+)
> 
> diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
> index 66f0a2ebe..62338e998 100644
> --- a/gnu/packages/emacs.scm
> +++ b/gnu/packages/emacs.scm
> @@ -1206,6 +1206,51 @@ Using emacs-direnv means that programs started from Emacs will use the
>  environment set through Direnv.")
>      (license license:gpl3+)))
>  
> +(define-public emacs-ggtags
> +  (package
> +    (name "emacs-ggtags")
> +    (version "0.8.12")
> +    (source
> +     (origin
> +       (method url-fetch)
> +       (uri (string-append "http://elpa.gnu.org/packages/ggtags-"
> +                           version ".el"))
> +       (sha256
> +        (base32
> +         "0ny3llk021g6r0s75xdm4hzpbxv393ddm2r6f2xdk8kqnq4gnirp"))))
> +    (build-system emacs-build-system)
> +    (home-page "https://github.com/leoliu/ggtags")
> +    (synopsis "Frontend to GNU Global source code tagging system")

I'd suggest putting "the" in here, so "Frontend to the GNU Global ...",
as I think that reads better.

> +    (description "@code{ggtags} provides a frontend to GNU Global source code
> +tagging system.
> +
> +Features:
> +
> +@itemize
> +@item Build on @code{compile.el} for asynchronicity and its large feature-set.
> +@item Automatically update Global's tag files when needed with tuning for
> +large source trees.
> +@item Intuitive navigation among multiple matches with mode-line display of
> +current match, total matches and exit status.
> +@item Read tag with completion.
> +@item Show definition at point.
> +@item Jump to #include files.
> +@item Support search history and saving a search to register/bookmark.
> +@item Query replace.
> +@item Manage Global's environment variables on a per-project basis.
> +@item Highlight (definition) tag at point.
> +@item Abbreviated display of file names.
> +@item Support all Global search backends: @code{grep}, @code{idutils}, etc.
> +@item Support exuberant ctags @url{http://ctags.sourceforge.net/} and
> +@code{pygments} backend.
> +@item Support all Global's output formats: @code{grep}, @code{ctags-x},
> +@code{cscope} etc.
> +@item Support projects on remote hosts (e.g. via @code{tramp}).
> +@item Support eldoc.
> +@item Search @code{GTAGSLIBPATH} for references and symbols.
> +@end itemize\n")
> +    (license license:gpl3+)))
> +
>  (define-public emacs-go-mode
>    (package
>      (name "emacs-go-mode")

Similarly with "the GNU Global" in the description. What do you think?
Apart from that, this looks fine to me :)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply	other threads:[~2017-10-16  5:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-14  9:04 [bug#28830] [PATCH] gnu: Add emacs-ggtags Oleg Pykhalov
2017-10-16  5:51 ` Christopher Baines [this message]
2017-10-16 10:22   ` Oleg Pykhalov
2017-10-31  8:22     ` Christopher Baines
2017-10-31 17:11       ` bug#28830: " Oleg Pykhalov
2017-10-31 19:39       ` [bug#28830] " Tobias Geerinckx-Rice

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=20171016065131.4e838899@cbaines.net \
    --to=mail@cbaines.net \
    --cc=28830@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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.