From: Fredrik Salomonsson <plattfot@posteo.net>
To: Luis Felipe <luis.felipe.la@protonmail.com>,
Luis Felipe <luis.felipe.la@protonmail.com>
Cc: help guix <help-guix@gnu.org>
Subject: Re: What Python IDE are you using?
Date: Wed, 24 Aug 2022 01:09:15 +0000 [thread overview]
Message-ID: <87fshmv45g.fsf@d2.com> (raw)
In-Reply-To: <isfvk5ArqCi7xcuQr097BOrZFnzQtVhcKtryhtBKICac0E0gtqOQLfZOZ5cNbTMO7wbgRQ4-vVYukMHrSrBbEmjnAb5nlnzZcnqMfO9Ysrs=@protonmail.com>
Luis Felipe <luis.felipe.la@protonmail.com> writes:
> On Tuesday, August 23rd, 2022 at 23:39, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
>
>> On Tuesday, August 23rd, 2022 at 21:20, Fredrik Salomonsson plattfot@posteo.net wrote:
>>
>
>> > I generally use emacs + eglot [0]. It works great out of the box for me,
>> > zero configuration on my part. I can't speak much about speed as the
>> > python programming I do is over tramp, which tends to slow things down.
>>
>
>> I tried both emacs-lsp-mode and eglot today, but autocompletion didn't work in any of them. They both seem to use company-mode by default, the same as emacs-elpy. Is autocompletion working for you? If yes, what version of Guix are you using? (I'm on Guix System 3f17158, emacs-company 0.9.13).
>
> Hmm, I just ran Emacs in three separate guix containers, one for an LSP mode-based IDE, one for an Eglot-based IDE and one for an Elpy-based IDE. In each of these containers, I ran "emacs -q -l CONFIG.el" to avoid loading any "init.el" file, and instead load a specific, minimal configuration file for each IDE. Autocompletion worked in all of them.
>
> So it seems something in my "~/.congig/emacs/init.el" is not right anymore for my current generation of Emacs packages...
Yeah, sounds like something in your config is breaking the autocomplete.
I don't use company anymore but instead I use corfu. I am using guix
92b25a0 on a foreign distro, with emacs-eglot@1.8 and emacs-corfu@0.26.
And emacs-pgtk-native-comp@28.1.90-224.03fe258 from the flat channel
d95204c. And autocomplete works fine on my end.
> I think I found emacs-lsp-mode faster than eglot, and the autodocumentation/help in the latter was kind of distracting because it displays too much information for the symbol
> at point, which makes the minibuffer change hight frequently.
Right, I forgot a do actually have some configuration associated with eglot.
try
(setf eldoc-echo-area-use-multiline-p nil)
That should take care of the minibuffer issue. As I also was quite
annoyed with that.
--
s/Fred[re]+i[ck]+/Fredrik/g
next prev parent reply other threads:[~2022-08-24 1:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 22:29 What Python IDE are you using? Luis Felipe
2022-08-23 5:28 ` Dr. Arne Babenhauserheide
2022-08-23 16:49 ` Luis Felipe
2022-08-26 17:53 ` Maxim Cournoyer
2022-08-28 18:13 ` Luis Felipe
2022-08-23 11:34 ` Csepp
2022-08-23 16:52 ` Luis Felipe
2022-08-24 13:26 ` Luis Felipe
2022-08-25 7:57 ` Csepp
2022-08-25 13:01 ` Luis Felipe
2022-08-23 21:20 ` Fredrik Salomonsson
2022-08-23 23:39 ` Luis Felipe
2022-08-24 0:13 ` Luis Felipe
2022-08-24 1:09 ` Fredrik Salomonsson [this message]
2022-08-24 12:00 ` Luis Felipe
2022-08-25 18:33 ` david larsson
2022-08-25 18:43 ` david larsson
2022-08-28 18:03 ` Luis Felipe
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=87fshmv45g.fsf@d2.com \
--to=plattfot@posteo.net \
--cc=help-guix@gnu.org \
--cc=luis.felipe.la@protonmail.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.
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).