Re: [O] Poll: new keybinding for org-insert-structure-template?

[Rasmus]

Eric Abrahamsen  writes:

> Rasmus  writes:
>
>> Nicolas Goaziou  writes:
>>
>>> Hello,
>>>
>>> Rasmus  writes:
>>>
 Nicolas, are there any public interfaces to make ox export like
 interfaces?
>>>
>>> No, there isn't. However, Org provides `org-mks'.
>>
>> Good point.  It isn’t quite as nice as the export dispatcher.  Let’s wait
>> and see what Eric prefers.
>
> I don't have to own this! I don't have a strong feeling about it, and
> left to my own devices would just keep the single-character keys.

It’s pretty nice and quick with only one character.

> But I see why people would want more/longer keys, and better
> discoverability.

Discoverability is nice to have, but it’s a secondary issue.


> The main desires are:
>
> 1. String keys of arbitrary length.
> 2. Discoverability: either a window of choices pops up automatically, or
>you can do it with TAB, etc.
> 3. Ideally, you don't have to hit an extra key to finish.
>
> Given that, it seems to me that `org-mks' is just fine. It doesn't do as
> much as the export dispatcher, but I don't see that it needs to.

It doesn’t seem to offer a way to distinguish between a single "a" and
"ab".

(org-mks '(("a" "a.. templates")
   ("a" "export ascii" "")
   ("ab" "abstract" "")
   ("l" "latex" ""))
 "Select a template"
 "Template key: "
 '(("q" "Abort")))

Perhaps the best way would be to automatically reserve upper case letters
for blocks with keys longer than one character, although that seems a bit
arbitrary.

(org-mks '(("A" "a.. templates")
   ("a" "export ascii" "")
   ("Ab" "abstract" "")
   ("l" "latex" ""))
 "Select a template"
 "Template key: "
 '(("q" "Abort")))

Rasmus

-- 
And I faced endless streams of vendor-approved Ikea furniture. . .

Re: [O] Can export the files with bibliography only to LaTeX

[Julian M. Burgos]

I do not think there is an out-of-the-box way to export a bibliography
directly from org-mode to formats other than LaTex.  What I usually do
is export to Tex and then use Pandoc (https://pandoc.org/) to convert that 
document to other
formats, usually Word so I can share my work with my colleagues.  Pandoc
can read the bibtex file and add the right citations, doing something
like this:

pandoc --bibliography /path/to/my_bib_file.bib my_document.docx my_document.tex

There is also the ox-pandoc package, that allows you to export directly
from org using pandoc.  I have not tried yet (it is in my to-do list).

https://github.com/kawabata/ox-pandoc

Julian

Melleus writes:

> I used to think that I can export from org to bunch of different
> formats. But all of a sudden when I need this feature I see that I can
> export only to LaTeX. But when I try exporting to other format I get
>
> Wrong type argument: stringp, nil   error message.
>
> When there's no bibtex references or exporting to LaTeX everything just
> works.
>
> How can I troubleshoot the situation and possibly find the clue? I
> couldn't find any documentation on the exporting references issues on
> Worg unfortunately.
>
> My environment: Gentoo with stable keyword, Emacs 25.3.1, Org 9.1.4.
>
> Thanks ahead of time.


--
Julian Mariano Burgos, PhD
Hafrannsóknastofnun, rannsókna- og ráðgjafarstofnun hafs og vatna/
Marine and Freshwater Research Institute
Botnsjávarsviðs / Demersal Division
Skúlagata 4, 121 Reykjavík, Iceland
Sími/Telephone : +354-5752037
Bréfsími/Telefax:  +354-5752001
Netfang/Email: julian.bur...@hafogvatn.is

Re: [O] Can export the files with bibliography only to LaTeX

[Alan Schmitt]

Hello,

org-ref (https://github.com/jkitchin/org-ref) has some bibliography
support for html (and looking back at it for plain text, although I
never tried it).

Best,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-11: 405.14, 2016-11: 403.53


signature.asc
Description: PGP signature

Re: [O] DEADLINE ignored?

[Rainer Stengele]

Am 04.09.2017 um 12:21 schrieb Eric S Fraga:

On Monday,  4 Sep 2017 at 12:08, Pdj wrote:

Hello, I am observing this (funky?) behavior:
in the agenda, the deadline seems to be identified only if it
immediately follows the headline, and it is ignored otherwise.
Am I missing something?   Thank you, Paolo.


You are not missing something.  As the manual says:

 A timestamp may be preceded by special keywords to facilitate
 planning.  Both the timestamp and the keyword have to be positioned
 immediately after the task they refer to.

I guess immediately means not even a blank line.


Hi,

it looks like

* TODO task
DEADLINE: <2017-12-14 Do>
SCHEDULED: <2017-12-14 Do>

will find the DEADLINE and SCHEDULE timestamp and display correctly in the 
agenda while

* TODO task
SCHEDULED: <2017-12-14 Do>
DEADLINE: <2017-12-14 Do>

will still find the SCHEDULED tinestamp but no more the DEADLINE.
I had this sequence in my org templates in the past and had no issues as far as 
I remember.
Has this behaviour changed?

Freshly creating a new SCHEDULED and DEADLINED timestamp results in the 
structure below.
Do all tasks now need to have both items in the same line like here:

* TODO task
SCHEDULED: <2017-12-14 Do> DEADLINE: <2017-12-14 Do>

Thank you.
Regards, Rainer

Org mode version 9.1.4 (release_9.1.4-206-g4b80c6.dirty ..

Re: [O] Can export the files with bibliography only to LaTeX

[Adonay Felipe Nogueira]

Indeed, Pandoc is a way out ;)

I just would advise against converting from LaTeX to Word DOC.

I'd say stick to LaTeX and PDF.

This is important because: just like PDF, DOC (and also DOCX and
ODF-family) is sometimes binary file, but beyond that: DOC is not
standardized, and one can't edit a DOC in plain text editor, this makes
it difficult to read version differences for a given file (although it
can be used in revision/version controlled spaces, it still makes it
difficult for a human reviewer to read the differences).

Relying on these formats such as DOC and DOCX only serve to
make people more dependent on the non-free software behind these.

Finally, if writting collaboratively with someone else, either send them
the Org or LaTeX file anyways, or if they are reviewing the changes: either
make use of a revision/version control system, send them only the diffs
that come from the revision/version control system you're using, or send
them the HTML output of `diffoscope' comparing a PDF of a previous
version with the PDF of the new version.

