From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33359@debbugs.gnu.org, Tim Gesthuizen <tim.gesthuizen@yahoo.de>
Subject: bug#33359: On emacs-clang-format
Date: Wed, 14 Nov 2018 11:48:50 +0100 [thread overview]
Message-ID: <87y39w0wa5.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87o9asj6ra.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
That's absolutely right, I didn't know clang packaged it already.
Here is the listing.
--8<---------------cut here---------------start------------->8---
> ls -1 /gnu/store/...-clang-6.0.1/share/clang
bash-autocomplete.sh
clang-format-bbedit.applescript
clang-format-diff.py
clang-format-sublime.py
clang-format.el
clang-format.py
clang-rename.el
clang-rename.py
--8<---------------cut here---------------end--------------->8---
Not should we fix the Emacs package, but also the Vim .py files, the
Sublime+bbedit extensions (which we can discard I guess) and the Bash
completion.
I see a few ways we can proceed:
- Deprecate emacs-clang-format.
- Use emacs-clang-tooling as suggested by Tim.
- Use clang as it is and fix the installation of the share folder.
- Use clang:emacs output and clang:vim output.
- Keep emacs-clang-format but use the Clang source (as per Tim suggestion), and
add emacs-clang-rename from the same source.
In all cases we need to fix the installation of the Bash completion file and
maybe to discard the Sublime+bbedit extensions.
> : - The license is incorrect. The version that is cloned from github
> : also seems to have some licensing issues (Missing full license...)
Which license?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-11-14 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 21:40 bug#33359: On emacs-clang-format Tim Gesthuizen
2018-11-14 10:25 ` Ludovic Courtès
2018-11-14 10:48 ` Pierre Neidhardt [this message]
2018-11-14 15:56 ` Tim Gesthuizen
2018-11-26 13:54 ` Pierre Neidhardt
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=87y39w0wa5.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=33359@debbugs.gnu.org \
--cc=ludo@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 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).