From: timor <timor.dd@gmail.com>
To: emacs-orgmode@gnu.org, mail@nicolasgoaziou.fr
Subject: Re: HTML Export of Links to Source Blocks seems broken
Date: Mon, 20 Jun 2016 15:07:53 +0200 [thread overview]
Message-ID: <CAAX25XCYeCfW8ztF27UJmvUoJSHULYXOJEDgn-tZheYGkJq1nQ@mail.gmail.com> (raw)
In-Reply-To: <87fus82fai.fsf@saiph.selenimh>
Hello Nicolas,
2016-06-20 14:52 GMT+02:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> They have no influence over the link description (which is "1" in both
> cases, as you noticed). If you want to change the description, simply
> provide one:
>
> [[test_fun][whatever]]
Sorry for not being able to express myself more clearly, since this is
the exact thing I was making a suggestion about in the first place.
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.
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.
> Regards,
>
> --
> Nicolas Goaziou
next prev parent reply other threads:[~2016-06-20 13:07 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 [this message]
2016-06-20 20:23 ` 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=CAAX25XCYeCfW8ztF27UJmvUoJSHULYXOJEDgn-tZheYGkJq1nQ@mail.gmail.com \
--to=timor.dd@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).