emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexey Lebedeff <binarin@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix clock table when there are links in headings.
Date: Tue, 18 Mar 2014 17:24:14 +0400	[thread overview]
Message-ID: <CADOt_n8A9FGDMAF3kx80bW17_o_Y=Uub_mV8zLKnirfDycoV1A@mail.gmail.com> (raw)
In-Reply-To: <87vbviuycr.fsf@bzg.ath.cx>

Hi Bastien,

Sorry, I failed to explicitly mention that it was in agenda
clockreport. It was in the screenshot, but I forgot that clocktable is
used in other places than agenda.


With current master (17ecfd4130b11e400b65dfd6b9df43af43d4061b) from
git://orgmode.org/org-mode.git i observe following behaviour:

- When I generate clocktable using C-c C-x C-c on such a heading, all
looks perfect - only descriptions are shown.

- But in agenda (via org-agenda-clockreport-mode) it is displayed with
braces like "STRT {{a}{b}} and {{c}{d}}". This happens if  ':link'
option is enabled when calling org-clock-get-table-data and something
like this is evaluated:
(org-make-link-string "file::abc:100" "[[a][b]] and [[c][d]]") =>
"[[file::abc:100][{{a}{b}} and {{c}{d}}]]"

2014-03-13 15:33 GMT+04:00 Bastien <bzg@gnu.org>:
> Hi Alexey,
>
> I assumed you use the latest Org version, but maybe not.
>
> What does M-x org-version RET reports?
>
> Actually, my bracket links are displayed correctly in the
> clocktable (i.e. as bracket links, not with curly braces.)
>
> Maybe I'm missing something,
>
> --
>  Bastien

  reply	other threads:[~2014-03-18 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  5:47 [PATCH] Fix clock table when there are links in headings Alexey Lebedeff
2014-03-03 12:32 ` Bastien
2014-03-13 11:21   ` Alexey Lebedeff
2014-03-13 11:33     ` Bastien
2014-03-18 13:24       ` Alexey Lebedeff [this message]
2014-03-18 16:10         ` Bastien
2014-03-19  8:57           ` Alexey Lebedeff
2014-03-19  9:50             ` Bastien
2014-03-20  7:47               ` Alexey Lebedeff
2014-03-20  8:45                 ` Bastien

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='CADOt_n8A9FGDMAF3kx80bW17_o_Y=Uub_mV8zLKnirfDycoV1A@mail.gmail.com' \
    --to=binarin@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.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).