From: kazark <kazark@zoho.com>
To: "emacs-orgmode" <emacs-orgmode@gnu.org>
Subject: Re: Org 9.7.5: problems with tab-width and certain syntax combinations in SETUPFILE
Date: Wed, 26 Jun 2024 19:07:28 -0400 [thread overview]
Message-ID: <19056cdd499.f39d579d405432.5488182499909296272@zoho.com> (raw)
In-Reply-To: <19056b6b712.b56dc3e1403727.546293949229584581@zoho.com>
[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]
(I had not joined the mailing list before sending the first message.)
I have a workaround for this that allows me to at least load my org files: I can #+COMMENT: out all the lists, which I have in there as documentation (I treat my setup files like literate configuration files).
---- On Wed, 26 Jun 2024 18:42:13 -0400 kazark <kazark@zoho.com> wrote ---
Hi,
I am getting this error after updating to Org-Mode 9.7.5:
The error was: (error "Tab width in Org files must be 8, not 2. Please adjust your ‘tab-width’ settings for Org mode.")
However, it does not happen when I load every Org-Mode file. The MWE I have come up with requires two files; call them test.org and properties.org. The contents of test.org are simply a link to properties.org as a setup file.
#+SETUPFILE: properties.org
The contents of properties.org can be as simple as:
+ foo
#+TODO: TODO(t) | DONE(d)
But no simpler. If the plain list item is removed, the problem does not occur. If the TODO element is removed, the problem does not occur. The problem can also be caused with a MACRO element, but not by COMMENT, BIND, LATEX_HEADER, &c.
Loading properties.org does not cause the problem. Only loading test.org causes the problem, so the problem seems to be specific to when an Org file is loaded as a startup file. I am not clear why tab-width is not being set to 8 in that case. It is true that my global tab-width configuration is 2, but I have not attempted to force Org-Mode to use a value of 2. In fact, before I realize that Org-Mode itself now does (setq-local tab-width 8) I even tried doing that on org-mode-hook, but it didn't help.
Perhaps this is a problem with my configuration, but I suspect that it is an edge-case bug in Org itself. I have reason to think that I am one of the heavier users of setup files. https://emacs.stackexchange.com/a/59492/19069 So it seems entirely possible that I am just the first to hit this edge case.
Because I do rely quite a bit on setup files, this has me in a fairly broken state at the moment. I deeply appreciate any help or advice that you have, as well as all the hard work that goes into Org-Mode. I live my whole life in Org-Mode.
Kazark
[-- Attachment #2: Type: text/html, Size: 3415 bytes --]
next prev parent reply other threads:[~2024-06-26 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 22:42 Org 9.7.5: problems with tab-width and certain syntax combinations in SETUPFILE kazark
2024-06-26 23:07 ` kazark [this message]
2024-06-27 9:54 ` Ihor Radchenko
2024-06-27 12:51 ` kazark
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=19056cdd499.f39d579d405432.5488182499909296272@zoho.com \
--to=kazark@zoho.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 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).