unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: emacs-devel@gnu.org
Subject: Yet another global/gtags package into elpa..
Date: Tue, 29 Mar 2022 01:27:54 +0200	[thread overview]
Message-ID: <20220328232754.feeavepjtqauvnv5@Ergus> (raw)
In-Reply-To: 20220328232754.feeavepjtqauvnv5.ref@Ergus

Hi:

After many years dealing with issues (specially with tramp) with all the
global/gtags packages around (agtags, gxref, counsel-gtags, ggtags and
global-tags) I definitively implemented my own simpler one only with
emacs internal infrastructure, and I am wondering if it may be fine to
add it to elpa.  The package could be even added to vanilla due to it's
simplicity and because fully integrates into the emacs ecosystem.

The package adds backends for xref, project and imenu with less than 350
lines and fully supporting tramp in an optimized way (checking the
executable availability in remote nodes and respecting the user configs
including connection-local-variables if set). There is just some missing
documentation but I will add it when I have some time.

If you consider that it is fine to add it; please just give me the
steps.

https://github.com/Ergus/global-xref

Best,
Ergus



       reply	other threads:[~2022-03-28 23:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220328232754.feeavepjtqauvnv5.ref@Ergus>
2022-03-28 23:27 ` Ergus [this message]
2022-03-29  8:21   ` Yet another global/gtags package into elpa Michael Albinus
2022-03-29  9:56     ` Ergus
2022-03-29 10:08       ` Michael Albinus
2022-03-29 12:16     ` Dmitry Gutov
2022-03-29 16:07       ` Ergus
2022-03-29 16:16         ` Dmitry Gutov
2022-03-29 17:15           ` Ergus
2022-04-02  0:47   ` Daniel Martín

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20220328232754.feeavepjtqauvnv5@Ergus \
    --to=spacibba@aol.com \
    --cc=emacs-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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).