emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Luke Crook <luke@balooga.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Links to headings not generated in Tables
Date: Thu, 19 Dec 2013 11:12:17 -0800	[thread overview]
Message-ID: <CADtPBF3pqGh9g_N9LZDtvmWS6yJ441qooBxXoC+3LKvwhJj7kg@mail.gmail.com> (raw)
In-Reply-To: <87siupzcst.fsf@alphaville.bos.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1732 bytes --]

Hi Nicolas,

What about the following code.  In the following, <<1>> and <<2>> are not
appearing in the HTML or the Latex exorts.



* test
  One, [[1]] and two, [[2]].


* blee

| ID    | Descr | Descr |
|-------+-------+-------|
| <<1>> | One   | One   |
| <<2>> | Two   | Two   |



On Thu, Nov 21, 2013 at 1:04 PM, Nick Dokos <ndokos@gmail.com> wrote:

> Luke Crook <luke@balooga.com> writes:
>
> > Nicolas Goaziou <n.goaziou <at> gmail.com> writes:
> >
> >>
> >> Hello,
> >>
> >> Luke Crook <luke <at> balooga.com> writes:
> >>
> >> > Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version.
> >>
> >> OK. Then could you provide an ECM? I'm unable to reproduce the problem.
> >>
> >> Regards,
> >>
> >
> >
> > Hi Nicolas,
> >
> > The first two work correctly, the third does not generate a link for me.
> >
> >
> >
> > | [[id:6920d682-963f-412b-927b-af7dcfd57c79][Code 13]]  |
> > | [[*Code 13]] |
> > | [[*Code 13][Code 13]]  |
> >
> >
> > *** Code 13
> > :PROPERTIES:
> > :ID:       6920d682-963f-412b-927b-af7dcfd57c79
> > :END:
>
> It does for me - here's the table in the HTML output:
>
> --8<---------------cut here---------------start------------->8---
> <table border="2" cellspacing="0" cellpadding="6" rules="groups"
> frame="hsides">
>
>
> <colgroup>
> <col  class="left" />
> </colgroup>
> <tbody>
> <tr>
> <td class="left"><a href="#sec-1">Code 13</a></td>
> </tr>
>
> <tr>
> <td class="left"><a href="#sec-1">1</a></td>
> </tr>
>
> <tr>
> <td class="left"><a href="#sec-1">Code 13</a></td>
> </tr>
> </tbody>
> </table>
> --8<---------------cut here---------------end--------------->8---
>
> Org-mode version 8.2.3c (release_8.2.3c-256-g5ea022.dirty @
> /home/nick/elisp/org-mode/lisp/)
>
> Nick
>
>
>

[-- Attachment #2: Type: text/html, Size: 3170 bytes --]

  reply	other threads:[~2013-12-19 19:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 20:04 Links to headings not generated in Tables Luke Crook
2013-11-20 20:25 ` Nicolas Goaziou
2013-11-20 21:01   ` Luke Crook
2013-11-20 21:11     ` Nicolas Goaziou
2013-11-21 20:36       ` Luke Crook
2013-11-21 21:04         ` Nick Dokos
2013-12-19 19:12           ` Luke Crook [this message]
2013-12-19 19:19             ` Luke Crook
2013-12-19 20:48             ` Nicolas Goaziou
2013-12-20  1:08               ` Luke Crook

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=CADtPBF3pqGh9g_N9LZDtvmWS6yJ441qooBxXoC+3LKvwhJj7kg@mail.gmail.com \
    --to=luke@balooga.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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).