Hello,
童俊翔 writes:
> How to add left superscripts without using additional packages in
> org-mode?
Maybe using LaTeX, e.g., \(^{super}\)A.
Regards,
--
Nicolas Goaziou
Hello,
Thomas S. Dye writes:
> I worked on a project to port the Org manual to Org about three years
> ago. At the time, I thought the Texinfo exporter supported the project
> quite well.
>
> The project had a mixed reception and ultimately wasn't adopted, but I
> don't remember Texinfo exporte
Since upgrading to 8.3.4, exporting to HTML fails if there
is a hypertext link in the document with the following error:
if: Autoloading failed to define function url-encode-url
This is the document that fails:
--begin--
#+TITLE: Testing
#+AUTHOR: Brad Collins
#+EMAIL: b...@chenla.la
*
Yes, it works, thank you!
Junxiang
> On 29 Feb 2016, at 17:57, Nicolas Goaziou wrote:
>
> Hello,
>
> 童俊翔 writes:
>
>> How to add left superscripts without using additional packages in
>> org-mode?
>
> Maybe using LaTeX, e.g., \(^{super}\)A.
>
> Regards,
>
> --
> Nicolas Goaziou
Eric S Fraga writes:
> On Monday, 22 Feb 2016 at 10:04, Samuel Loury wrote:
>
> [...]
>
>> Reproducing a slow behavior is not easy. Today, the agenda is produced
>> in about 10s with almost the same contents. I included the profiler
>> report anyway, hoping that you will find something useful in
Nicolas Goaziou writes:
> However, I still think it would be nice to have the document somewhere
> in the Org tree, perhaps in contrib/ as a start, then possibly one day
> in doc/.
Would it serve a purpose?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
On 2016-02-29, at 11:05, Nicolas Goaziou wrote:
> Hello,
>
> Thomas S. Dye writes:
>
>> I worked on a project to port the Org manual to Org about three years
>> ago. At the time, I thought the Texinfo exporter supported the project
>> quite well.
>>
>> The project had a mixed reception and ult
Headline titles may be empty, in which case the respective match group
will be nil. This would throw an error when trying to regexp-replace
checkbox cookies.
TODO: Depending on preference, a place-holder string might be a better
choice (for user-display) rather than leaving the outline-path elemen
Hello,
Thomas S. Dye writes:
> Nicolas Goaziou writes:
>
>> However, I still think it would be nice to have the document somewhere
>> in the Org tree, perhaps in contrib/ as a start, then possibly one day
>> in doc/.
>
> Would it serve a purpose?
Mainly for demonstration. It would also give us
Hello,
Marcin Borkowski writes:
> I know next to nothing about texinfo, but would a converter from texinfo
> to Org be possible? (Or from info to Org, for that matter?)
Possible.
You need a texinfo parser. Also, since Texinfo and Org do not provide
exactly the same features, there are some d
童俊翔 writes:
> How to add left superscripts without using additional packages in org-mode?
I use \nbsp{}^{1}.
Cheers,
Roger
Hello,
Tobias Getzner writes:
> Headline titles may be empty, in which case the respective match group
> will be nil. This would throw an error when trying to regexp-replace
> checkbox cookies.
Indeed. Thank you for the report. I applied a slightly different fix,
tho.
> TODO: Depending on pref
I knew there was a way to do this. I forgot the \nbsp, {} by itself does
not work. Thanks for the reminder.
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitch
John Kitchin writes:
> I knew there was a way to do this. I forgot the \nbsp, {} by itself does not
> work. Thanks for the
> reminder.
The \nbsp does add a space however, so if you are really picky, it might
not be the best choice: you can do
some text\nbsp^{super}A...
to eat one of the space
In support of Nicolas' recommendations you may also find some test
examples with the macros he suggested here:
https://github.com/jkitchin/org-ref/tree/master/test
Over the past week I have been integrating tests on org-ref using some
of those macros. They are pretty easy to use.
Nicolas Goaziou
This describes a system to efficiently capture Org input on a smart phone,
with an emphasis on iOS. The nice thing about this approach is that it only
requires things that you likely already have: your smart phone, your Google
account, and Org. While not required, a text editing app on your
iOS/And
Ken Mankoff wrote:
> I use only MobileOrg and can capture to my desktop by tapping only
> a 5 buttons:
> 1) The app icon, 2) enter text (or tap the mic button and speak),
> 3) Done 4) Outline Mode 5) Sync.
>
> My Desktop then automatically updates w/o 5 minute delay.
> Captured notes are tagged as
Thomas S. Dye writes:
> The project had a mixed reception and ultimately wasn't adopted, but I
> don't remember Texinfo exporter deficiencies figuring into the
> decision.
Well, maybe except that the texinfo exporter is even slower than
texinfo5. I haven't tried it in the last few months, but I e
I am sure this is not the best way to do this, but it more or less does
what you want, which is put the tblfm line at the end (although you
could also format the table in the function.
This is somewhat fragile, i.e. it worked for me as is, and not if I
changed very many things in the headers.
#+
Nicolas Goaziou writes:
> Thomas S. Dye writes:
>
>> I worked on a project to port the Org manual to Org about three years
>> ago. At the time, I thought the Texinfo exporter supported the project
>> quite well.
>>
>> The project had a mixed reception and ultimately wasn't adopted, but I
>> don
Aloha Achim,
Achim Gratz writes:
> Thomas S. Dye writes:
>> The project had a mixed reception and ultimately wasn't adopted, but I
>> don't remember Texinfo exporter deficiencies figuring into the
>> decision.
>
> Well, maybe except that the texinfo exporter is even slower than
> texinfo5. I hav
Hello,
Skip Collins writes:
> I have come up with a better solution than globally passing "broken"
> links. I defined a new "raw" link type. So now if I want to put a
> non-standard link in my export, I can do something like:
> Here is a [[raw:foo:/\bar, baz][bad link]].
> which is exported in h
Hello,
Thomas S. Dye writes:
>> So it needs some love and at least one bugfix.
>
> Sorry to hear that. At the time, I enjoyed working with the texinfo
> exporter and didn't mind that it worked slowly.
The bug is not related to Texinfo back-end. It was fixed a few days ago.
There are a couple
Hello,
Brad Collins writes:
> Since upgrading to 8.3.4, exporting to HTML fails if there
> is a hypertext link in the document with the following error:
>
>if: Autoloading failed to define function url-encode-url
This doesn't seem to be related to Org. `url-encode-url' is autoloaded
in Ema
Nicolas Goaziou writes:
> Tobias Getzner writes:
>
>> Headline titles may be empty, in which case the respective match group
>> will be nil. This would throw an error when trying to regexp-replace
>> checkbox cookies.
>
> Indeed. Thank you for the report. I applied a slightly different fix,
> th
When using the current git HEAD, I’ve noticed that my agenda has become
rather messy. This is because I’m including the outline-path in agenda
entries, and it seems that the changes following aa78158 (possibly
66fbceb?) have changed the org-get-outline-path semantics.
The documentation says that
Hello,
i updated to org-mode 8.3.4 on windows.
When i now do an org-mobile-push then the agendas.org file is created
but has no entries. it only contains the dates and diary entries, but
none of my tasks, as if no agenda files would be there.
When i use orgmode normally on my pc, everything is wo
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
--text follows this line--
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
--
Hello,
neutrico writes:
> Steps to reproduce:
>
> 1. Create org document hello.org :
>
> #+BEGIN_SRC org
>
> #TITLE: Hello
>
> ** World
>
> #+END_SRC
>
> 2. M-x org-html-export-as-html
>
> Returns:
>
> apply: Wrong type argument: listp, #("HELLO" 0 5 (:parent (#0)))
>
>
> When I remove TITLE the
Hello,
9661031 <9661...@gmail.com> writes:
> When you use a headline which is more than 7th level,the exported LaTeX file
> raises an error in typesetting. Here is an example (org file):
>
> ===
> * one
> ** two
> *** three
> four
> * five
> ** six
> *** seven
> eight
>
W dniu 02/29/2016 o 10:15 PM, Nicolas Goaziou pisze:
Hello,
neutrico writes:
Steps to reproduce:
1. Create org document hello.org :
#+BEGIN_SRC org
#TITLE: Hello
** World
#+END_SRC
2. M-x org-html-export-as-html
Returns:
apply: Wrong type argument: listp, #("HELLO" 0 5 (:parent (#0)
Hello,
Tobias Getzner writes:
> When using the current git HEAD, I’ve noticed that my agenda has become
> rather messy. This is because I’m including the outline-path in agenda
> entries, and it seems that the changes following aa78158 (possibly
> 66fbceb?) have changed the org-get-outline-path
This documentation bug exists also in org-mode 8.3.2 and the current online org-mode manual.The export of links like [[file:a.org::#my-custom-id][Some link]] and[[file:a.org::*Section header][Some link to a section header]] is notdescribed in the org-mode manual. This leads to questions like thefo
34 matches
Mail list logo
