emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: timor <timor.dd@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: HTML Export of Links to Source Blocks seems broken
Date: Mon, 20 Jun 2016 22:23:54 +0200	[thread overview]
Message-ID: <877fdjbodh.fsf@saiph.selenimh> (raw)
In-Reply-To: <CAAX25XCYeCfW8ztF27UJmvUoJSHULYXOJEDgn-tZheYGkJq1nQ@mail.gmail.com> (timor's message of "Mon, 20 Jun 2016 15:07:53 +0200")

timor <timor.dd@gmail.com> writes:

> The thing is, I have a lot of code blocks that define functions, which
> are named exactly after that function.  And as I frequently want to
> reference one of those in the text, I don't want to say
>
>     [[test_fun][test_fun]] ..
> [[another_long_function][another_long_function]]...
>
> everytime, since [[test_fun]] already contains all the information
> needed to generate the link, and the description.  The description is
> always the same as the link target.  That is why I would want to
> change the way that the default link description is generated in the
> case that none is provided.

You can use a hook, which will work at the Org level, or a filter, to
work at the HTML level. See, e.g., (info "(org) Advanced configuration").

> I think that would make sense, given that the way the default
> description is generated at the moment does not seem to provide any
> benefit.

It does, but not in your example. See (info "(org) Internal links") for
details.

Regards,

      reply	other threads:[~2016-06-20 20:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 10:18 HTML Export of Links to Source Blocks seems broken timor
2016-06-17  7:51 ` Nicolas Goaziou
2016-06-17 10:46   ` timor
2016-06-17 11:56     ` Nicolas Goaziou
2016-06-20  8:18       ` timor
2016-06-20 12:52         ` Nicolas Goaziou
2016-06-20 13:07           ` timor
2016-06-20 20:23             ` Nicolas Goaziou [this message]

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=877fdjbodh.fsf@saiph.selenimh \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=timor.dd@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).