From: Ihor Radchenko <yantar92@posteo.net>
To: "Jakob Schöttl" <jschoett@gmail.com>
Cc: emacs-orgmode@gnu.org, mail@nicolasgoaziou.fr
Subject: Re: [Bug] org-update-dblock randomly broken for more than 10 columns and larger files
Date: Sun, 20 Aug 2023 06:56:51 +0000 [thread overview]
Message-ID: <87msymdwwc.fsf@localhost> (raw)
In-Reply-To: <975ecec6-86cc-3df9-f55a-d4cfea0f8263@gmail.com>
Jakob Schöttl <jschoett@gmail.com> writes:
> 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.
Confirmed.
Unimportant.
The internal implementation details of colview demand heading text to
have at least the number of characters equal to the number of fields. If
there are less, spaces are added. But not beyond the necessary number of
spaces.
This is not easy to change.
And I am not sure if it is necessarily a bug, though I can see how it
can be slightly annoying.
If someone reading this is bothered about the current behaviour, feel
free to work on the fix.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-08-20 6:57 UTC|newest]
Thread overview: 13+ 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
2023-08-20 6:56 ` Ihor Radchenko [this message]
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
2024-07-12 6:30 ` Jakob Schöttl
2024-07-12 11:45 ` Ihor Radchenko
2024-07-12 11:56 ` Ihor Radchenko
2024-07-12 12:01 ` 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=87msymdwwc.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jschoett@gmail.com \
--cc=mail@nicolasgoaziou.fr \
/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).