emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Jakob Schöttl" <jschoett@gmail.com>
To: emacs-orgmode@gnu.org
Cc: mail@nicolasgoaziou.fr, Ihor Radchenko <yantar92@posteo.net>
Subject: Re: [Bug] org-update-dblock randomly broken for more than 10 columns and larger files
Date: Sat, 19 Aug 2023 20:18:27 +0200	[thread overview]
Message-ID: <975ecec6-86cc-3df9-f55a-d4cfea0f8263@gmail.com> (raw)
In-Reply-To: <87edknovdh.fsf@localhost>

So, org-update-dblock or org-dblock-write:columnview is adding trailing 
spaces in the org file. These spaces change the behavior of subsequent 
calls which will add even more spaces.

Here is a minimal example:

* Table
#+BEGIN: columnview :format "%a %b %c %d %e %f %g"
#+END:

This works as expected. But for each field you add, one trailing space 
is appended to the heading when the org-dblock-update is called.

In larger files, I cannot see any logic behind the added spaces so far.

I tested in Emacs 29.1 and org-mode 9.6.6. (Don't know how to use latest 
version from git repo.)

The function org-dblock-write:columnview is mostly by Nicolas Goaziou 
(from 2016 and 2018). Hello Nicolas, I've added you here. Maybe you have 
an idea what this could be?

Anyway, I'm afraid I can't contribute and fix it. I have no experience 
with elisp, tooling, debugging, and the org-mode code base. I need this 
export feature and will write a org2csv extraction script in Haskell. 
I'm aware that it would be much more helpful in org-mode itself – but 
sorry...




  parent reply	other threads:[~2023-08-19 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  9:41 [Bug] org-update-dblock randomly broken for more than 10 columns and larger files Jakob Schöttl
2023-08-01 11:27 ` Ihor Radchenko
2023-08-07  7:56   ` Jakob Schöttl
2023-08-19 18:18   ` Jakob Schöttl [this message]
2023-08-20  6:56     ` Ihor Radchenko
2023-08-20  8:29       ` Jakob Schöttl
2023-08-20  8:37       ` Jakob Schöttl
2023-08-20  8:57         ` Ihor Radchenko
2023-08-21  7:50           ` Jakob Schöttl

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=975ecec6-86cc-3df9-f55a-d4cfea0f8263@gmail.com \
    --to=jschoett@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=yantar92@posteo.net \
    /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).