From: Rudi C <rudiwillalwaysloveyou@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Forcing tab-width to be 8 makes using Python source blocks very difficult
Date: Sat, 16 Mar 2024 09:02:51 +0330 [thread overview]
Message-ID: <CAE9z9A38BsUPW6+HyZ-EE3GaOkYdt1SJpuNxLxWua9c3gRNvrw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
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.
Moreover, using 8 spaces for indentation is generally unsuitable for small
laptop screens, where screen real estate is of utmost importance.
Personally, I have been using a hook to force `tab-width` back to 4 spaces,
but this has resulted in persistent warnings:
```
Error running timer 'org-indent-initialize-agent': (error "Tab width in Org
files must be 8, not 4. Please adjust your 'tab-width' settings for Org
mode.") [4 times]
```
In my opinion, the touted benefits of consistency brought by this breaking
change do not justify the inconvenience it causes. I prefer customizable
software that can be adapted to various situations, rather than enforcing
uniform behavior.
PS: Please use Reply to All.
[-- Attachment #2: Type: text/html, Size: 1229 bytes --]
next reply other threads:[~2024-03-16 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 5:32 Rudi C [this message]
2024-03-16 9:41 ` Forcing tab-width to be 8 makes using Python source blocks very difficult Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE9z9A38BsUPW6+HyZ-EE3GaOkYdt1SJpuNxLxWua9c3gRNvrw@mail.gmail.com \
--to=rudiwillalwaysloveyou@gmail.com \
--cc=emacs-orgmode@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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.