From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id yFYdD2effGZLMgAAe85BDQ:P1 (envelope-from ) for ; Wed, 26 Jun 2024 23:08:23 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id yFYdD2effGZLMgAAe85BDQ (envelope-from ) for ; Thu, 27 Jun 2024 01:08:23 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=zoho.com header.s=zm2022 header.b=WBynEVip; dmarc=pass (policy=reject) header.from=zoho.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; arc=pass ("zohomail.com:s=zohoarc:i=1") ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1719443303; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=/Xdy6pD4vzIqkTnUxjQXEEUIEu6Yp6U1M6btsOPschA=; b=rBy0pWgwWEmPz30R6TdZX/fy0lNFknKhQL2DyRMXBe6lfPAI7PgXLRlg/bLMTu8lq1grI6 rQDZjv4u05mU3KBPshWh/0G17LYeUksh92ygs0HChhZcnnMxLvbe3RSFA0nneAOGwq/yVx dQazKZ7jLYGoLeDDSlU+wWwvVIF1UZlL/FyQRrlQNIBA8razHQ+OWZTBjiD964Tyb/Nq8v 565Xw2XF8yEksn5+alTgUHgMTBGp61pAbIoJzaMzedX5KvRwKSm6B5bik9s4wRGquzXaCx tDsL75mQNPu3A1/XIpWsWNbjDTm4EMkZ82GoI4FojoKWINNk7ikAsMJjlSn+jA== ARC-Seal: i=2; s=key1; d=yhetil.org; t=1719443303; a=rsa-sha256; cv=pass; b=I2CfqOw98tcJ81HnjosWK4sugteJWOGlZQW/mGhotUONT7V2mnltEvRwU1XCnXHY3w5cxy sawM63BMXQqIIbxv8F0uqLFl0ZnhH41sYOSrrWiwkdrfy3Wt8V6mRDqQYB61eL+jSO/uk6 AnIkqrDG6zK1igmrqKDyuQ+i9ud2q60NpxMh/HVQmkjMmO/6ukqxJoGw2S0W/4VH6apMQs dNkRYItbIH99GQgNeZSpIy48CBKWeJhrhiLUExqbc4ziFAY8FEvtxhnetB/0DfKovhSXqg nYlTnZR6e8sx9I+w4Pt3siiO57AM0C/t5ZWelPayETuseAmnUcuGEoRg5d39xw== ARC-Authentication-Results: i=2; aspmx1.migadu.com; dkim=pass header.d=zoho.com header.s=zm2022 header.b=WBynEVip; dmarc=pass (policy=reject) header.from=zoho.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; arc=pass ("zohomail.com:s=zohoarc:i=1") Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id ECFC335742 for ; Thu, 27 Jun 2024 01:08:22 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sMbjq-0001tw-Hu; Wed, 26 Jun 2024 19:07:42 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sMbjp-0001tD-0j for emacs-orgmode@gnu.org; Wed, 26 Jun 2024 19:07:41 -0400 Received: from sender4-of-o55.zoho.com ([136.143.188.55]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sMbjl-0007FC-Om for emacs-orgmode@gnu.org; Wed, 26 Jun 2024 19:07:40 -0400 ARC-Seal: i=1; a=rsa-sha256; t=1719443254; cv=none; d=zohomail.com; s=zohoarc; b=Mdb40Xk+IoOH1uDS8cxKgbOZ2i7weX4C9kqjj3i6pIPRjoADSXPlL7ezhsMEBKOXM8RCuwG3lFPbeqqocp+ZMWhYgNGDFo/RHUd0waQB7fKCK1GWiOw1YK6os0StH/JOWge6loLR+hDXrhMrEtOJgro0DxIX68kkyOZv0rmqG0c= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1719443254; h=Content-Type:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To:Cc; bh=/Xdy6pD4vzIqkTnUxjQXEEUIEu6Yp6U1M6btsOPschA=; b=TtamRuWNkFhmGw4qo6sDDIN58ItbAkjCQWOx+ZYnohnRMp3w5wtF7uIPp+VaHPgzP5rIukBhPsjKIhb2Z6H2FDyd7IAwnLK9pfJwmuiPE81tP5lWLggtuuvZDZjzku+iwlfK/Dq76+S+vISWBQE3cswLyF0+VEFzMzwcdd5Kk7I= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=zoho.com; spf=pass smtp.mailfrom=kazark@zoho.com; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1719443254; s=zm2022; d=zoho.com; i=kazark@zoho.com; h=Date:Date:From:From:To:To:Message-Id:Message-Id:In-Reply-To:References:Subject:Subject:MIME-Version:Content-Type:Reply-To:Cc; bh=/Xdy6pD4vzIqkTnUxjQXEEUIEu6Yp6U1M6btsOPschA=; b=WBynEVip96vc0IqFmTMl3ZC2NHZYJGL0rWOrFswoHqrQo39H/xyUC0SwcR88jWhU 22iHTXgyk81oXJAxXf/YaGZHAokdBxKDiHE/wJGjuKK3TXaOgT6wa6cMAFdjlwTaw2j XBEvHTF7XmIbH8Yvzoj9uhbT3aE5uRVmIf+Ldndk= Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1719443248305663.873667596625; Wed, 26 Jun 2024 16:07:28 -0700 (PDT) Date: Wed, 26 Jun 2024 19:07:28 -0400 From: kazark To: "emacs-orgmode" Message-Id: <19056cdd499.f39d579d405432.5488182499909296272@zoho.com> In-Reply-To: <19056b6b712.b56dc3e1403727.546293949229584581@zoho.com> References: <19056b6b712.b56dc3e1403727.546293949229584581@zoho.com> Subject: Re: Org 9.7.5: problems with tab-width and certain syntax combinations in SETUPFILE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1301979_1555945082.1719443248281" Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail Received-SPF: pass client-ip=136.143.188.55; envelope-from=kazark@zoho.com; helo=sender4-of-o55.zoho.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Queue-Id: ECFC335742 X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: -10.88 X-Spam-Score: -10.88 X-TUID: 3PywoiHKTkTX ------=_Part_1301979_1555945082.1719443248281 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable (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 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.=C2=A0 Pleas= e adjust your =E2=80=98tab-width=E2=80=99 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. Th= e 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 occ= ur. 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_H= EADER, &c. Loading properties.org does not cause the problem. Only loading test.org ca= uses the problem, so the problem seems to be specific to when an Org file i= s loaded as a startup file. I am not clear why tab-width is not being set t= o 8 in that case. It is true that my global tab-width configuration is 2, b= ut I have not attempted to force Org-Mode to use a value of 2. In fact, bef= ore 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 a= n 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 ca= se. Because I do rely quite a bit on setup files, this has me in a fairly broke= n 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 lif= e in Org-Mode. Kazark ------=_Part_1301979_1555945082.1719443248281 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =
(I had not joined the mailing list before sending = the first message.)

I have a workaround for th= is that allows me to at least load my org files: I can #+COMMENT: out all t= he lists, which I have in there as documentation (I treat my setup files li= ke literate configuration files).



---- On Wed, 26 Jun 2024 18:42:13 -0400 kazark <k= azark@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 =E2=80=98tab-width=E2=80=99 set= tings for Org mode.")

However, it does not hap= pen when I load every Org-Mode file. The MWE I have come up with requires t= wo files; call them test.org and properties.org. The contents of test.org a= re simply a link to properties.org as a setup file.

#+SETUPFILE: properties.org

The contents= of properties.org can be as simple as:

+ foo<= br>
#+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 a= lso 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 seem= s 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 no= w does (setq-local tab-width 8) I even tried doing that on org-mode-hook, b= ut it didn't help.

Perhaps this is a problem w= ith my configuration, but I suspect that it is an edge-case bug in Org itse= lf. I have reason to think that I am one of the heavier users of setup file= s. 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 f= airly broken state at the moment. I deeply appreciate any help or advice th= at you have, as well as all the hard work that goes into Org-Mode. I live m= y whole life in Org-Mode.

Kazark



<= /html> ------=_Part_1301979_1555945082.1719443248281--