Hi,
I am actually using the #+BIBLIOGRAPHY: functionality. I know that
the functionality lies in ox-bibtex.el. I think a (require 'ox-bibtex)
after loading org-mode did the trick.
cheers,
timor
2016-07-01 14:21 GMT+02:00 David Abernethy :
> I eventually stumbled on the solution to my
Hello Nicolas,
2016-06-20 14:52 GMT+02:00 Nicolas Goaziou :
> 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
...
...
Link to test_fun
Link to another_test_fun
#+END_EXAMPLE
Regards,
timor
2016-06-17 13:56 GMT+02:00 Nicolas Goaziou :
> Hello,
>
> timor writes:
>
>> Why is the link text set to "1" in both cases?
>
> This is just a nonsensical number because Org does
t for some reason seems to do some
form of generic numbering for the link text.
I would probably add a case for (org-element-type destination) being
"src-block", and then use the :name property of the link destination
as link text. Does that route make sense?
Regards,
timor
expect the link text to actually spell "test_fun" and
"another_test_fun" in this case, since those are the names of the
source blocks.
As a workaround, is there anywhere in the exporter that I could hook
into to change the link text myself?
(org version 8.3.4)
Regads,
timor
Hello Nicolas,
Custom IDs seem to be a good alternative here, although I would think
about the <> part as an invisible part, since I don't expect
it to be visible for e.g. export.
Thanks.
Regards,
timor
but for what I want to use it, I will remove the
"<>" part manually.
I was just wondering if maybe this should already be done in
org-get-outline-path itself, since links are also replaced by their
description according to the documentation.
regards,
timor
2016-04-20 9:45 GMT+02:00 Eric S Fraga :
> So it's not just the title that needs to be
> treated carefully but other entries (author, editor, booktitle).
You are correct. The piece of code in question is actually called for
all fields, not only title. I was using the title as an example. So
if
agraphs or link
descriptions, or wherever these kinds of empahsis characters are
valid.
This is only an example of what I want to be able to do, no
specification, sorry.
regards
timor
e, but it is
not org-mode's job to correct poor BibTeX, I think). Therefore they
should be kept intact when reading the field.
> If that's the case, we could indeed remove the duplicate '(123 . 125).
Very nice.
regards,
timor
plain-text parts of org documents (i.e. that would be exported as
the content of attributes in html, or to plain text paragraphs in
Markdown, etc.), there shall be a way to treat strings in the same way
as the surrounding plain text, which would otherwise be handled by
org-mode in a special way.
Does that help?
regards,
timor
{{Unnecessary Braces in Title.}}
I do think, however, that the correct behavior would be to only strip
the outer pair of braces.
regards,
timor
Emacs : GNU Emacs 24.5.1 (i686-pc-mingw32)
of 2015-04-11 on LEG570
Package: Org-mode version 8.3.4 (8.3.4-39-ge0acd8-elpaplus @
/AppData/Roaming/.emacs.
rs which can be escaped.
I also don't know if backslash is the correct way to go.
Another thing I think is important is that is
semi-obvious to non-org-mode people. That's why I think using
org-entities is not a valid workaround for my original problem.
regards,
timor
2015-09-27 11:41
Hello,
Is there a way to export to Markdown without any embedded HTML?
Thanks.
bly make more people make
> use of it.
>
> .. Or should people use zero width spaces?
I am the OP of that QnA
I am wondering why there is no simple backslash-escaping of org-mode syntax?
regards,
timor
15 matches
Mail list logo
