how to export checkboxes to odt?

how to export checkboxes to odt?

[Uwe Brauer]

Hi

Any idea how to export checkboxes to odt?

I mean not just simply having [ ] in the odt document but having them translated as actual boxes.

Thanks and regards

Uwe Brauer 

[SOLVED] (was: how to export checkboxes to odt?)

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

>>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:

> Hi

> Any idea how to export checkboxes to odt?

> I mean not just simply having [ ] in the odt document but having them translated as actual boxes.

Either using latex $\boxtimes$
or   UTF8 ☒



[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

Re: [SOLVED] (was: how to export checkboxes to odt?)

[Timothy]

[-- Attachment #1: Type: text/plain, Size: 288 bytes --]

Hello,

>> Any idea how to export checkboxes to odt?
>> I mean not just simply having [ ] in the odt document but having them translated as actual boxes.
>
> Either using latex ⊠
> or   UTF8 ☒

I’m wondering, would this be worth adding to ox-odt?

All the best,
Timothy

Re: [SOLVED]

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 447 bytes --]

>>> "T" == Timothy  <tecosaur@gmail.com> writes:

> Hello,
>>> Any idea how to export checkboxes to odt?
>>> I mean not just simply having [ ] in the odt document but having them translated as actual boxes.
>> 
>> Either using latex ⊠
>> or   UTF8 ☒

> I’m wondering, would this be worth adding to ox-odt?

I think Juan's solution would be nice, however it does not work for me write now, so I have to see what is wrong with it.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

Re: [SOLVED] (was: how to export checkboxes to odt?)

[Max Nikulin]

On 29/09/2021 11:07, Timothy wrote:
> 
>>> Any idea how to export checkboxes to odt?
>>> I mean not just simply having [ ] in the odt document but having them translated as actual boxes.
>>
>> Either using latex ⊠
>> or   UTF8 ☒
> 
> I’m wondering, would this be worth adding to ox-odt?

LibreOffice has some object called "checkbox" that could be inserted 
using "Form Controls" toolbar. I have never used this feature, so unsure 
whether it is a proper representation for Org checkboxes.

[checkbox in tables] (was: [SOLVED])

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

>>> "MN" == Max Nikulin <manikulin@gmail.com> writes:

> On 29/09/2021 11:07, Timothy wrote:
>> 
>>> Any idea how to export checkboxes to odt?
>>> I mean not just simply having [ ] in the odt document but having them translated as actual boxes.
>>> 
>>> Either using latex ⊠
>>> or   UTF8 ☒
>> I’m wondering, would this be worth adding to ox-odt?

> LibreOffice has some object called "checkbox" that could be inserted
> using "Form Controls" toolbar. I have never used this feature, so
> unsure whether it is a proper representation for Org checkboxes.

I should add, that I need to generate an odt document, in which checkboxes are placed in tables, a feature that is not supported by org mode as of today, unfortunately.


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

Re: how to export checkboxes to odt?

[Juan Manuel Macías]

Hi Uwe,

Uwe Brauer writes:

> Any idea how to export checkboxes to odt?
>
> I mean not just simply having [ ] in the odt document but having them translated as actual boxes.

You can try:

(defun my/org-odt--checkbox (item)
  "Return check-box string associated to ITEM."
  (let ((checkbox (org-element-property :checkbox item)))
    (if (not checkbox) ""
      (format "<text:span text:style-name=\"%s\">%s</text:span>"
	      "OrgCode" (cl-case checkbox
			  (on "\u2611 ") ; CHECK MARK
			  (off "\u2610 ")
			  (trans "[-] ")))))) ;; I don't know which character to choose here...

(advice-add 'org-odt--checkbox :override  #'my/org-odt--checkbox)

Best regards,

Juan Manuel 

Re: how to export checkboxes to odt?

[Uwe Brauer]

[-- Attachment #1.1: Type: text/plain, Size: 1383 bytes --]

>>> "JMM" == Juan Manuel Macías <maciaschain@posteo.net> writes:

Hi Juan,

> Hi Uwe,
> Uwe Brauer writes:

>> Any idea how to export checkboxes to odt?
>> 
>> I mean not just simply having [ ] in the odt document but having them translated as actual boxes.

> You can try:

> (defun my/org-odt--checkbox (item)
>   "Return check-box string associated to ITEM."
>   (let ((checkbox (org-element-property :checkbox item)))
>     (if (not checkbox) ""
>       (format "<text:span text:style-name=\"%s\">%s</text:span>"
> 	      "OrgCode" (cl-case checkbox
> 			  (on "\u2611 ") ; CHECK MARK
> 			  (off "\u2610 ")
> 			  (trans "[-] ")))))) ;; I don't know which character to choose here...

> (advice-add 'org-odt--checkbox :override  #'my/org-odt--checkbox)

Thanks very much, I saw it too late to respond yesterday. A couple of remarks

    1. (on "\u2611 ") ; CHECK MARK: I rather prefer 2612 but this is a
       question of taste

    2. It seems not to work, I loaded the function and Executed the
       advice, but 

When I tried to export this minimal example

* Check the conversion of checkboxes


    1. Latex $\boxtimes$

    2. UTF8 ☒,   ▢ □

    3. Org   [ ] and   [X]

    4. Org [] [-]

I obtained a odt file in which 3 and 4 were *not* converted to UTF8. I
attach the file. What do I miss?

Regards

Uwe 


[-- Attachment #1.2: checkbox.odt --]
[-- Type: application/vnd.oasis.opendocument.text, Size: 12057 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

[misunderstanding] (was: how to export checkboxes to odt?)

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 479 bytes --]



> Hi Juan,




> Thanks very much, I saw it too late to respond yesterday. A couple of remarks

>     1. (on "\u2611 ") ; CHECK MARK: I rather prefer 2612 but this is a
>        question of taste

>     2. It seems not to work, I loaded the function and Executed the
>        advice, but 

I just want to clarify, that your code works.
I realized that I used the word checkbox not a the strict org mode sense.
Sorry for the confusion!

Thanks for your code

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

[BUG] org-persist [9.5 (release_9.5-194-gdb302d @ /home/oub/emacs/site-lisp/packages/org/)]

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 85 bytes --]


In connection with my earlier bug report, here is the backtrace when starting emacs

[-- Attachment #2: startup-error.txt --]
[-- Type: text/plain, Size: 10676 bytes --]

Debugger entered--Lisp error: (void-function org-file-name-concat)
  org-file-name-concat("/home/oub/.cache" "org-persist/")
  byte-code("\301\302\303 \304\1!\203\16\0\10\202\17\0\211\262\1\305\"!\207" [user-emacs-directory expand-file-name org-file-name-concat xdg-cache-home seq-empty-p "org-persist/"] 5)
  (defvar org-persist-directory (byte-code "\301\302\303 \304\1!\203\16\0\10\202\17\0\211\262\1\305\"!\207" [user-emacs-directory expand-file-name org-file-name-concat xdg-cache-home seq-empty-p "org-persist/"] 5) ("/home/oub/emacs/site-lisp/packages/org/org-persist..." . 175))
  require(org-persist)
  byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\300\305!\210\300\306!\210\300\307!\210\300\310!\210\300\311!\210\300\312!\210\300\313!\210\300\314!\207" [require avl-tree ring cl-lib ol org org-persist org-compat org-entities org-footnote org-list org-macs org-table] 2)
  require(org-element)
  byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\300\305!\210\300\306!\210\300\307!\210\300\310!\207" [require cl-lib ob-exp oc oc-basic ol org-element org-macro tabulated-list] 2)
  require(ox)
  byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\300\305!\210\306\307\310\311\312\313\314\315\316&\10\207" [require cl-lib format-spec ox ox-publish table org-export-define-backend html ((bold . org-html-bold) (center-block . org-html-center-block) (clock . org-html-clock) (code . org-html-code) (drawer . org-html-drawer) (dynamic-block . org-html-dynamic-block) (entity . org-html-entity) (example-block . org-html-example-block) (export-block . org-html-export-block) (export-snippet . org-html-export-snippet) (fixed-width . org-html-fixed-width) (footnote-reference . org-html-footnote-reference) (headline . org-html-headline) (horizontal-rule . org-html-horizontal-rule) (inline-src-block . org-html-inline-src-block) (inlinetask . org-html-inlinetask) (inner-template . org-html-inner-template) (italic . org-html-italic) (item . org-html-item) (keyword . org-html-keyword) (latex-environment . org-html-latex-environment) (latex-fragment . org-html-latex-fragment) (line-break . org-html-line-break) (link . org-html-link) (node-property . org-html-node-property) (paragraph . org-html-paragraph) (plain-list . org-html-plain-list) (plain-text . org-html-plain-text) (planning . org-html-planning) (property-drawer . org-html-property-drawer) (quote-block . org-html-quote-block) (radio-target . org-html-radio-target) (section . org-html-section) (special-block . org-html-special-block) (src-block . org-html-src-block) (statistics-cookie . org-html-statistics-cookie) (strike-through . org-html-strike-through) (subscript . org-html-subscript) (superscript . org-html-superscript) (table . org-html-table) (table-cell . org-html-table-cell) (table-row . org-html-table-row) (target . org-html-target) (template . org-html-template) ...) :filters-alist ((:filter-options . org-html-infojs-install-script) (:filter-parse-tree . org-html-image-link-filter) (:filter-final-output . org-html-final-function)) :menu-entry (104 "Export to HTML" ((72 "As HTML buffer" org-html-export-as-html) (104 "As HTML file" org-html-export-to-html) (111 "As HTML file and open" (lambda (a s v b) (if a ... ...))))) :options-alist ((:html-doctype "HTML_DOCTYPE" nil org-html-doctype) (:html-container "HTML_CONTAINER" nil org-html-container-element) (:html-content-class "HTML_CONTENT_CLASS" nil org-html-content-class) (:description "DESCRIPTION" nil nil newline) (:keywords "KEYWORDS" nil nil space) (:html-html5-fancy nil "html5-fancy" org-html-html5-fancy) (:html-link-use-abs-url nil "html-link-use-abs-url" org-html-link-use-abs-url) (:html-link-home "HTML_LINK_HOME" nil org-html-link-home) (:html-link-up "HTML_LINK_UP" nil org-html-link-up) (:html-mathjax "HTML_MATHJAX" nil "" space) (:html-equation-reference-format "HTML_EQUATION_REFERENCE_FORMAT" nil org-html-equation-reference-format t) (:html-postamble nil "html-postamble" org-html-postamble) (:html-preamble nil "html-preamble" org-html-preamble) (:html-head "HTML_HEAD" nil org-html-head newline) (:html-head-extra "HTML_HEAD_EXTRA" nil org-html-head-extra newline) (:subtitle "SUBTITLE" nil nil parse) (:html-head-include-default-style nil "html-style" org-html-head-include-default-style) (:html-head-include-scripts nil "html-scripts" org-html-head-include-scripts) (:html-allow-name-attribute-in-anchors nil nil org-html-allow-name-attribute-in-anchors) (:html-divs nil nil org-html-divs) (:html-checkbox-type nil nil org-html-checkbox-type) (:html-extension nil nil org-html-extension) (:html-footnote-format nil nil org-html-footnote-format) (:html-footnote-separator nil nil org-html-footnote-separator) (:html-footnotes-section nil nil org-html-footnotes-section) (:html-format-drawer-function nil nil org-html-format-drawer-function) (:html-format-headline-function nil nil org-html-format-headline-function) (:html-format-inlinetask-function nil nil org-html-format-inlinetask-function) (:html-home/up-format nil nil org-html-home/up-format) (:html-indent nil nil org-html-indent) (:html-infojs-options nil nil org-html-infojs-options) (:html-infojs-template nil nil org-html-infojs-template) (:html-inline-image-rules nil nil org-html-inline-image-rules) (:html-link-org-files-as-html nil nil org-html-link-org-files-as-html) (:html-mathjax-options nil nil org-html-mathjax-options) (:html-mathjax-template nil nil org-html-mathjax-template) (:html-metadata-timestamp-format nil nil org-html-metadata-timestamp-format) (:html-postamble-format nil nil org-html-postamble-format) (:html-preamble-format nil nil org-html-preamble-format) (:html-prefer-user-labels nil nil org-html-prefer-user-labels) (:html-self-link-headlines nil nil org-html-self-link-headlines) (:html-table-align-individual-fields nil nil org-html-table-align-individual-fields) (:html-table-caption-above nil nil org-html-table-caption-above) (:html-table-data-tags nil nil org-html-table-data-tags) ...)] 9)
  require(ox-html)
  byte-code("\300\301!\210\300\302!\210\300\303!\210\304\305\306\307\310\311\312\313\314\315\316\317&\13\210\320\321\322\323\324DD\325\312\305\326\327&\7\210\320\330\322\323\331DD\332..." [require cl-lib ox-html ox-publish custom-declare-group org-export-md nil "Options specific to Markdown export back-end." :tag "Org Markdown" :group org-export :version "24.4" :package-version (Org . "8.0") custom-declare-variable org-md-headline-style funcall function #f(compiled-function () #<bytecode 0x1f400b723399>) "Style used to format headlines.\nThis variable can ..." :type (choice (const :tag "Use \"atx\" style" atx) (const :tag "Use \"Setext\" style" setext)) org-md-footnotes-section #f(compiled-function () #<bytecode 0x1f40006223633>) "Format string for the footnotes section.\nThe first..." string "26.1" (Org . "9.0") org-md-footnote-format #f(compiled-function () #<bytecode -0x377aad65da8591f>) "Format string for the footnote reference.\nThe %s w..." (Org . "9.0") org-export-define-derived-backend md html :filters-alist ((:filter-parse-tree . org-md-separate-elements)) :menu-entry (109 "Export to Markdown" ((77 "To temporary buffer" (lambda (a s v b) (org-md-export-as-markdown a s v))) (109 "To file" (lambda (a s v b) (org-md-export-to-markdown a s v))) (111 "To file and open" (lambda (a s v b) (if a (org-md-export-to-markdown t s v) (org-open-file ...)))))) :translate-alist ((bold . org-md-bold) (center-block . org-md--convert-to-html) (code . org-md-verbatim) (drawer . org-md--identity) (dynamic-block . org-md--identity) (example-block . org-md-example-block) (export-block . org-md-export-block) (fixed-width . org-md-example-block) (headline . org-md-headline) (horizontal-rule . org-md-horizontal-rule) (inline-src-block . org-md-verbatim) (inlinetask . org-md--convert-to-html) (inner-template . org-md-inner-template) (italic . org-md-italic) (item . org-md-item) (keyword . org-md-keyword) (latex-environment . org-md-latex-environment) (latex-fragment . org-md-latex-fragment) (line-break . org-md-line-break) (link . org-md-link) (node-property . org-md-node-property) (paragraph . org-md-paragraph) (plain-list . org-md-plain-list) (plain-text . org-md-plain-text) (property-drawer . org-md-property-drawer) (quote-block . org-md-quote-block) (section . org-md-section) (special-block . org-md--convert-to-html) (src-block . org-md-example-block) (table . org-md--convert-to-html) (template . org-md-template) (verbatim . org-md-verbatim)) :options-alist ((:md-footnote-format nil nil org-md-footnote-format) (:md-footnotes-section nil nil org-md-footnotes-section) (:md-headline-style nil nil org-md-headline-style))] 12)
  require(ox-md)
  byte-code("\300\301!\210\302\303\304\305\306\307\310\311\312\313\314\315&\13\210\316\317\320\321\310\303\322\323&\7\210\316\324\325\326\310\303\322\327&\7\210\316\330\331\332\310\303\322\327&..." [require ox-md custom-declare-group org-export-pandoc nil "Options specific to Pandoc export back-end." :tag "Org Pandoc" :group org-export :version "24.4" :package-version (Org . "8.0") custom-declare-variable org-pandoc-process-after-export t "Run pandoc to process the file after exporting it?" :type (choice (const :tag "Yes" t) (const :tag "No" nil)) org-pandoc-command "pandoc" "Command to run pandoc." string org-pandoc-extra-options "" "Extra pandoc options to use every time.\nFor exampl..." org-pandoc-output-format 'epub "Default output format for pandoc conversion." symbol org-pandoc-output-standalone "Should output be a single standalone file or not?" boolean org-pandoc-epub-rights "Copyright/license statement to include in EPUB met..." org-pandoc-epub-stylesheet "Stylesheet to apply to EPUB files."] 12)
  require(ox-pandoc)
  eval-buffer(#<buffer  *load*-315843> nil "/home/oub/emacs/init/emacs_init.el" nil t)  ; Reading at buffer position 22629
  load-with-code-conversion("/home/oub/emacs/init/emacs_init.el" "/home/oub/emacs/init/emacs_init.el" nil nil)
  load("/home/oub/emacs/init/emacs_init.el" nil nil t)
  load-file("~/emacs/init/emacs_init.el")
  (cond ((and (not running-xemacs) (> emacs-major-version 19)) (package-initialize) (load-file "~/emacs/init/emacs_init.el") (setq custom-file "/home/oub/emacs/init/custom-init.el") (load-file "/home/oub/emacs/init/custom-init.el")))
  eval-buffer(#<buffer  *load*> nil "/home/oub/.emacs" nil t)  ; Reading at buffer position 905
  load-with-code-conversion("/home/oub/.emacs" "/home/oub/.emacs" nil nil)
  load("/home/oub/.emacs" nil nil t)
  load-file("~/.emacs")
  funcall-interactively(load-file "~/.emacs")
  call-interactively(load-file nil nil)
  command-execute(load-file)

[-- Attachment #3: Type: text/plain, Size: 391 bytes --]





Emacs  : GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.14.6, Xaw3d scroll bars)
 of 2021-11-08
Package: Org mode version 9.5 (release_9.5-194-gdb302d @ /home/oub/emacs/site-lisp/packages/org/)

current state:
==============
State could not be dumped due to the following error:

(void-variable org-descriptive-links)

You should still send this bug report.

[SOLVED] (was: [BUG] org-persist [9.5 (release_9.5-194-gdb302d @ /home/oub/emacs/site-lisp/packages/org/)])

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

>>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:

> In connection with my earlier bug report, here is the backtrace when starting emacs

> Debugger entered--Lisp error: (void-function org-file-name-concat)

> (void-variable org-descriptive-links)

> You should still send this bug report.


I found the culprit, the recently installed org-real pkg.

I uninstalled it and everything was back to normally.

Regards

Uwe Brauer

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

Re: [SOLVED] (was: [BUG] org-persist [9.5 (release_9.5-194-gdb302d @ /home/oub/emacs/site-lisp/packages/org/)])

[Ihor Radchenko]

Uwe Brauer <oub@mat.ucm.es> writes:

> I found the culprit, the recently installed org-real pkg.
>
> I uninstalled it and everything was back to normally.

Hmm. I suspect that org-real might not be the problem by itself. Rather
you may load it too early and pull-in built-in org.

Best,
Ihor

Re: [SOLVED]

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 426 bytes --]

>>> "IR" == Ihor Radchenko <yantar92@gmail.com> writes:

> Uwe Brauer <oub@mat.ucm.es> writes:
>> I found the culprit, the recently installed org-real pkg.
>> 
>> I uninstalled it and everything was back to normally.

> Hmm. I suspect that org-real might not be the problem by itself. Rather
> you may load it too early and pull-in built-in org.

Well I don't load anything, that is all done by the package system.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

Re: [SOLVED]

[Ihor Radchenko]

Uwe Brauer <oub@mat.ucm.es> writes:

>> Hmm. I suspect that org-real might not be the problem by itself. Rather
>> you may load it too early and pull-in built-in org.
>
> Well I don't load anything, that is all done by the package system.

I was just guessing. But do you really have init.el with no requires?

Best,
Ihor

Re: [SOLVED]

[Uwe Brauer]

>>> "IR" == Ihor Radchenko <yantar92@gmail.com> writes:

> Uwe Brauer <oub@mat.ucm.es> writes:
>>> Hmm. I suspect that org-real might not be the problem by itself.
>>> Rather you may load it too early and pull-in built-in org.
>> 
>> Well I don't load anything, that is all done by the package system.

> I was just guessing. But do you really have init.el with no requires?

I have a lot of requires in my init file, but non for org-real besides I
have installed a lot of org addons from MELPA and none have caused me
any problem.

So if I understand you correctly. I do load my org package too late for
org-real?

Regards

Uwe 

Re: [SOLVED]

[Ihor Radchenko]

Uwe Brauer <oub@mat.ucm.es> writes:

> So if I understand you correctly. I do load my org package too late for
> org-real?

I think so. My speculation:

If the newest Org is not yet in load-path when you load org-real,
org-real's (require 'org) will pull-in built-in version of org-compat.

Later, when load-path points to the newest version of Org, you load
org-persist (org-persist does not exist in built-in version of Org),
which relies on org-file-name-concat to be defined in the newest version
of org-compat. However, built-in version of org-compat is already loaded
by emacs and (require 'org-compat) inside org-persist does not trigger
loading. Hence, you are getting

> Debugger entered--Lisp error: (void-function org-file-name-concat)

Best,
Ihor

org-ref-insert-cite-link inserts citep

[Uwe Brauer]

Hi 

I enjoy org-ref, but I struggle to configure org-ref-insert-link.

It inserts, per default, citep
for example 
citep:wald84:_gener_relat

How can I change that to plain cite:wald84:_gener_relat

Thanks and regards

Uwe Brauer 

[SOLVED] (was: org-ref-insert-cite-link inserts citep)

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 202 bytes --]

>>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:

   > Hi 

   > I enjoy org-ref, but I struggle to configure org-ref-insert-link.

(setq org-ref-default-citation-link "cite")

Is your friend


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]

Re: [SOLVED] (was: org-ref-insert-cite-link inserts citep)

[John Kitchin]

[-- Attachment #1: Type: text/plain, Size: 612 bytes --]

That is the default value of that variable. I guess you had set it
elsewhere to be getting citep before.

John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu



On Wed, Dec 11, 2019 at 4:59 PM Uwe Brauer <oub@mat.ucm.es> wrote:

> >>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:
>
>    > Hi
>
>    > I enjoy org-ref, but I struggle to configure org-ref-insert-link.
>
> (setq org-ref-default-citation-link "cite")
>
> Is your friend
>
>

[-- Attachment #2: Type: text/html, Size: 1307 bytes --]

Re: [SOLVED]

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

>>> "JK" == John Kitchin <jkitchin@andrew.cmu.edu> writes:

> That is the default value of that variable. I guess you had set it
> elsewhere to be getting citep before.

Right, moreover in some obscure place which was not easy to find, and
the setting was also not commented, so it unclear to me why I did this.

Bad bad practise.

Uwe 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]

org babel: %% [removed source block]

[Uwe Brauer]

Hi 

I have the following org file
#+BEGIN_SRC matlab :tangle test.m :padline no :results none
function [ll x]=mitest(A0,x0)
% initialization 
format long
epsi=1.e-3;
nit=0;
nmaxit=200;
Delta=10;
A=A0;
while Delta>epsi & nit<nmaxit
    nit=nit+1; % counter
#+END_SRC

The basic idea is.
That we do.
We also will

#+BEGIN_SRC matlab :tangle test.m :padline no
    y=A*x0;
end
#+END_SRC

Now org-babel-tangle works nicely, but when I try to export the org file
to latex via org-export-dispatch

I obtain a latex file in which the source code is removed. 

What do I miss??


I am asked in the export process whether I want to evaluate the code,
which I don't since it is a simple function not a code to be evaluated.

Re: org babel: %% [removed source block]

[Berry, Charles]

I cannot reproduce your export issue with org 9.1.14.

You need to provide more details.

Perhaps you have a header-arg set that you have not told us about?

What does C-c C-v C-i report when point is in each of your source blocks? I get

Lang: matlab
Properties:
	:header-args 	nil
	:header-args:matlab 	nil
Header Arguments:
	:cache		no
	:exports	code
	:hlines		no
	:noweb		no
	:padline	no
	:results	none
	:session	none
	:tangle		test.m


for the first.

HTH,

Chuck

> On Nov 29, 2018, at 3:38 AM, Uwe Brauer <oub@mat.ucm.es> wrote:
> 
> 
> Hi 
> 
> I have the following org file
> #+BEGIN_SRC matlab :tangle test.m :padline no :results none
> function [ll x]=mitest(A0,x0)
> % initialization 
> format long
> epsi=1.e-3;
> nit=0;
> nmaxit=200;
> Delta=10;
> A=A0;
> while Delta>epsi & nit<nmaxit
>    nit=nit+1; % counter
> #+END_SRC
> 
> The basic idea is.
> That we do.
> We also will
> 
> #+BEGIN_SRC matlab :tangle test.m :padline no
>    y=A*x0;
> end
> #+END_SRC
> 
> Now org-babel-tangle works nicely, but when I try to export the org file
> to latex via org-export-dispatch
> 
> I obtain a latex file in which the source code is removed. 
> 
> What do I miss??
> 
> 
> I am asked in the export process whether I want to evaluate the code,
> which I don't since it is a simple function not a code to be evaluated.
> 
> 
> 

[SOLVED] (was: org babel: %% [removed source block])

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

>>> "Berry," == Berry, Charles <ccberry@ucsd.edu> writes:

   > I cannot reproduce your export issue with org 9.1.14.
   > You need to provide more details.

Sorry for the noise. I just realised that a very very long time ago I
installed a function  remove-src-blk-export, which, uhh, removes source
blocks. 

I removed that function and everything works as expected.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]

Re: [SOLVED]

[Nick Dokos]

Uwe Brauer <oub@mat.ucm.es> writes:

>>>> "Berry," == Berry, Charles <ccberry@ucsd.edu> writes:
>
>    > I cannot reproduce your export issue with org 9.1.14.
>    > You need to provide more details.
>
> Sorry for the noise. I just realised that a very very long time ago I
> installed a function  remove-src-blk-export, which, uhh, removes source
> blocks. 
>
> I removed that function and everything works as expected.

I was going to ask who produced that unfamiliar-looking "%% [removed
source block]" :-) Glad you figured it out.

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

export table to html, don't display certain columns

[Uwe Brauer]

Hi

I know that in radio tables I can skip columns like this

% END RECEIVE ORGTBL firmas \begin{comment} #+ORGTBL: SEND firmas 
orgtbl-to-latex  :skipcols (1) :lend "\\\\ \\hline" :environment 
supertabular 


However how can I achieve that in tables in org file which I want 
to export to html?

Thanks

Uwe Brauer 

[SOLVED] (was: export table to html, don't display certain columns)

[Uwe Brauer]

>>> "Uwe" == Uwe Brauer <oub@mat.ucm.es> writes:

   > Hi
   > I know that in radio tables I can skip columns like this

   > % END RECEIVE ORGTBL firmas \begin{comment} #+ORGTBL: SEND firmas
   > orgtbl-to-latex  :skipcols (1) :lend "\\\\ \\hline" :environment
   > supertabular 

To answer my own question

| / | /     |     |       | /   |
|   | Name  | Res | Letra | Obs |
|---+-------+-----+-------+-----|
|   | Smith |   0 |       |     |
|   | Jones | 1.4 |       |     |
|   | Bond  | 5.6 | *     |     |

All columns starting with / are ignored when exporting. Sorry for the
noise and the double posting.

Uwe Brauer 

Re: [SOLVED]

[Uwe Brauer]

   > To answer my own question

   > | / | /     |     |       | /   |
   > |   | Name  | Res | Letra | Obs |
   > |---+-------+-----+-------+-----|
   > |   | Smith |   0 |       |     |
   > |   | Jones | 1.4 |       |     |
   > |   | Bond  | 5.6 | *     |     |

   > All columns starting with / are ignored when exporting. Sorry for the
   > noise and the double posting.


That is not entirely correct. Someone (I forgot who it was, sorry)
provided me with the following hack


(add-hook 'org-export-before-processing-hook
           'f-ox-filter-table-column-del)


(defun f-ox-filter-table-column-del (back-end)
   "Delete the columns $2 to $> marked as \"/\" on a row with \"/\" in $1.
 If you want a non-empty column $1 to be deleted make it $2 by
 inserting an empty column before or rearrange column order in
 some other way. Make sure \"/\" is in $1 again after that."
   (while (re-search-forward
           "^[ \t]*| +/ +|\\(.*?|\\)?? +\\(/\\) +|" nil t)
     (goto-char (match-beginning 2))
     (org-table-delete-column)
     (beginning-of-line)))


That is very useful and I wonder why there is nothing in org vanilla
(but then it might and I did not find it.)

how do you compose mails in Gnus with org-mode

[Joseph Vidal-Rosset]

Hello,

I know that the subject of my email exists already.
[[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]

But  I'm  loosing  to  much  time   in  searching  the  solution  of  my
"problem". I would be happy to get in Gnus the same function that exists
in mu4e that is org-mu4e-compose-org-mode.  Supposing that I want to reply
to an email, I  would be glad to write my reply in  a org file and, once
finished this reply,  going back to gnus to be  able to org-mime-htmlize
it and send it.
At the moment the only solution that I  have is to quit gnus in order to
make an org file that I copy and paste in the reply. I am convinced that
a better solution  exists, but I am  unable to find it  (ideally the org
file for such a reply would contain the bibliography link by default).

Your help will be very welcome,

Best wishes,

Jo. 

Re: how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:

Hallo

> I know that the subject of my email exists already.
> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]

This works perfectly for your subject:

,----[ C-h f outorg-edit-as-org RET ]
| outorg-edit-as-org is an interactive Lisp function in ‘outorg.el’.
| 
| It is bound to M-# #, <menu-bar> <Outshine> <Edit As Org>.
| 
| (outorg-edit-as-org &optional ARG)
| 
| Convert and copy to temporary Org buffer
| 
| With ARG, act conditional on the raw value of ARG:
| 
| | prefix | raw | action 1          | action 2                       |
| |--------+-----+-------------------+--------------------------------|
| | C-u    | (4) | edit-whole-buffer | ---                            |
| | C-1    |   1 | edit-whole-buffer | insert default export-template |
| | C-2    |   2 | edit-whole-buffer | prompt user for template-file  |
| | C-3    |   3 | edit-whole-buffer | insert & keep default template |
| | C-4    |   4 | edit-whole-buffer | insert & keep template-file    |
| | C-5    |   5 | propagate changes | ---                            |
| 
| [back]
`----

It has already been described several time how to configure
outshine/outorg that it works with message-mode too.

Its actually quite easy. Configure outshine like described in the
README, and add outline-minor-mode to message-mode-hook in your .emacs.

,----
| (add-hook 'emacs-lisp-mode-hook 'outline-minor-mode)
| (add-hook 'message-mode-hook 'outline-minor-mode))
`----

Then with M-# # your email (open in message-mode, gnus) will be opened
in an org-mode buffer for editing in org-mode.

Looks very similar to opening a source-block in org-mode to edit the
sources in the programming language mode.

,----
| [ *unsent followup to Joseph Vidal-Rosset on gmane.emacs.orgmode* ] 
| Exit with M-# (Meta-Key and #)
| * --text follows this line--
| Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
| 
| Hallo
| 
| > I know that the subject of my email exists already.
| > https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html
| 
| This works perfectly for your subject:  [...]
`----

and tells you how to exit again: M-#

-- 
cheers,
Thorsten

Re: how do you compose mails in Gnus with org-mode

[Uwe Brauer]

>>> "Thorsten" == Thorsten Jolitz <tjolitz@gmail.com> writes:

   > Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
   > Hallo

   >> I know that the subject of my email exists already.
   >> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]

   > This works perfectly for your subject:

I just realised that you are the author of that package. Sorry.

I set

(require 'outorg)  
(require 'outshine)
(add-hook 'outline-minor-mode-hook 'outshine-hook-function)

(add-hook 'message-mode-hook 'outline-minor-mode)

But when I fire up outorg-edit-as-org in a reply message I obtain the
error I described in my earlier message.

Uwe Brauer 

Re: how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer <oub@mat.ucm.es> writes:

>>>> "Thorsten" == Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>    > Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
>    > Hallo
>
>    >> I know that the subject of my email exists already.
>    >> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
>
>    > This works perfectly for your subject:
>
> I just realised that you are the author of that package. Sorry.
>
> I set
>
> (require 'outorg)  
> (require 'outshine)
> (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>
> (add-hook 'message-mode-hook 'outline-minor-mode)

ok, maybe I answered the wrong message, does not look that incomplete
actually. Maybe try a copy of my config.

I used outorg-edit-as-org to insert and evaluate these source blocks
directly in this email, so for me it works:

#+BEGIN_SRC emacs-lisp  
 (emacs-version)
#+END_SRC

#+results:
: GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
:  of 2018-02-09

#+BEGIN_SRC emacs-lisp  
 (org-version)
#+END_SRC

#+results:
: 8.2.10

#+BEGIN_SRC emacs-lisp  
 (gnus-version)
#+END_SRC

#+results:
: Gnus v5.13

> But when I fire up outorg-edit-as-org in a reply message I obtain the
> error I described in my earlier message.
>
> Uwe Brauer 


-- 
cheers,
Thorsten

Re: how do you compose mails in Gnus with org-mode

[Uwe Brauer]

>>> "Thorsten" == Thorsten Jolitz <tjolitz@gmail.com> writes:

> Uwe Brauer <oub@mat.ucm.es> writes:
>>>>> "Thorsten" == Thorsten Jolitz <tjolitz@gmail.com> writes:
>> 
>> > Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
>> > Hallo
>> 
>> >> I know that the subject of my email exists already.
>> >> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
>> 
>> > This works perfectly for your subject:
>> 
>> I just realised that you are the author of that package. Sorry.
>> 
>> I set
>> 
>> (require 'outorg)  
>> (require 'outshine)
>> (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>> 
>> (add-hook 'message-mode-hook 'outline-minor-mode)

> ok, maybe I answered the wrong message, does not look that incomplete
> actually. Maybe try a copy of my config.

> I used outorg-edit-as-org to insert and evaluate these source blocks
> directly in this email, so for me it works:
I still can't

> #+BEGIN_SRC emacs-lisp  
>  (emacs-version)
> #+END_SRC


> #+results:
> : GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
> :  of 2018-02-09


GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2018-01-25"



> #+BEGIN_SRC emacs-lisp  
>  (org-version)
> #+END_SRC

Git master from June 2017 so relatively recent

> #+results:
> : 8.2.10

> #+BEGIN_SRC emacs-lisp  
>  (gnus-version)
> #+END_SRC

> #+results:
> : Gnus v5.13

The same here.

>> But when I fire up outorg-edit-as-org in a reply message I obtain the
>> error I described in my earlier message.
>> 
>> Uwe Brauer 

Re: how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer <oub@mat.ucm.es> writes:

>>>> "Thorsten" == Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> Uwe Brauer <oub@mat.ucm.es> writes:
>>>>>> "Thorsten" == Thorsten Jolitz <tjolitz@gmail.com> writes:
>>> 
>>> > Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
>>> > Hallo
>>> 
>>> >> I know that the subject of my email exists already.
>>> >> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
>>> 
>>> > This works perfectly for your subject:
>>> 
>>> I just realised that you are the author of that package. Sorry.
>>> 
>>> I set
>>> 
>>> (require 'outorg)  
>>> (require 'outshine)
>>> (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>>> 
>>> (add-hook 'message-mode-hook 'outline-minor-mode)
>
>> ok, maybe I answered the wrong message, does not look that incomplete
>> actually. Maybe try a copy of my config.
>
>> I used outorg-edit-as-org to insert and evaluate these source blocks
>> directly in this email, so for me it works:
> I still can't
>
>> #+BEGIN_SRC emacs-lisp  
>>  (emacs-version)
>> #+END_SRC
>
>
>> #+results:
>> : GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
>> :  of 2018-02-09
>
>
> GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, Xaw3d
> scroll bars)
>  of 2018-01-25"

Wow, emacs 27 ... I'm on Archlinux and always thought packages a pretty
up-to-date.

Maybe outline has changed somehow between Emacs 25 and Emacs 27?
But I don't think so, the error you send is pretty typical for
incomplete configuration.

> Debugger entered--Lisp error: (error "Before first heading")
>   signal(error ("Before first heading"))
>   error("Before first heading")
>   outline-back-to-heading()

is typical when 

,----
| outorg-prepare-message-mode-buffer-for-editing ()
`----

has not run, it turns this line into a 1st level org headline thus
converting any kind of message body into an org file.

,----
| * --text follows this line--
| Uwe Brauer <oub@mat.ucm.es> writes:
`----

without this, the error is justified - an org file without a single 
org headline is no org file at all.

You could try to write an email with these lines:

,----
| * 1st level
| ** 2nd level
| some text
`----

put point on some text an call outorg, to see if it works.

Another option would be to use edebug:
open outorg.el, put point into 'outorg-edit-as-org', and call M-x
edebug-defun. Then convert an email again, and go step-by-step with
SPACE key, and see how far you get.

When done, call 'load-library' on outorg.el to get rid of edebug
instrumentation.

>> #+BEGIN_SRC emacs-lisp  
>>  (org-version)
>> #+END_SRC
>
> Git master from June 2017 so relatively recent
>
>> #+results:
>> : 8.2.10
>
>> #+BEGIN_SRC emacs-lisp  
>>  (gnus-version)
>> #+END_SRC
>
>> #+results:
>> : Gnus v5.13
>
> The same here.
>
>>> But when I fire up outorg-edit-as-org in a reply message I obtain the
>>> error I described in my earlier message.
>>> 
>>> Uwe Brauer 
>
>
>

-- 
cheers,
Thorsten

Re: how do you compose mails in Gnus with org-mode

[Uwe Brauer]

   > Uwe Brauer <oub@mat.ucm.es> writes:

   > Wow, emacs 27 ... I'm on Archlinux and always thought packages a pretty
   > up-to-date.

Right Ubuntu officially only ships 24, which is pretty old.

Well it is directly form git master, so it is a pre release.
The official release is 26.

   > Maybe outline has changed somehow between Emacs 25 and Emacs 27?
   > But I don't think so, the error you send is pretty typical for
   > incomplete configuration.

I think at the weekend, I will debug the problem. It might be that there
some parts of my init file which are in conflict with your package.

   > is typical when 

   > ,----
   > | outorg-prepare-message-mode-buffer-for-editing ()
   > `----

   > has not run, it turns this line into a 1st level org headline thus
   > converting any kind of message body into an org file.

   > ,----
   > | * --text follows this line--
   > | Uwe Brauer <oub@mat.ucm.es> writes:
   > `----

   > without this, the error is justified - an org file without a single 
   > org headline is no org file at all.

   > You could try to write an email with these lines:

   > ,----
   > | * 1st level
   > | ** 2nd level
   > | some text
   > `----

   > put point on some text an call outorg, to see if it works.

ok
   > Another option would be to use edebug:
   > open outorg.el, put point into 'outorg-edit-as-org', and call M-x
   > edebug-defun. Then convert an email again, and go step-by-step with
   > SPACE key, and see how far you get.

Right.

BTW, you recommended
  (require 'outorg-export)

I installed your package via the package system, so I don't see that
file. Where can I obtain it from?

Re: how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer <oub@mat.ucm.es> writes:

>    > Uwe Brauer <oub@mat.ucm.es> writes:
>
>    > Wow, emacs 27 ... I'm on Archlinux and always thought packages a
>    > pretty
>    > up-to-date.
>
> Right Ubuntu officially only ships 24, which is pretty old.
>
> Well it is directly form git master, so it is a pre release.
> The official release is 26.

Then Archlinux is not that much out of date.

>    > Maybe outline has changed somehow between Emacs 25 and Emacs 27?
>    > But I don't think so, the error you send is pretty typical for
>    > incomplete configuration.
>
> I think at the weekend, I will debug the problem. It might be that there
> some parts of my init file which are in conflict with your package.

A good start would be to try outshine with emacs-lisp mode.
With your outshine config done, write a file like foo.el

,----
| ;;; 1st level header
| ;;;; Sum
| (+ 1 1)
| ;;;; Subtract
| (- 2 1)
`----

or

,----
| ;; * 1st level header
| ;; ** Sum
| (+ 1 1)
| ;; ** Subtract
| (- 2 1)
`----

and see if you got headline fontification and all the outshine
functionality.

If that works, its a message-mode problem.
If not, a genereal problem with your config.

> [...]
> BTW, you recommended
>   (require 'outorg-export)
>
> I installed your package via the package system, so I don't see that
> file. Where can I obtain it from?

It's an extension to outorg:

,----
| ;;; outorg-export.el -- Automated exporting through org
| 
| ;; Author: Jonathan Leech-Pepin <jonathan.leechpepin AT gmail DOT com
| ;; Version: 0.1
| ;; URL: https://github.com/jleechpe/outorg-export
| 
| ;;;; MetaData
| ;; :PROPERTIES:
| ;; :copyright: Jonathan Leech-Pepin
| ;; :copyright-years: 2014+
| ;; :version:  0.3
| ;; :licence:  GPLv3 or later
| ;; :licence-url: http://www.gnu.org/licenses/
| ;; :part-of-emacs: no
| ;; :author:   Jonathan Leech-Pepin
| ;; :author_email: jonathan.leechpepin AT gmail DOT com
| ;; :keywords: emacs org-mode export
| ;; :END:
`----

This is the README

,----
| outorg-export
| =============
| 
| Automated exporting of sections of source files to any format org can export to.
`----

-- 
cheers,
Thorsten

Re: how do you compose mails in Gnus with org-mode

[Uwe Brauer]

>>> "Thorsten" == Thorsten Jolitz <tjolitz@gmail.com> writes:

   > Uwe Brauer <oub@mat.ucm.es> writes:
   >> > Uwe Brauer <oub@mat.ucm.es> writes:
   >> 
   >> > Wow, emacs 27 ... I'm on Archlinux and always thought packages a
   >> > pretty
   >> > up-to-date.
   >> 
   >> Right Ubuntu officially only ships 24, which is pretty old.
   >> 
   >> Well it is directly form git master, so it is a pre release.
   >> The official release is 26.

   > Then Archlinux is not that much out of date.

   >> > Maybe outline has changed somehow between Emacs 25 and Emacs 27?
   >> > But I don't think so, the error you send is pretty typical for
   >> > incomplete configuration.
   >> 
   >> I think at the weekend, I will debug the problem. It might be that there
   >> some parts of my init file which are in conflict with your package.

   > A good start would be to try outshine with emacs-lisp mode.
   > With your outshine config done, write a file like foo.el

   > ,----
   > | ;;; 1st level header
   > | ;;;; Sum
   > | (+ 1 1)
   > | ;;;; Subtract
   > | (- 2 1)
   > `----

   > or

   > ,----
   > | ;; * 1st level header
   > | ;; ** Sum
   > | (+ 1 1)
   > | ;; ** Subtract
   > | (- 2 1)
   > `----

   > and see if you got headline fontification and all the outshine
   > functionality.

That seems to work, I opened your outorg buffer and there everything
worked as expected.


   > If that works, its a message-mode problem.
   > If not, a genereal problem with your config.

   >> [...]
   >> BTW, you recommended
   >> (require 'outorg-export)
   >> 
   >> I installed your package via the package system, so I don't see that
   >> file. Where can I obtain it from?

   > It's an extension to outorg:

Where can I find it, only in that site? It seems not to be in elpa/melpa
and marmelade.

Thanks for the pointer

Uwe 

Re: how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer <oub@mat.ucm.es> writes:

>>>> "Thorsten" == Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>    > A good start would be to try outshine with emacs-lisp mode.
>    > With your outshine config done, write a file like foo.el
>
>    > ,----
>    > | ;;; 1st level header
>    > | ;;;; Sum
>    > | (+ 1 1)
>    > | ;;;; Subtract
>    > | (- 2 1)
>    > `----
>
>    > or
>
>    > ,----
>    > | ;; * 1st level header
>    > | ;; ** Sum
>    > | (+ 1 1)
>    > | ;; ** Subtract
>    > | (- 2 1)
>    > `----
>
>    > and see if you got headline fontification and all the outshine
>    > functionality.
>
> That seems to work, I opened your outorg buffer and there everything
> worked as expected.
>
>
>    > If that works, its a message-mode problem.
>    > If not, a genereal problem with your config.

When I do M-# # writing this mail I see:
,----
| [ *unsent followup to Uwe Brauer on gmane.emacs.orgmode* ] Exit with M-#
| (Meta-Key and #)
| * --text follows this line--
| Uwe Brauer <oub@mat.ucm.es> writes: ...[]
`----

I suggest edebug then, as written, this must run successfully:

,----[ C-h f outorg-prepare-message-mode-buffer-for-editing RET ]
| outorg-prepare-message-mode-buffer-for-editing is a Lisp function in
| ‘outorg.el’.
| 
| (outorg-prepare-message-mode-buffer-for-editing)
| 
| Prepare an unsent-mail in a message-mode buffer for outorg.
| 
| This function assumes that ’--text follows this line--’ (or
| whatever is found inside variable ‘mail-header-separator’) is the
| first line below the message header, is always present, and never
| modified by the user. It turns this line into an ‘outshine’
| headline and out-comments all text below this line - if any.
`----

>    >> [...]
>    >> BTW, you recommended
>    >> (require 'outorg-export)
>    >> 
>    >> I installed your package via the package system, so I don't see that
>    >> file. Where can I obtain it from?
>
>    > It's an extension to outorg:
>
> Where can I find it, only in that site? It seems not to be in elpa/melpa
> and marmelade.

Only available via github I think ....

-- 
cheers,
Thorsten

[SOLVED] (was: how do you compose mails in Gnus with org-mode)

[Uwe Brauer]

   > Uwe Brauer <oub@mat.ucm.es> writes:

   > When I do M-# # writing this mail I see:
   > ,----
   > | [ *unsent followup to Uwe Brauer on gmane.emacs.orgmode* ] Exit with M-#
   > | (Meta-Key and #)
   > | * --text follows this line--
   > | Uwe Brauer <oub@mat.ucm.es> writes: ...[]
   > `----


I found the culprit

(setq message-yank-prefix "   > ")

No idea why I had this, but may be it is ages there. Just moving it out
my init files and everything worked as expected. Thanks

Uwe 

Re: [SOLVED]

[Thorsten Jolitz]

Uwe Brauer <oub@mat.ucm.es> writes:

>    > Uwe Brauer <oub@mat.ucm.es> writes:
>
>    > When I do M-# # writing this mail I see:
>    > ,----
>    > | [ *unsent followup to Uwe Brauer on gmane.emacs.orgmode* ] Exit
>    > | with M-#
>    > | (Meta-Key and #)
>    > | * --text follows this line--
>    > | Uwe Brauer <oub@mat.ucm.es> writes: ...[]
>    > `----
>
>
> I found the culprit
>
> (setq message-yank-prefix "   > ")
>
> No idea why I had this, but may be it is ages there. Just moving it out
> my init files and everything worked as expected. Thanks

Ok, good ... ;-)

-- 
cheers,
Thorsten