From: Munyoki Kilyungi <me@bonfacemunyoki.com>
To: jgart <jgart@dismail.de>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: emacs-jedi package bug missing crucial python server file
Date: Wed, 22 Jun 2022 12:14:10 +0300 [thread overview]
Message-ID: <86pmj15acd.fsf@bonfacemunyoki.com> (raw)
In-Reply-To: <20220621225926.GB5429@gac> (jgart@dismail.de's message of "Tue, 21 Jun 2022 22:59:26 -0500")
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
jgart <jgart@dismail.de> writes:
> Hi Guixers,
>
> Just wanted to report a bug with emacs-jedi:
>
> This is all that is currently copied into gnu/store:
>
> jedi-autoloads.el jedi-autoloads.elc jedi-core.el
> jedi-core.elc jedi-pkg.el jedi.el jedi.elc
> test-jedi.el test-jedi.elc tryout-jedi.el
> tryout-jedi.elc
>
> But it's missing jediepcserver.py:
>
> https://github.com/tkf/emacs-jedi/blob/master/Makefile#L132
>
> You would then need to put this in your emacs config:
>
> (setq jedi:server-command '("PATH/TO/jediepcserver.py"))
>
> I'll try to work on it when I get a chance but feel free to fix it if you have the time.
>
A bit of bike-shedding here, but do you have all
your Emacs configs in Guix? And do you use Guix
Home? Also, how does your python set-up look like
in Guix/Emacs?
--
Munyoki Kilyungi
D4F09EB110177E03C28E2FE1F5BBAE1E0392253F (hkp://keys.gnupg.net)
Free Software Activist
Humble GNU Emacs User | Bearer of scheme-y parens
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2022-06-22 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 3:59 emacs-jedi package bug missing crucial python server file jgart
2022-06-22 9:14 ` Munyoki Kilyungi [this message]
2022-06-30 2:13 ` jgart
2022-06-30 11:42 ` Munyoki Kilyungi
2022-06-22 12:55 ` Luis Felipe
2022-06-24 4:03 ` Maxim Cournoyer
2022-06-29 15:44 ` Luis Felipe
2022-06-22 17:32 ` Maxim Cournoyer
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=86pmj15acd.fsf@bonfacemunyoki.com \
--to=me@bonfacemunyoki.com \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.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).