From: Ihor Radchenko <yantar92@posteo.net>
To: Rudi C <rudiwillalwaysloveyou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Forcing tab-width to be 8 makes using Python source blocks very difficult
Date: Sat, 16 Mar 2024 09:41:53 +0000 [thread overview]
Message-ID: <871q8ajyxq.fsf@localhost> (raw)
In-Reply-To: <CAE9z9A38BsUPW6+HyZ-EE3GaOkYdt1SJpuNxLxWua9c3gRNvrw@mail.gmail.com>
Rudi C <rudiwillalwaysloveyou@gmail.com> writes:
> Recently, a breaking change has been introduced in Org mode that sets the
> default tab-width to 8 spaces (
> https://list.orgmode.org/orgmode/8734y5d2gs.fsf@localhost/). This change
> has made using Python source blocks in Org mode challenging, as operations
> like `evil-org->` rely on `tab-width`, and Python code conventions
> typically use 4 spaces for indentation.
May you please provide more details on what exactly "evil-org->" refers
to and what specific problems you encountered?
> Moreover, using 8 spaces for indentation is generally unsuitable for small
> laptop screens, where screen real estate is of utmost importance.
May you please provide a detailed example where 8 spaces causes issues?
In source blocks specifically, we make sure that tab width visually
looks as in the corresponding source code buffer.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-03-16 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 5:32 Forcing tab-width to be 8 makes using Python source blocks very difficult Rudi C
2024-03-16 9:41 ` Ihor Radchenko [this message]
2024-03-16 10:27 ` Rudi C
2024-03-16 11:02 ` Ihor Radchenko
2024-03-16 17:39 ` Rudi C
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=871q8ajyxq.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=rudiwillalwaysloveyou@gmail.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.
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).