For more information on the current caveats of using `diffoscope' with
PDF files, see my reply in [1].

[1] 
.

2017-12-14T09:06:19+ Julian M. Burgos wrote:
> I do not think there is an out-of-the-box way to export a bibliography
> directly from org-mode to formats other than LaTex.  What I usually do
> is export to Tex and then use Pandoc (https://pandoc.org/) to convert
> that document to other
> formats, usually Word so I can share my work with my colleagues.  Pandoc
> can read the bibtex file and add the right citations, doing something
> like this:
>
> pandoc --bibliography /path/to/my_bib_file.bib my_document.docx 
> my_document.tex
>
> There is also the ox-pandoc package, that allows you to export directly
> from org using pandoc.  I have not tried yet (it is in my to-do list).
>
> https://github.com/kawabata/ox-pandoc
>
> Julian

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
  gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.

[O] advice please: best way to export to DOC(X) with maths

[Eric S Fraga]

Hello,

almost all the writing I do that is intended to be exported will be
exported to LaTeX.  However, every now and again I need to export to
DOC/DOCX.

My query is: what is the best way (i.e. the state of the art) currently
in org to export to DOC/DOCX for text that has equations?  I have both
inline maths, e.g. \(i \in [0,n]\) and displayed equations.  Is there a
route that will convert these to something Word et al. can process
directly, other than images?  Maybe via pandoc?

Thanks,
eric

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.3-168-g7455f4


signature.asc
Description: PGP signature

[O] Referencing TODO items

[Paulo Matos]

Hi,

I have a TODO item that got stuck due to some unforseen circumstances.
Another TODO item is needed as a workaround therefore I have something like:

* TODO Implement using hash tables
  :LOGBOOK:
  - Note taken on ... \\
  Stuck because...
  :END:

* TODO Implement using hand written maps
  This is required because todo item REF was stuck. If unstuck, we can
remove this implementation.

How can I REF the first TODO item in the second?

Thanks,

-- 
Paulo Matos

Re: [O] Can export the files with bibliography only to LaTeX

[Eric S Fraga]

On Thursday, 14 Dec 2017 at 10:11, Adonay Felipe Nogueira wrote:
> Indeed, Pandoc is a way out ;)
>
> I just would advise against converting from LaTeX to Word DOC.

[...]

> Relying on these formats such as DOC and DOCX only serve to
> make people more dependent on the non-free software behind these.

I am sympathetic to these views but unfortunately it's not always
possible.  My university, for instance, requires me to prepare exam
scripts in DOC (hence my related email a few minutes ago... my yearly
task of preparing scripts is upon me).  I hate it but I have no choice.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.3-168-g7455f4


signature.asc
Description: PGP signature

Re: [O] Referencing TODO items

[Michael Welle]

Hello,

Paulo Matos  writes:

> Hi,
>
> I have a TODO item that got stuck due to some unforseen circumstances.
> Another TODO item is needed as a workaround therefore I have something like:
>
> * TODO Implement using hash tables
>   :LOGBOOK:
>   - Note taken on ... \\
>   Stuck because...
>   :END:
>
> * TODO Implement using hand written maps
>   This is required because todo item REF was stuck. If unstuck, we can
> remove this implementation.
>
> How can I REF the first TODO item in the second?
do M-x org-store-link on the first TODO item and M-x org-insert-link
where you want to reference the first TODO item.

Regards
hmw

Re: [O] DEADLINE ignored?

[Nicolas Goaziou]

Hello,

Rainer Stengele  writes:

> it looks like
>
> * TODO task
> DEADLINE: <2017-12-14 Do>
> SCHEDULED: <2017-12-14 Do>
>
> will find the DEADLINE and SCHEDULE timestamp and display correctly in
> the agenda while

Sheer luck, I would say.

> * TODO task
> SCHEDULED: <2017-12-14 Do>
> DEADLINE: <2017-12-14 Do>
>
> will still find the SCHEDULED tinestamp but no more the DEADLINE.
> I had this sequence in my org templates in the past and had no issues as far 
> as I remember.
> Has this behaviour changed?

I cannot remember Org supporting this syntax, actually. I don't think
anything changed.

> Freshly creating a new SCHEDULED and DEADLINED timestamp results in the 
> structure below.
> Do all tasks now need to have both items in the same line like here:
>
> * TODO task
> SCHEDULED: <2017-12-14 Do> DEADLINE: <2017-12-14 Do>

They do, but it's not new.

Regards,

-- 
Nicolas Goaziou

Re: [O] Referencing TODO items

[Paulo Matos]

On 14/12/17 14:31, Michael Welle wrote:
> Hello,
> 
> Paulo Matos  writes:
> 
>> Hi,
>>
>> I have a TODO item that got stuck due to some unforseen circumstances.
>> Another TODO item is needed as a workaround therefore I have something like:
>>
>> * TODO Implement using hash tables
>>   :LOGBOOK:
>>   - Note taken on ... \\
>>   Stuck because...
>>   :END:
>>
>> * TODO Implement using hand written maps
>>   This is required because todo item REF was stuck. If unstuck, we can
>> remove this implementation.
>>
>> How can I REF the first TODO item in the second?
> do M-x org-store-link on the first TODO item and M-x org-insert-link
> where you want to reference the first TODO item.
> 

Interesting but it doesn't really work properly.

My TODO looks like:

* TODO add support for %lo and %hi operands in offsets

I create the link and the link has the name of the todo headline.
When I try to follow with C-c C-o, it says 'No match - create a new
heading?'. If I say yes, a new heading is created in my document that
looks like:

* *add support for ^@ and ^@ operands in offsets

I am curious why %hi and %lo would cause any troubles...

-- 
Paulo Matos

Re: [O] Referencing TODO items

[Michael Welle]

Hello,

Paulo Matos  writes:
[...]
> Interesting but it doesn't really work properly.
>
> My TODO looks like:
>
> * TODO add support for %lo and %hi operands in offsets
>
> I create the link and the link has the name of the todo headline.
> When I try to follow with C-c C-o, it says 'No match - create a new
> heading?'. If I say yes, a new heading is created in my document that
> looks like:
>
> * *add support for ^@ and ^@ operands in offsets
>
> I am curious why %hi and %lo would cause any troubles...
I can confirm that behaviour, but it doesn't bother me, because I use ;):

(setq org-id-link-to-org-use-id 'create-if-interactive)

Regards
hmw

Re: [O] Referencing TODO items

[Paulo Matos]

On 14/12/17 15:20, Michael Welle wrote:
>>
>> I am curious why %hi and %lo would cause any troubles...
> I can confirm that behaviour, but it doesn't bother me, because I use ;):
> 
> (setq org-id-link-to-org-use-id 'create-if-interactive)
> 

When I looked at it, it sounded that the only thing it does it to
automatically create the heading without prompting, however I ran into
troubles when testing. My org-mode doesn't have that variable (9.1.2)
and even if it did it wouldn't solve the problem (assuming I am correct
about its intended behaviour since I don't want a new heading, I want to
follow the link to the existing heading.


-- 
Paulo Matos

Re: [O] DEADLINE ignored?

[Rainer Stengele]

Am 14.12.2017 um 14:41 schrieb Nicolas Goaziou:

Hello,

Rainer Stengele  writes:


it looks like

* TODO task
DEADLINE: <2017-12-14 Do>
SCHEDULED: <2017-12-14 Do>

will find the DEADLINE and SCHEDULE timestamp and display correctly in
the agenda while


Sheer luck, I would say.


* TODO task
SCHEDULED: <2017-12-14 Do>
DEADLINE: <2017-12-14 Do>

will still find the SCHEDULED tinestamp but no more the DEADLINE.
I had this sequence in my org templates in the past and had no issues as far as 
I remember.
Has this behaviour changed?


I cannot remember Org supporting this syntax, actually. I don't think
anything changed.


Freshly creating a new SCHEDULED and DEADLINED timestamp results in the 
structure below.
Do all tasks now need to have both items in the same line like here:

* TODO task
SCHEDULED: <2017-12-14 Do> DEADLINE: <2017-12-14 Do>


They do, but it's not new.

Regards,


Thanks, Nicolas.

I am concerned hearing you say "sheer luck" because I am relying on such double 
entries, which seem to have worked well in the past:

* TODO [#A] Change tyres spring/autumn
DEADLINE: <2018-05-01 Di> SCHEDULED: <2018-04-21 Sa +1y>
DEADLINE: <2018-11-10 Sa> SCHEDULED: <2018-11-03 Sa +1y>

So is that working only by sheer luck?

Thank you.
Regards, Rainer

Re: [O] DEADLINE ignored?

[Nicolas Goaziou]

Rainer Stengele  writes:

> I am concerned hearing you say "sheer luck" because I am relying on such 
> double entries, which seem to have worked well in the past:
>
> * TODO [#A] Change tyres spring/autumn
> DEADLINE: <2018-05-01 Di> SCHEDULED: <2018-04-21 Sa +1y>
> DEADLINE: <2018-11-10 Sa> SCHEDULED: <2018-11-03 Sa +1y>
>
> So is that working only by sheer luck?

Definitely. Planning info is a single line, right below the heading.
Most related code relies on that assumption.

Regards,

[O] Git repository error

[Josiah Schwab]

Hello,

For about the past day, I've been getting this error upon running 'make
update' from my local Org repository:

  fatal: read error: Connection reset by peer
  error: Could not fetch origin

If I recall correctly, this has happened before and the resolution was
that some admin needed to do something server-side.

Thanks,
Josiah

Re: [O] Can export the files with bibliography only to LaTeX

[Adonay Felipe Nogueira]

Interesting...

Is this really a requirement? Did you actually asked which formats they
support? Perhaps with careful negotiation, you might come up with good
outcomes. For example: support for sending your work as PDF, TXT or
HTML.

In the case of HTML, you can use any of these to convert your LaTeX file
to HTML:

a) htlatex "File.tex"; although I don't know if this one will do
multiple runs automatically.

b) make4ht "File.tex"; if I'm not mistaken, this last method automates
the various runs of mk4ht; or lastly

c) pass "htlatex" as the LaTeX command (`-latex=' option) in `latexmk',
see the texdoc for `latexmk' and for `htlatex' to know what to put in
the `-latex=' option.

2017-12-14T12:28:46+ Eric S Fraga wrote:
> [...]
>
>
> I am sympathetic to these views but unfortunately it's not always
> possible.  My university, for instance, requires me to prepare exam
> scripts in DOC (hence my related email a few minutes ago... my yearly
> task of preparing scripts is upon me).  I hate it but I have no choice.

[O] Icalendar / exclude events older than 2 months

[Jota Pin]

Dear all,

I would like to set a hook that excludes events older than 2 months from 
exporting using org-icalendar-combine-agenda-files.

I do not know enough lisp for that, thanks for any help ,
Jota

Re: [O] Referencing TODO items

[Michael Welle]

Hello,

Paulo Matos  writes:

> On 14/12/17 15:20, Michael Welle wrote:
>>>
>>> I am curious why %hi and %lo would cause any troubles...
>> I can confirm that behaviour, but it doesn't bother me, because I use ;):
>> 
>> (setq org-id-link-to-org-use-id 'create-if-interactive)
>> 
>
> When I looked at it, it sounded that the only thing it does it to
> automatically create the heading without prompting, however I ran into
> troubles when testing. My org-mode doesn't have that variable (9.1.2)
it is from org-id. It gives the heading a unique id and uses that to
reference the heading instead of the heading's text. That way the
reference does not become invalid if the heading's text changes. And, as
a side effect, it works around the problem you found.


> and even if it did it wouldn't solve the problem (assuming I am correct
> about its intended behaviour since I don't want a new heading, I want to
> follow the link to the existing heading.
No, it doesn't solve the problem. I guess the problem is that the
heading's text is fed to a format form or something like that.

Regards
hmw

[O] LaTeX (not Beamer) export options

[Ken Mankoff]

Hi Org List,

Is there an easy way to specify #+LATEX_HEADER options that will not be used 
when exporting to Beamer? I can do the opposite - #+BEAMER_HEADER lines are not 
exported to LaTeX. But I have some LaTeX config options that are getting in the 
way when exporting to Beamer.

Thanks,

  -k.

Re: [O] Poll: new keybinding for org-insert-structure-template?

[Eric Abrahamsen]

Rasmus  writes:

> Eric Abrahamsen  writes:
>
>> Rasmus  writes:
>>
>>> Nicolas Goaziou  writes:
>>>
 Hello,

 Rasmus  writes:

> Nicolas, are there any public interfaces to make ox export like
> interfaces?

 No, there isn't. However, Org provides `org-mks'.
