emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: columns view, org-lint, and native compilation
Date: Mon, 02 Aug 2021 13:15:02 +0100	[thread overview]
Message-ID: <87pmuw9h6h.fsf@ucl.ac.uk> (raw)

Hello all,

TL;DR: org-lint fails, maybe due to native compilation

Longer version: columns view (=org-columns=) doesn't work properly for
me.  If point is in some hierarchy where a higher level heading has a
COLUMNS property, that higher level heading is highlighted and columns
shown for it but none of the subheadings has its columns shown.

In starting to debug this, I decided to make sure the structure of my
file was okay so I invoked =org-lint= which then fails with back trace:

Debugger entered--Lisp error: (search-failed "^[ \11]*#\\+[A-Za-z]+: + *$")
  #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_9>((fixed-width [...]) "")
  #f(compiled-function (datum) #<bytecode 0x146681f219129778>)((fixed-width [...]))
  #f(compiled-function (--data) #<bytecode 0x1281a52c3b7209bc>)((fixed-width [...]))
  org-element-map( [...] )
  org-lint--collect-duplicates([...] )
  #f(compiled-function (c) #<bytecode -0x2b3bd7f9f1a63af>)(#s(org-lint-checker :name duplicate-name :description "Report duplicate NAME values" :categories (babel link) :trust high))
  cl-mapcan(#f(compiled-function (c) #<bytecode -0x2b3bd7f9f1a63af>) [...])

with a lot of text elided.

Before I post something to bugs @ Emacs, has anybody else had problems
with (a) org-columns and (b) org-lint, with or without native

Thank you,

: Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-607-g185706
: Latest paper written in org: https://arxiv.org/abs/2106.05096

             reply	other threads:[~2021-08-02 12:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 12:15 Eric S Fraga [this message]
2021-08-05 15:14 ` columns view, org-lint, and native compilation Ihor Radchenko
2021-08-09 13:13   ` Eric S Fraga

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:

  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=87pmuw9h6h.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \


* 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


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).