From: "Francesco Pizzolante" <fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
To: Joost Helberg <joost-JFNXyGN8thM@public.gmane.org>
Cc: mailing-list-org-mode <emacs-orgmode-mXXj517/zsQ@public.gmane.org>
Subject: Re: [bug] Alignment bug in clock tables
Date: Fri, 17 Oct 2014 08:29:29 +0200 [thread overview]
Message-ID: <874mv31a5y.fsf@example.com> (raw)
In-Reply-To: <8738b5o3lt.fsf-JFNXyGN8thM@public.gmane.org> (Joost Helberg's message of "Fri, 03 Oct 2014 12:21:50 +0200")
Hi Joost,
> I reported this on September 2nd too. Hitting C-c C-c inside the table
> fixes the formatting. Also moving to a position inside the table and
> doing: M-x org-table-align fixes the formatting. Hence
> I tried to create a new formatter function in order to re-align after
> writing the table:
>
> (defun my-formatter( ipos tables params )
> (progn
> (org-clocktable-write-default ipos tables params)
> (forward-line 2)
> (org-table-align)
> )
> )
>
> and install this as the formatter, but it didn't help. If it would have
> helped, I could have fixed the default table-writer by adding
> (org-table-align).
>
> Anyone an idea?
On my side, I tried another *workaround*: I call (org-table-align) in
a before-save-hook. This way, all tables are correctly aligned when
I save. I simply call:
(org-table-map-tables 'org-table-align t)
But this only works when you save and thus only for file buffers (and
you can still see the misalignment when you create/update the dynamic
blocks).
Currently I have no solution for agenda buffers when displaying clock
tables.
Any hint to fix this is welcome.
Regards,
Francesco
next prev parent reply other threads:[~2014-10-17 6:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 15:41 [bug] Alignment bug in clock tables Francesco Pizzolante
2014-10-03 10:21 ` Joost Helberg
[not found] ` <8738b5o3lt.fsf-JFNXyGN8thM@public.gmane.org>
2014-10-17 6:29 ` Francesco Pizzolante [this message]
2014-11-03 15:45 ` Stormking
2014-11-07 15:16 ` Stormking
[not found] ` <loom.20141107T160907-625-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2015-02-11 10:26 ` Francesco Pizzolante
2015-02-18 12:17 ` Stormking
2015-02-18 14:22 ` Nicolas Goaziou
2015-02-18 14:48 ` Stormking
2015-02-18 14:57 ` Nicolas Goaziou
2015-02-18 15:05 ` Stormking
2015-02-18 15:08 ` Stormking
2015-02-18 15:13 ` Nicolas Goaziou
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=874mv31a5y.fsf@example.com \
--to=fpz-djc/ipccudyqhejpep6iedvlejwurmry@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
--cc=joost-JFNXyGN8thM@public.gmane.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).