>>>
>>> Good point.  It isn’t quite as nice as the export dispatcher.  Let’s wait
>>> and see what Eric prefers.
>>
>> I don't have to own this! I don't have a strong feeling about it, and
>> left to my own devices would just keep the single-character keys.
>
> It’s pretty nice and quick with only one character.
>
>> But I see why people would want more/longer keys, and better
>> discoverability.
>
> Discoverability is nice to have, but it’s a secondary issue.
>
>
>> The main desires are:
>>
>> 1. String keys of arbitrary length.
>> 2. Discoverability: either a window of choices pops up automatically, or
>>you can do it with TAB, etc.
>> 3. Ideally, you don't have to hit an extra key to finish.
>>
>> Given that, it seems to me that `org-mks' is just fine. It doesn't do as
>> much as the export dispatcher, but I don't see that it needs to.
>
> It doesn’t seem to offer a way to distinguish between a single "a" and
> "ab".
>
> (org-mks '(("a" "a.. templates")
>("a" "export ascii" "")
>("ab" "abstract" "")
>("l" "latex" ""))
>  "Select a template"
>  "Template key: "
>  '(("q" "Abort")))
>
> Perhaps the best way would be to automatically reserve upper case letters
> for blocks with keys longer than one character, although that seems a bit
> arbitrary.
>
> (org-mks '(("A" "a.. templates")
>("a" "export ascii" "")
>("Ab" "abstract" "")
>("l" "latex" ""))
>  "Select a template"
>  "Template key: "
>  '(("q" "Abort")))

Right, you can't have a string act as both a "sub-menu dispatcher" and a
menu item at the same time.

I don't see that it's a big deal, though. For the default value, at
least, it's pretty clear how we would arrange the values: SRC and EXPORT
need sub-menus, and everything else doesn't. Ie:

'(("s" "Source Code")
  ("se" "Elisp" "src elisp")
  ("sp" "Python" "src python")
  ...etc
  ("e" "Export Block")
  ("eh" "HTML" "export html")
  ("el" "LaTeX" "export latex")
  ...etc
  ("v" "Verbatim" "verbatim")
  ("q" "Quote" "quote")
  ("E" "Example" "example")
  ...etc
  )

That's not so bad, is it?

Eric

Re: [O] Referencing TODO items

[Nicolas Goaziou]

Hello,

Paulo Matos  writes:

> My TODO looks like:
>
> * TODO add support for %lo and %hi operands in offsets
>
> I create the link and the link has the name of the todo headline.
> When I try to follow with C-c C-o, it says 'No match - create a new
> heading?'. If I say yes, a new heading is created in my document that
> looks like:
>
> * *add support for ^@ and ^@ operands in offsets
>
> I am curious why %hi and %lo would cause any troubles...

This is because % are not properly escaped, so `org-link-unescape'
turns %hi into ^@.

