From: Csepp <raingloom@riseup.net>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Csepp <raingloom@riseup.net>, help-guix@gnu.org
Subject: Re: What Python IDE are you using?
Date: Thu, 25 Aug 2022 09:57:09 +0200 [thread overview]
Message-ID: <8735dkhhpx.fsf@riseup.net> (raw)
In-Reply-To: <YG3lXttcigtRKtSPKJejFVKYSDJx1bMpjk0mzt8wUu2FciZY57O0jWPxNvqi7V2ufDVwOGZMwfAPG0jbXDYY5MipqxrvvvBdQSWDZO9Ju5k=@protonmail.com>
Luis Felipe <luis.felipe.la@protonmail.com> writes:
> [[PGP Signed Part:Undecided]]
> On Tuesday, August 23rd, 2022 at 16:52, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
>
>> Hi raingloom,
>>
>
>> On Tuesday, August 23rd, 2022 at 11:34, Csepp raingloom@riseup.net wrote:
>>
>
>> > kakoune + kak-lsp + python-lsp-server + python-black + mypy, maybe a
>> > kakoune editorconfig plugin too
>> >
>
>> > I load it in a guix shell and blamo, nice editor with pretty much every
>> > IDE functionality you could dream of.
>> >
>
>> > I've used this for multiple projects at uni, IMHO it works pretty well.
>>
>
>> Oh, I didn't know about kakoune. I'll put it on the list. Thanks, raingloom :)
>
> I think I'm going to explore vim further as my fallback editor. It
> seems like that's the first step to understand kakoune (I couldn't get
> started with kakoune Get started! document :]).
>
> raingloom, did you move from vim to kakoune? If that was the case, did you found something annoying when programming Python in vim?
>
> [2. application/pgp-keys; publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc]...
>
> [[End of PGP Signed Part]]
I went through the vim tutorial a few years ago, tried neovim for a
while, but haven't used it in years. I tend to switch between editors.
Before Kakoune I used Acme for a long time, which inspired some features
of Kakoune. I also use Emacs quite a bit.
I tried Kakoune mostly because I really liked the ideas in Acme but
didn't like how anti-keyboard it was. The simple orthogonal
configuration language and its focus on multiple selections were very
appealing too. I don't like old editors with crusted up config
languages and UX conventions. I could never really "git gud" at neovim,
so I abandoned it, but Kakoune just "clicked" after 1-2 afternoons of
noodling around in it.
next prev parent reply other threads:[~2022-08-25 8:12 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 [this message]
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
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=8735dkhhpx.fsf@riseup.net \
--to=raingloom@riseup.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).