From: Luis Felipe <luis.felipe.la@protonmail.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: help-guix@gnu.org
Subject: Re: What Python IDE are you using?
Date: Tue, 23 Aug 2022 16:49:08 +0000 [thread overview]
Message-ID: <-BFSK-paJcgXs5z4d0Kpha8jK0SUg9yung8u8GzDlUp66bSR4YqRWGysHqrE2KWf7_2ZlU9GQUfTVkhUR-k8nZWOyyQzodzHpw20aPshVrw=@protonmail.com> (raw)
In-Reply-To: <871qt7a5ct.fsf@web.de>
[-- Attachment #1.1: Type: text/plain, Size: 1099 bytes --]
Hello Dr. Arne
On Tuesday, August 23rd, 2022 at 05:28, Dr. Arne Babenhauserheide <arne_bab@web.de> wrote:
> I also experience problems with autocompletion at the moment. I’m
> considering to switch back from company to auto-complete-mode, but I shy
> away from the re-configuration effort at the moment.
Good to know it's not just me.
> I have not checked lsp for Python. My experience with lsp for Javascript
> is that they are a bit sluggish — I prefer an Emacs native solution
> where it exists.
>
> Example for that (though other language): Working with js2-mode+eslint
> via flycheck is superior to lsp/tide-mode in my opinion. I feel the
> difference, because I’m in a codebase transitioning to Typescript, and
> the user experience in plain Javascript with js2-mode is better. lsp has
> more bells and whistles, but js2-mode is precise and instantly at my
> fingers.
That's good to know too. I'll give LSP a try anyways and see. I really don't want to leave Emacs, but it would be nice to have a decent backup editor.
Thanks for commenting, Dr. Arne :)
[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1722 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
next prev parent reply other threads:[~2022-08-23 16:51 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='-BFSK-paJcgXs5z4d0Kpha8jK0SUg9yung8u8GzDlUp66bSR4YqRWGysHqrE2KWf7_2ZlU9GQUfTVkhUR-k8nZWOyyQzodzHpw20aPshVrw=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=arne_bab@web.de \
--cc=help-guix@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 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.