This is now fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] DEADLINE ignored?

[Rainer Stengele]

Am 14.12.2017 um 16:39 schrieb Nicolas Goaziou:

Rainer Stengele  writes:


I am concerned hearing you say "sheer luck" because I am relying on such double 
entries, which seem to have worked well in the past:

* TODO [#A] Change tyres spring/autumn
DEADLINE: <2018-05-01 Di> SCHEDULED: <2018-04-21 Sa +1y>
DEADLINE: <2018-11-10 Sa> SCHEDULED: <2018-11-03 Sa +1y>

So is that working only by sheer luck?


Definitely. Planning info is a single line, right below the heading.
Most related code relies on that assumption.

Regards,



Thanks for clarifying, I will adjust and use multiple tasks.

Regards
Rainer

Re: [O] Can export the files with bibliography only to LaTeX

[edgar]

Date: Thu, 14 Dec 2017 12:28:46 +
Subject: Re: [O] Can export the files with bibliography only to LaTeX
I am sympathetic to these views but unfortunately it's not always
possible.  My university, for instance, requires me to prepare exam
scripts in DOC (hence my related email a few minutes ago... my yearly
task of preparing scripts is upon me).  I hate it but I have no choice.



I'm on the same boat: when your advisor "kindly" asks you to write 
everything in DOC{,X}. But it's a boat that is sinking, and let's hope 
sooner than later.


-

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  

Re: [O] advice please: best way to export to DOC(X) with maths

[edgar]

Date: Thu, 14 Dec 2017 12:18:24 +
From: Eric S Fraga 
To: emacs-orgmode@gnu.org
Subject: [O] advice please: best way to export to DOC(X) with maths
Message-ID: <87ind9pkof@gmail.com>
Content-Type: text/plain; charset="us-ascii"

Hello,

almost all the writing I do that is intended to be exported will be
exported to LaTeX.  However, every now and again I need to export to
DOC/DOCX.

My query is: what is the best way (i.e. the state of the art) currently
in org to export to DOC/DOCX for text that has equations?  I have both
inline maths, e.g. \(i \in [0,n]\) and displayed equations.  Is there a
route that will convert these to something Word et al. can process
directly, other than images?  Maybe via pandoc?

Thanks,
eric

--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.3-168-g7455f4


I only know how to do a rough approximation by means of pandoc:

#+BEGIN_SRC bash
  pandoc -f org+smart my-original.org -t docx+smart -o my-output.docx
#+END_SRC

for slightly older versions of pandoc, this may work (there is an 
equivalent for the references, I think):

#+BEGIN_SRC bash
  pandoc -f org+smart --bibliography=../../References.bib 
my-original.org -o my-output.doc

#+END_SRC

I used to have a better solution, but at some point it stopped working. 
I didn't ask here, because 1/2 of my questions go under the radar, and I 
don't like to bug people with my issues:


To get a working file, first export to odt with Org-mode
(~C-c C-e o o~), and then run this (you can do ~C-c C-c~
on it; make sure that LibreOffice is not running)
#+BEGIN_SRC shell :results none
 libreoffice --headless --convert-to doc ./my-.odt
#+END_SRC

For the latter, I used to have
#+OPTIONS: tex:dvipng

A better solution would be most appreciated.

-

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  

Re: [O] Referencing TODO items

[Paulo Matos]

On 14/12/17 22:45, Nicolas Goaziou wrote:
> Hello,
> 
> Paulo Matos  writes:
> 
>> My TODO looks like:
>>
>> * TODO add support for %lo and %hi operands in offsets
>>
>> I create the link and the link has the name of the todo headline.
>> When I try to follow with C-c C-o, it says 'No match - create a new
>> heading?'. If I say yes, a new heading is created in my document that
>> looks like:
>>
>> * *add support for ^@ and ^@ operands in offsets
>>
>> I am curious why %hi and %lo would cause any troubles...
> 
> This is because % are not properly escaped, so `org-link-unescape'
> turns %hi into ^@.
> 
> This is now fixed. Thank you.
> 

Perfect.
Thanks for the quick fix.

> Regards,
> 

-- 
Paulo Matos

Re: [O] Referencing TODO items

[Ken Mankoff]

On 2017-12-14 at 14:20, Michael Welle  wrote:
> I can confirm that behaviour, but it doesn't bother me, because I use
>
> (setq org-id-link-to-org-use-id 'create-if-interactive)

This is a nice feature/solution but I'd like to point out to others reading it 
that there may be a better option that uses custom IDs if they exist:

(setq org-id-link-to-org-use-id 'create-if-interactive-and-no-custom-id)

  -k.