From: fis trivial <ybbs.daans@hotmail.com>
To: Tim Gesthuizen <tim.gesthuizen@yahoo.de>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: emacs irony-mode
Date: Mon, 13 Aug 2018 19:23:21 +0000 [thread overview]
Message-ID: <BLUPR16MB05002330E9926C7D7D865E2B92390@BLUPR16MB0500.namprd16.prod.outlook.com> (raw)
In-Reply-To: <aae4d5c5-1c15-6ce0-f94c-f82f68e8f438@yahoo.de>
Tim Gesthuizen writes:
> Hi,
>
> I am trying to package irony-mode for emacs and quickly
>
> noticed that I need more input on how packages like this should
>
> be seperated or handled.
>
> Maybe somebody wants to take my approach and integrate the
>
> package definition(s) into guix or provide some information
>
> towards how such packages should be integrated.
>
> You find the script with my package definition attached.
>
> Mentioning packages with similar problems would also be helpful.
>
>
> Best regards,
>
> Tim Gesthuizen
I'm not helping. But there are other candidates than irony-mode now. For two
scenarios:
1. You have a way to generate compilation database:
Use cquery with lsp-mode. cquery is a fully featured c/c++/objective-c
language server.
or
Use rtags. The server is packaged in Guix. Personal experience tells
that cquery is better at its job. But you can be the judge. :)
2. You can't generate a compilation database:
Just use company-clang and flycheck, which combined should do everything
irony could.
If this doesn't convince you to give up irony-mode. Then your packaging looks
good to me. If there really is room to improve, maybe you can extract the
"source" part out? Note that I'm not proficient as others here.
--
Jiaming
next prev parent reply other threads:[~2018-08-13 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 18:53 emacs irony-mode Tim Gesthuizen
2018-08-13 10:30 ` Pierre Neidhardt
2018-08-13 18:04 ` Tim Gesthuizen
2018-08-13 18:11 ` Pierre Neidhardt
2018-08-13 18:55 ` Tim Gesthuizen
2018-08-13 19:23 ` fis trivial [this message]
2018-08-13 19:48 ` Tim Gesthuizen
2018-08-13 19:53 ` Pierre Neidhardt
2018-08-13 20:11 ` Tim Gesthuizen
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=BLUPR16MB05002330E9926C7D7D865E2B92390@BLUPR16MB0500.namprd16.prod.outlook.com \
--to=ybbs.daans@hotmail.com \
--cc=guix-devel@gnu.org \
--cc=tim.gesthuizen@yahoo.de \
/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.