From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: edgar@openmail.cc
Cc: help-gnu-emacs@gnu.org, emacs-orgmode@gnu.org
Subject: Re: How to use Org with Python as an IDE?
Date: Tue, 07 Sep 2021 00:20:17 +0200 [thread overview]
Message-ID: <87k0jts5ny.fsf@web.de> (raw)
In-Reply-To: <20210905010312.Horde.qSaJV-gSBfKINOKhvYgNygs@www.vfemail.net>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
edgar@openmail.cc writes:
> I am very sorry for wasting your precious time. This was very simple
It’s the finding that’s hard, not the setup.
> 1. Install (some are optional) python-language-server
> jedi-language-server bash-language-server python-pylint
> python-pydocstyle ccls python-pyls-black
You may also want to use flake8. That helps keep your code pythonic. I
don’t know how much of that is in pylint.
What you may want to add is tangling and *detangling* of
Python-codeblocks in org-mode so you can get a full Python-IDE with
actually working files that you can merge back into org for
documentation. As an example:
https://hg.sr.ht/~arnebab/draketo/browse/anderes/mathe-ass.org?rev=432c5954109b#L346
#+begin_src javascript :tangle "mathe-ass.js" :exports none :comments link
…
#+end_src
Mind the :comments link. That allows getting changed code back into org
by running org-babel-detangle.
- org-babel-tangle creates your working codefile.
- hack in the codefile with full IDE support.
- org-babel-detangle gets your code back into org for better documentation.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2021-09-06 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 22:29 Fwd: How to use Org with Python as an IDE? edgar
2021-09-05 1:03 ` edgar
2021-09-06 22:20 ` Dr. Arne Babenhauserheide [this message]
2021-09-07 3:37 ` edgar
-- strict thread matches above, loose matches on Subject: below --
2021-09-04 4:58 edgar
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0jts5ny.fsf@web.de \
--to=arne_bab@web.de \
--cc=edgar@openmail.cc \
--cc=emacs-orgmode@gnu.org \
--cc=help-gnu-emacs@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).