Re: [O] Emacs+org on Windows 7 pro

[Grant Rettke]

I found Cygwin to make things more difficult for Emacs so I installed
the plain old Windows Emacs and did the following:

https://github.com/grettke/help/blob/master/help.md#windows

https://www.wisdomandwonder.com/article/5647/enabling-png-jpg-and-gif-in-emacs-on-windows

I got Org from Git did the setup as described

https://github.com/grettke/help/blob/master/help.md#help-enables-literate-programming

And then everything else "just worked".
Sincerely,

Grant Rettke


On Mon, Aug 22, 2016 at 9:55 AM, Eric S Fraga  wrote:
> Hello all,
>
> I am asking a n00b question here: what the is best way to get org (+
> emacs obviously) on an MS Windows 7 pro system for use by more than one
> user on the system (multiple accounts with users not having
> Administrator accounts)?  I don't need bleeding edge versions of either
> org or emacs but hopefully something relatively up to date.
>
> The few times I have had to use a Windows system (luckily very seldom
> ;-), I have simply installed cygwin and gone from there.  This is not a
> viable solution in this case due to the users concerned.
>
> Thanks,
> eric
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.94.1, Org release_8.3.5-1070-g190476
>

Re: [O] new link parameters and link abbreviations

[John Kitchin]

I can confirm this happens. I think it happens because the abbreviation
is not listed in org-plain-link-re, so when the bracket link is
activated, no type is ever defined (it is done by a group in the
org-plain-link-re). The type is somewhat fundamental to the activation
function, as it is used to look up all the link properties, and hence
you get the default help (and all other properties too).

I haven't thought of a simple fix though. It would involve adding the
abbreviations to the known link types, and some kind of lookup for when
the type in a link is not in org-link-parameters that resolves the type
to something in org-link-parameters. Since the abbreviations seem to
have quite flexible format, it isn't obvious how to do that robustly,
without changing the abbreviation syntax. 

I would suggest just defining short links ;) It seems like you can
probably build the abbreviation functionality into the follow function
right?


mc writes:

> Yes, with pleasure:
>
> Let's put it the most simple way:
>
>
> 1. Here is my new-link definition:
>
> #+begin_src emacs-lisp
>   (org-link-set-parameters "new-link" :help-echo "show new-link's help echo")
> #+end_src
>
> (it doesn't change matter, if there would be :follow or :store function etc.)
>
>
> 2. the 'tooltip' shows my :help-echo string as expected.
>
> [[new-link:awesome]]
>
>
> 3. Then I add the following abbreviation of the above link:
>
> #+begin_src emacs-lisp
>   (setq org-link-abbrev-alist '(("nl" . "new-link::%s")))
> #+end_src
>
>
> 4. the 'tooltip' does not work but shows the default:
>
> [[nl:awesome]]
>
>
> Hope that clarifies the issue.
>
>
> Thanks once more for your sustained patience making link handling much
> easier and more powerful!
> mc
>
>
>
>> On 20 Aug 2016, at 17:17, John Kitchin  wrote:
>> 
>> that isn't a feature I have used too often. Could you post a small example 
>> that illustrates the problem? Thanks,
>> 
>> 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 Fri, Aug 19, 2016 at 12:13 AM, mc > > wrote:
>> The new link parameters are fabulous!
>> 
>> Only the parameter ':help-echo' seems not to be respected, if a link is used 
>> by an abbreviated form as defined by the 'org-link-abbrev-alist'.
>> 
>> Would be nice, if this could be fixed.
>> 
>> Anyway, thank you for this big step forward,
>> mc
>> 


-- 
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

[O] Org links, URLs and HTML export

[Fabrice Popineau]

Hi,

I'm puzzled by the following.
I write a couple of Org file with HTML export in mind, building a site with
several pages, say:
foo.org -> foo.html
bar.org -> bar.html
I want to insert a link in foo.org that will point to bar.html when
exported.

I can insert : [[http:bar.html]]
However, I would like to be able to insert any kind of relative url.
Specifically, there is no mean to insert something
like : [[http:/bar.html]] which is exported to 
The corresponding export should be 

Strangely, some browsers grok the former (Chrome), but not all of them
(Safari).
Anyway, only the later is correct.

Is there any way to fix exporting relative urls?

If I'm wrong somewhere, please correct me.

Best regards,

Fabrice

Re: [O] How to safely update from ver. 8.2.10 to 8.3.x

[Cook, Malcolm]

> > I would not trust the result from failing to drop the -Q since the -Q is 
> > what
 > prevents your init file from loading, which we are explicitly trying to avoid
 > for the sake of compiling org in a fresh environment.
 > >
 > According to [[info:emacs#Initial Options]], --batch implies -q.
 > About -q and -Q, we have:
 > 
 > ‘-q’
 > ‘--no-init-file’
 >  Do not load any initialization file (*note Init File::).  When
 >  Emacs is invoked with this option, the Customize facility does not
 >  allow options to be saved (*note Easy Customization::).  This
 >  option does not disable loading ‘site-start.el’.
 > [...]
 > ‘-Q’
 > ‘--quick’
 >  Start emacs with minimum customizations.  This is similar to using
 >  ‘-q’, ‘--no-site-file’, ‘--no-site-lisp’, and ‘--no-splash’
 >  together.  This also stops Emacs from processing X resources by
 >  setting ‘inhibit-x-resources’ to ‘t’ (*note Resources::).


Aha - thanks for the rundown. 


 > 
 > So --batch implies -q, which is enough to bypass init.el.  -Q is
 > stronger than -q: it adds ‘--no-site-file’, ‘--no-site-lisp’, and
 > ‘--no-splash’ and inibits X resources.  But AFAIK, only my init.el
 > loads Org, and not site-start.el, which is empty here, or any Lisp
 > file in a site-lisp directory.  I searched every file in
 > /usr/share/emacs/site-lisp for "org" and I didn't find any line that
 > loads Org.
 > 
 > I am an Emacs beginner though, so I may be wrong.

I'm now figuring you're right.

> 
 > --

Re: [O] Emacs+org on Windows 7 pro

[John Kitchin]

Checkout http://github.com/jkitchin/scimax. With git installed it will
install an opinionatedly configured Emacs. Most of my students use it. I
would just have each user install it.

On Monday, August 22, 2016, Eric S Fraga  wrote:

> Hello all,
>
> I am asking a n00b question here: what the is best way to get org (+
> emacs obviously) on an MS Windows 7 pro system for use by more than one
> user on the system (multiple accounts with users not having
> Administrator accounts)?  I don't need bleeding edge versions of either
> org or emacs but hopefully something relatively up to date.
>
> The few times I have had to use a Windows system (luckily very seldom
> ;-), I have simply installed cygwin and gone from there.  This is not a
> viable solution in this case due to the users concerned.
>
> Thanks,
> eric
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.94.1, Org
> release_8.3.5-1070-g190476
>
>

-- 
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

[O] Emacs+org on Windows 7 pro

[Eric S Fraga]

Hello all,

I am asking a n00b question here: what the is best way to get org (+
emacs obviously) on an MS Windows 7 pro system for use by more than one
user on the system (multiple accounts with users not having
Administrator accounts)?  I don't need bleeding edge versions of either
org or emacs but hopefully something relatively up to date.

The few times I have had to use a Windows system (luckily very seldom
;-), I have simply installed cygwin and gone from there.  This is not a
viable solution in this case due to the users concerned.

Thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.94.1, Org release_8.3.5-1070-g190476

Re: [O] Feature request: "Figure #:" in labels of listings

[Clément Pit--Claudel]

On 2016-08-22 16:27, Nicolas Goaziou wrote:
> Done. Thank you.

Works great; thanks!

One small difficulty is that html export uses two separate counters for figures 
and listings, while LaTeX export calls both figures, and uses a single counter. 
This makes it tricky to reference figures in a way that works with both HTML 
and LaTeX: for HTML one needs to write "Figure [[fig:a]] shows x, Listing 
[[lst:b]] shows y" (which exports into "Figure 1 shows x, Listing 1 shows y", 
while for LaTeX one needs to write "Figure [[fig:a]] shows x, Figure [[lst:a]] 
shows y" (which exports into "Figure 1 shows x, Figure 2 shows y"). I don't 
know of an easy way to achieve this.

Potential solutions:
* Using a single counter in HTML, and calling listings "Figure"s, as in LaTeX
* Using two counters in LaTeX as well, though this will require changes to 
existing Org documents, which is not ideal.
* Introducing an org-mode equivalent of \autoref that would insert (and 
hyperlink, which would be nice) "Figure", "Listing", "Section", … as 
appropriate based on the link's target.

Clément.



signature.asc
Description: OpenPGP digital signature

Re: [O] How to safely update from ver. 8.2.10 to 8.3.x

[Jorge]

On 22 August 2016 at 14:19, Cook, Malcolm  wrote:
>> In the last command I forgot to drop the -Q.  But I guess it works either 
>> way.
>
> I would not trust the result from failing to drop the -Q since the -Q is what 
> prevents your init file from loading, which we are explicitly trying to avoid 
> for the sake of compiling org in a fresh environment.
>
According to [[info:emacs#Initial Options]], --batch implies -q.
About -q and -Q, we have:

‘-q’
‘--no-init-file’
 Do not load any initialization file (*note Init File::).  When
 Emacs is invoked with this option, the Customize facility does not
 allow options to be saved (*note Easy Customization::).  This
 option does not disable loading ‘site-start.el’.
[...]
‘-Q’
‘--quick’
 Start emacs with minimum customizations.  This is similar to using
 ‘-q’, ‘--no-site-file’, ‘--no-site-lisp’, and ‘--no-splash’
 together.  This also stops Emacs from processing X resources by
 setting ‘inhibit-x-resources’ to ‘t’ (*note Resources::).

So --batch implies -q, which is enough to bypass init.el.  -Q is
stronger than -q: it adds ‘--no-site-file’, ‘--no-site-lisp’, and
‘--no-splash’ and inibits X resources.  But AFAIK, only my init.el
loads Org, and not site-start.el, which is empty here, or any Lisp
file in a site-lisp directory.  I searched every file in
/usr/share/emacs/site-lisp for "org" and I didn't find any line that
loads Org.

I am an Emacs beginner though, so I may be wrong.

-- 
- I am Brazilian.  I apologize for possibly bad English and I welcome
corrections.
- Please adopt free formats like PDF, ODF, LaTeX, Vorbis, Opus, WebM and 7z.
- Free software for Android: https://f-droid.org/

Re: [O] Feature request: "Figure #:" in labels of listings

[Nicolas Goaziou]

Hello,

Clément Pit--Claudel  writes:

>> What class do you suggest for the listing number, "> class=\"listing-number\">"? 
>
> Sounds good :) 
>
>> If so, should `org-html-style-default' be modified?
>
> Maybe? It currently doesn't mention the related "figure-number" class, so it 
> doesn't really need to mention "listing-number" class IMO; for backwards 
> compatibility, though, we could consider adding 
>
>   .listing-number { display: none; }
>
> to it. I don't like this option too much, since it might create
> confusion in the future (I'd wonder why such a default — visible
> figure numbers, but hidden listing numbers — was chosen). It might be
> better to add this snippet to the NEWS file if users want to revert to
> the old behaviour.

Done. Thank you.


Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: export as ascii issue [8.3.5 (8.3.5-dist @ /usr/share/emacs/site-lisp/org/)]

[Nicolas Goaziou]

Hello,

mount umount  writes:

> i upgraded org-version to the latest 8.3.5 from 7.9 yesterday.
> in the past, in the generated ascii document, there is a time stamp like
> this:
>   title
>   =
> Author: My_name
> Date: 2016-08-17 15:00:00 CST
>
> But after i installed ver8.3.5, it now look like this:
> __
>  title
>  My_name
> __
>
> No time stamp now.

Do you provide a date to the document? E.g.,

#+date: 2016-08-17 15:00:00 CST


Regards,

-- 
Nicolas Goaziou

[O] [PATCH] org-mime supports emacs24

[Chen Bin]

Hi,
I got one patch to make org-mime.el usable at Emacs24. I also clean out
the obsolete code to make it not dependent on ascii and org export
backend any more.


>From a3ea36c0416c0debe831b98dc360a775a2bd1a73 Mon Sep 17 00:00:00 2001
From: Chen Bin 
Date: Sun, 21 Aug 2016 10:16:27 +1000
Subject: [PATCH 1/1] org-mime supports emacs24

- supports Emacs 24 (tested 24.3, 24.4, 24.5)
- clean code
- exported html contains no TOC by default
---
 contrib/lisp/org-mime.el | 203 +--
 1 file changed, 74 insertions(+), 129 deletions(-)

diff --git a/contrib/lisp/org-mime.el b/contrib/lisp/org-mime.el
index 2ced42e..46f0468 100644
--- a/contrib/lisp/org-mime.el
+++ b/contrib/lisp/org-mime.el
@@ -3,9 +3,10 @@
 ;; Copyright (C) 2010-2015 Eric Schulte
 
 ;; Author: Eric Schulte
+;; Maintainer: Chen Bin (redguardtoo)
 ;; Keywords: mime, mail, email, html
-;; Homepage: http://orgmode.org/worg/org-contrib/org-mime.php
-;; Version: 0.01
+;; Homepage: http://github.com/redguardtoo/org-mime
+;; Version: 0.0.3
 
 ;; This file is not part of GNU Emacs.
 
@@ -39,33 +40,32 @@
 ;; package the results into an email handling with appropriate MIME
 ;; encoding.
 ;;
+;; Quick start:
+;; Write mail in message-mode, make sure the mail body follows org format.
+;; Before sending mail, `M-x org-mime-htmlize'
+;;
+;; Setup (OPTIONAL):
 ;; you might want to bind this to a key with something like the
 ;; following message-mode binding
 ;;
 ;;   (add-hook 'message-mode-hook
 ;; (lambda ()
-;;   (local-set-key "\C-c\M-o" 'org-mime-htmlize)))
+;;   (local-set-key (kbd "C-c M-o") 'org-mime-htmlize)))
 ;;
 ;; and the following org-mode binding
 ;;
 ;;   (add-hook 'org-mode-hook
 ;; (lambda ()
-;;   (local-set-key "\C-c\M-o" 'org-mime-org-buffer-htmlize)))
+;;   (local-set-key (kbd "C-c M-o") 'org-mime-org-buffer-htmlize)))
 
 ;;; Code:
-(require 'cl)
-
-(declare-function org-export-string-as "ox"
- (string backend  body-only ext-plist))
-(declare-function org-trim "org" (s  keep-lead))
+(eval-when-compile
+  (require 'cl))
 
-(defcustom org-mime-use-property-inheritance nil
-  "Non-nil means al MAIL_ properties apply also for sublevels."
-  :group 'org-mime
-  :type 'boolean)
+(require 'org)
 
 (defcustom org-mime-default-header
-  "#+OPTIONS: latex:t\n"
+  "#+OPTIONS: latex:t toc:nil H:3\n"
   "Default header to control html export options, and ensure
   first line isn't assumed to be a title line."
   :group 'org-mime
@@ -88,31 +88,29 @@
   :group 'org-mime
   :type 'string)
 
-(defcustom org-mime-html-hook nil
+(defvar org-mime-html-hook nil
   "Hook to run over the html buffer before attachment to email.
-  This could be used for example to post-process html elements."
-  :group 'org-mime
-  :type 'hook)
-
-(mapc (lambda (fmt)
-   (eval `(defcustom
-,(intern (concat "org-mime-pre-" fmt "-hook"))
-nil
-(concat "Hook to run before " fmt " export.\nFunctions "
-"should take no arguments and will be run in a "
-"buffer holding\nthe text to be exported."
-  '("ascii" "org" "html"))
+This could be used for example to post-process html elements.")
 
-(defcustom org-mime-send-subtree-hook nil
-  "Hook to run in the subtree in the Org-mode file before export.")
+(defvar org-mime-pre-html-hook nil
+  "Hook to run before html export.
+Functions should take no arguments and will be run in a
+buffer holding\nthe text to be exported.")
 
-(defcustom org-mime-send-buffer-hook nil
+(defvar org-mime-send-buffer-hook nil
   "Hook to run in the Org-mode file before export.")
 
+(defun org-mime--export-string (s)
+  (if (fboundp 'org-export-string-as)
+  ;; emacs24
+  (org-export-string-as s 'html t)
+;; emacs 23
+(org-export-string s "html")))
+
 ;; example hook, for setting a dark background in  elements
 (defun org-mime-change-element-style (element style)
   "Set new default htlm style for  elements in exported html."
-  (while (re-search-forward (format "<%s\\>" element) nil t)
+  (while (re-search-forward (format "<%s" element) nil t)
 (replace-match (format "<%s style=\"%s\"" element style
 
 (defun org-mime-change-class-style (class style)
@@ -164,17 +162,14 @@ and images in a multipart/related part."
 ('semi (concat
 "--" "<>-{\n"
 "--" "[[text/plain]]\n" plain
-   (if (and images (> (length images) 0))
-   (concat "--" "<>-{\n"
-   "--" "[[text/html]]\n"  html
-   images
-   "--" "}-<>\n")
- (concat "--" "[[text/html]]\n"  html
- images))
+   (when images (concat "--" "<>-{\n"))
+"--" "[[text/html]]\n"  html
+   images
+   (when images (concat "--" "}-<>\n"))
 "--" "}-<>\n"))
 ('vm 

Re: [O] Sharing documents with bibtex bibliography from org to non-org users

[Julian M. Burgos]

Hi Martin,

The best solution I found so far is to export to latex, and then use
pandoc to convert the tex document into word.  You can point pandoc to
your .bib file, so the bibliography gets into the word document, doing
something like this:

pandoc --bibliography /home/julian/Documents/org_files/myrefs.bib -o 
mypaper.docx mypaper.tex

This works ok.  Figures sometimes do not get inserted into the Word document,
and there are other relatively minor issues.  I have not bother looking
very deeply to figure out if they can be solved, I just pass the word
document to my collaborators for editing (so they can use the track
changes options and so for), and I also send the pdf file (from latex)
so they can see exactly how the document would look, in terms of figures
and tables.

When you get your reviews back, you need to manually insert them into
your org document, which is a pain in the back.

An alternative way is to pass the org document to your coworker, so they
can edit them in word directly.  They should ignore all the markup
language, do not use the track changes option, and save the resulting
document as a text file.  Then you can incorporate the changes directly
into your org file using ediff.  But as you said, the markup language
may turn off people that are not very friendly to some code and strange
commands.

A third way would be to export to odt.  I think you can set the exporter
so it uses libre office to convert the resulting file into .doc or
.docx.  I have not tried this very well, so I am not sure how this works
with references, figures and tables.

Hopefully somebody on the list may have a better option,

All the best,

Julian

Martin Leduc writes:

> Hi orgers,
>
> People using org-mode or LaTeX to write scientific papers inevitably 
> face problems when time comes to share a manuscript with co-authors for 
> reviewing. Unless one decides to restrict the choice of his co-authors 
> based exclusively on their knowledge of LaTeX, collaborators generally 
> use Microsoft Word to write their documents.
>
> One way to share LaTeX documents with non-LaTeX users is to simply 
> copy-paste the LaTeX file into a Word document. You can then share this 
> file with other people along with a pdf-compiled version of the 
> manuscript allowing them to see all references, bibliography, equations 
> and figures. This is the most convenient approach for the first author, 
> who can simply copy-paste back the text into a tex file after the rounds 
> of review and then compile the LaTeX manuscript again following some 
> minor debugging.
>
> However, the latter approach may not be suitable in situations where the 
> document is intended to stay into a word format for whatever reason. It 
> could be for instance because you want to be kind with some co-authors 
> that wouldn't pay much interest into a scary document filled with 
> complicated codes.
>
> So I would like to know what are the best known strategies to circumvent 
> the latter issue. To simplify, I accept that I will need to rewrite the 
> equations (and eq. numbers) in the Word document. What I really want, 
> however, is all the citations and the list of references being managed 
> automatically at the step of exporting from org to ODT or to Plain Text.
>
> The only solution I see now is to export the org document to a plain pdf 
> (e.g. with no page numbers) and then to copy-paste the pdf into a Word 
> document. This strategy is cumbersome because a lot of work is generally 
> needed to format the word document (page wrapping, no line breaks 
> between paragraphs, words hyphenation, etc).
>
> Is there any cleaner solutions to this issue ? Or more general ideas on 
> how we could facilitate the sharing of documents containing a bibtex 
> bibliography between org and non-org users ?
>
> Thanks
>
> Martin


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

[O] Invalid search bound (wrong side of point) when creating agenda

[Toby Gee]

Sometimes when I create my agenda I get an "Invalid search bound (wrong side of
point)". Usually this happens when I just filed some todos and hit r on
the Agenda screen; invariably when this happens todo.org isn't
saved. When I save it, the error persists, until I close the todo.org
buffer, and after that everything is OK again for a while.

I generated a backtrace (below, but I haven't been able to find any clues as to
the problem. I'm running an up to date orgmode.

Debugger entered--Lisp error: (error "Invalid search bound (wrong side of 
point)")
  re-search-forward("^\\(?4:[   
]*\\)\\(?1::\\(?2:\\S-+\\):\\)\\(?:\\(?3:$\\)\\|[   
]+\\(?3:.*?\\)\\)\\(?5:[]*\\)$" 158397 t)
  org-element-node-property-parser(158397)
  org-element--current-element(158397 element node-property nil)
  byte-code("\212\214~\210b\210
\205.\n\205.\306\307!\205.\310\311\".\312.\f;\203+.\313\314.\f#\2021.\315\fA@.\"*.2\311\211.3\311.4\204f.\316.5\317
 \211.6.7\320.6P.8\321 ,\203\\.\322.4\311y\210\323\311w\210\324 
\210\202H..2U\203\225.\325\326.9\203\217.\327.\f;\203\205.\313\314.\f#\202\213.\315\fA@.\"*\202\220.\"\210\202H.\330\316.5\317
 \211.6.7\320.6P+.2\316#\203\274.\311y\210\323\311w\210\324 
\210\322.4\202H.dU\203\310.S\202\311..:\331.\f;\203\335.\313\314.\f#\202\343.\315\fA@.\"*\206\351.2b\210\332.:.\f;\203\375.\313\314.\f#\202.
\315\fA@.\"*\211.;X\205..;b\205..\327.:.\f;\203$.\313\314.\f#\202*.\315\fA@.\"*\211.:)\204\353.:\203G.m\203A.:.\202G.:.`.3*\332\f.\f;\203Y.\313\314.\f#\202_.\315\fA@.\"*\206z.\212\316.5\317
 \211.6.7\320.6P.8\333 
\210,`)\f.<.;.9\203\257.`U\203\223.\325\326.<\"\210\202\257.=\211.=\205\246.\334
 \206\246.\335.=\336 
\")\203\257.\325\337\311\"\210\f\204\376.\340.;\304.4\341.<.\f;\203\313.\313\314.\f#\202\321.\315\fA@.\"*$\211.\327.<.>.\211.;\203\353.\342\f\311.>$\202\370.\fA\343\fA@.>#\240\210\f+\210\344\f!\210\332\f.\f;\203.\313\314.\f#\202.\315\fA@.\"*\f\211.:\204&.\f;\205..\345\202..\f@9\205..\f@).?\211.@X\203\313.d.@U\204\313.@b\210.?\311.A.?.A\203\230.\346.?\347\"\203\\.\350\202\305.\346.?\351\"\203h.\322\202\305.\346.?\352\"\203t.\353\202\305.\346.?\354\"\203\200.\355\202\305.\346.?\350\"\203\214.\322\202\305.\346.?\356\"\205\305.\357\202\305.\346.?\353\"\203\244.\353\202\305.\346.?\355\"\203\260.\355\202\305.\346.?\322\"\203\274.\354\202\305.\346.?\357\"\205\305.\357*.4\202\351.?.B>\204\333.\325\326\f\"\210\202\351.\331\f.\f;\203\354.\313\314.\f#\202\362.\315\fA@.\"*\360\f.\f;\203.\313\314.\f#\202\n.\315\fA@.\"*.C.D.9\204H.D\205\340.C\205\340.DW\2044.DU\205\340.?\361>?\205\340.CV\204H.CU\205\340.dU\205\340.3\206O.Db\210\311.3.?\316.A.?.A\203\250.\346.?\347\"\203l.\350\202\325.\346.?\351\"\203x.\322\202\325.\346.?\352\"\203\204.\353\202\325.\346.?\354\"\203\220.\355\202\325.\346.?\350\"\203\234.\322\202\325.\346.?\356\"\205\325.\357\202\325.\346.?\353\"\203\264.\353\202\325.\346.?\355\"\203\300.\355\202\325.\346.?\322\"\203\314.\354\202\325.\346.?\357\"\205\325.\357*.4\f.<.C\211.;*\204\351.\325\326\f\"\210*\311.\202."
 [pos org-element-use-cache org-element--cache cached element property 
derived-mode-p org-mode org-element--cache-find nil :begin get-text-property 0 
plist-get t org-get-limited-outline-regexp "^" outline-previous-heading 
planning " .  \n" beginning-of-line throw exit :parent re-search-backward 
:contents-begin :end outline-next-heading input-pending-p time-less-p 
current-time interrupt org-element--current-element :structure org-add-props 
plist-put org-element--cache-put plain-text eql headline section inlinetask 
plain-list item property-drawer node-property table table-row :contents-end 
(plain-list table) ...] 9)
  org-element--parse-to(158403 t nil)
  
byte-code("\306H\307U\203\f.\310\311\215\210\306H\312U\203\262.\307H.\n\203h.
  
\n.\211.\250\2037.\250\2030.\fW\202F.\f@X\202F.\250\203C.\f@W\202F.\313\314\215*\204h.
A@\211..\307
I\210..\312\312HI\210..\306\312I\210)\315\316\317\"\210)\312H\320H\\./.0\203\207./.0V\203\207.\315\321\322\"\210\202\261.1\203\234./.1Y\203\234.\306\323I\210\202\261.\324./\317.2#.3\325.3I\210\306\323I\210))\307H\320H\325H.4\307H.5>\204\313.\326\327\330\331#\210.4\312H\307H\322C\317\322.6.7.8.9.3.:.;.3\204\364.\332.:!\203\364.\315\316\317\"\210.9\203\341.9\323H\211.<.=\333.=.>\"\206i.\334.=.=.?.=;\203\".\335\307.?.=#\202*.\336.=A@.?\"*.@.=\211.=:\204@.=;\205J.\337\202J.=@9\205J.=@)\340>\203V.@T\202X.@.
\203g.\341.=.>#\202h.   *).7\203\266.9\307H\203\266.  
.;.\211.\250\203\223.\250\203\214.\fW\202\242.\f@X\202\242.\250\203\237.\f@W\202\242.\313\314\215*\204\266.9.8B.8.9\307H.9\202\335.
   
.;.\211.\250\203\322.\250\203\313.\fW\202\341.\f@X\202\341.\250\203\336.\f@W\202\341.\313\314\215*\204\303.
\n\232\203\360.\315\316\317\"\210.6\204\f.2\211.2\205.\342 
\206.\343.2\344 \")\203.\307

Re: [O] Sharing documents with bibtex bibliography from org to non-org users

[Julian M. Burgos]

Hi Martin,

The best solution I found so far is to export to latex, and then use
pandoc to convert the tex document into word.  You can point pandoc to
your .bib file, so the bibliography gets into the word document, doing
something like this:

pandoc --bibliography /home/julian/Documents/org_files/myrefs.bib -o 
mypaper.docx mypaper.tex

This works ok.  Figures sometimes do not get inserted into the Word document,
and there are other relatively minor issues.  I have not bother looking
very deeply to figure out if they can be solved, I just pass the word
document to my collaborators for editing (so they can use the track
changes options and so for), and I also send the pdf file (from latex)
so they can see exactly how the document would look, in terms of figures
and tables.

When you get your reviews back, you need to manually insert them into
your org document, which is a pain in the back.

An alternative way is to pass the org document to your coworker, so they
can edit them in word directly.  They should ignore all the markup
language, do not use the track changes option, and save the resulting
document as a text file.  Then you can incorporate the changes directly
into your org file using ediff.  But as you said, the markup language
may turn off people that are not very friendly to some code and strange
commands.

A third way would be to export to odt.  I think you can set the exporter
so it uses libre office to convert the resulting file into .doc or
.docx.  I have not tried this very well, so I am not sure how this works
with references, figures and tables.

Hopefully somebody on the list may have a better option,

All the best,

Julian

Martin Leduc writes:

> Hi orgers,
>
> People using org-mode or LaTeX to write scientific papers inevitably 
> face problems when time comes to share a manuscript with co-authors for 
> reviewing. Unless one decides to restrict the choice of his co-authors 
> based exclusively on their knowledge of LaTeX, collaborators generally 
> use Microsoft Word to write their documents.
>
> One way to share LaTeX documents with non-LaTeX users is to simply 
> copy-paste the LaTeX file into a Word document. You can then share this 
> file with other people along with a pdf-compiled version of the 
> manuscript allowing them to see all references, bibliography, equations 
> and figures. This is the most convenient approach for the first author, 
> who can simply copy-paste back the text into a tex file after the rounds 
> of review and then compile the LaTeX manuscript again following some 
> minor debugging.
>
> However, the latter approach may not be suitable in situations where the 
> document is intended to stay into a word format for whatever reason. It 
> could be for instance because you want to be kind with some co-authors 
> that wouldn't pay much interest into a scary document filled with 
> complicated codes.
>
> So I would like to know what are the best known strategies to circumvent 
> the latter issue. To simplify, I accept that I will need to rewrite the 
> equations (and eq. numbers) in the Word document. What I really want, 
> however, is all the citations and the list of references being managed 
> automatically at the step of exporting from org to ODT or to Plain Text.
>
> The only solution I see now is to export the org document to a plain pdf 
> (e.g. with no page numbers) and then to copy-paste the pdf into a Word 
> document. This strategy is cumbersome because a lot of work is generally 
> needed to format the word document (page wrapping, no line breaks 
> between paragraphs, words hyphenation, etc).
>
> Is there any cleaner solutions to this issue ? Or more general ideas on 
> how we could facilitate the sharing of documents containing a bibtex 
> bibliography between org and non-org users ?
>
> Thanks
>
> Martin


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

[O] Bug: export as ascii issue [8.3.5 (8.3.5-dist @ /usr/share/emacs/site-lisp/org/)]

[mount umount]

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.

Hi there,

i exported org documents to ascii documents a lot.
i upgraded org-version to the latest 8.3.5 from 7.9 yesterday.
in the past, in the generated ascii document, there is a time stamp like
this:
  title
  =
Author: My_name
Date: 2016-08-17 15:00:00 CST

But after i installed ver8.3.5, it now look like this:
__
 title
 My_name
__

No time stamp now.

Although i like the old style, i think i should move on to the new style
since the developer likes it. But i can't stand with no time stamp.

i did a little home work on this.
In the old version, org-mode invoke "format-time-string" to get the
current date. with M-x : (format-time-string "%T"), i can get current
time successfully.

but in the new version, it uses "org-export-get-date". with M-x :
(org-export-get-date "%T"), i get "nil" now.

could you please take a look into this issue?

Thanks!
umount

Emacs  : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
 of 2016-04-17 on lgw01-04, modified by Debian
Package: Org-mode version 8.3.5 (8.3.5-dist @ /usr/share/emacs/site-lisp/org/)

current state:
==
(setq
 org-tab-first-hook '(org-hide-block-toggle-maybe
  org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-default-hook
  org-babel-speed-command-hook)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-html-format-drawer-function '(lambda (name contents) contents)
 org-latex-format-inlinetask-function 
'org-latex-format-inlinetask-default-function
 org-confirm-shell-link-function 'yes-or-no-p
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-latex-format-drawer-function '(lambda (name contents) contents)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '(#[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook org-show-block-all
append local]
   5]
 #[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook
org-babel-show-result-all append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-ascii-format-drawer-function '(lambda (name contents width) contents)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
  org-babel-execute-safely-maybe)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-html-format-headline-function 'org-html-format-headline-default-function
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 )

Re: [O] How can I get multiple references to the same footnote in org table [ox-latex]

[Nicolas Goaziou]

Kaushal Modi  writes:

> PS: You meant "quite (easy?/difficult?) to solve on the LaTeX
> side"? :)

Pick whichever you want!

More seriously, footnotes are a bit tricky in LaTeX.

Regards,

Re: [O] How to safely update from ver. 8.2.10 to 8.3.x

[Cook, Malcolm]

> In the last command I forgot to drop the -Q.  But I guess it works either way.

I would not trust the result from failing to drop the -Q since the -Q is what 
prevents your init file from loading, which we are explicitly trying to avoid 
for the sake of compiling org in a fresh environment.

~Malcolm

 > 
 > On 22 August 2016 at 12:25, Jorge  wrote:
 > > On 15 August 2016 at 14:29, Cook, Malcolm  wrote:
 > >>   emacs -Q -batch -eval "(progn (require 'package) (add-to-list
 > 'package-archives '(\"org\" . \"http://orgmode.org/elpa/\;))  (package-
 > initialize) (package-refresh-contents) (package-install 'org-plus-contrib))"
 > > Here I plan to drop the "-Q" (because --batch already implies -q,
 > > which I think is enough).  So my command would be
 > > emacs --batch --eval "(progn (require 'package) (add-to-list
 > > 'package-archives '(\"org\" . \"http://orgmode.org/elpa/\;))
 > > (package-initialize) (package-refresh-contents) (package-install
 > > 'org-plus-contrib))"
 > >
 > >> Note: I use org-plus-contrib from melpa instead of org.  If you want just
 > org, you could simply:
 > >>
 > >>   emacs -Q -batch -eval "(progn (require 'package) 
 > >> (package-initialize)
 > (package-refresh-contents) (package-install 'org-plus-contrib))"
 > >
 > > Would not it be
 > > emacs -Q --batch --eval "(progn (require 'package)
 > > (package-initialize) (package-refresh-contents) (package-install
 > > 'org))"
 > > ?
 > >
 > >
 > > --
 > > - I am Brazilian.  I apologize for possibly bad English and I welcome
 > > corrections.
 > > - Please adopt free formats like PDF, ODF, LaTeX, Vorbis, Opus, WebM
 > and 7z.
 > > - Free software for Android: https://f-droid.org/
 > 
 > 
 > 
 > --
 > - I am Brazilian.  I apologize for possibly bad English and I welcome
 > corrections.
 > - Please adopt free formats like PDF, ODF, LaTeX, Vorbis, Opus, WebM and
 > 7z.
 > - Free software for Android: https://f-droid.org/

Re: [O] How to safely update from ver. 8.2.10 to 8.3.x

[Jorge]

In the last command I forgot to drop the -Q.  But I guess it works either way.

On 22 August 2016 at 12:25, Jorge  wrote:
> On 15 August 2016 at 14:29, Cook, Malcolm  wrote:
>>   emacs -Q -batch -eval "(progn (require 'package) (add-to-list 
>> 'package-archives '(\"org\" . \"http://orgmode.org/elpa/\;))  
>> (package-initialize) (package-refresh-contents) (package-install 
>> 'org-plus-contrib))"
> Here I plan to drop the "-Q" (because --batch already implies -q,
> which I think is enough).  So my command would be
> emacs --batch --eval "(progn (require 'package) (add-to-list
> 'package-archives '(\"org\" . \"http://orgmode.org/elpa/\;))
> (package-initialize) (package-refresh-contents) (package-install
> 'org-plus-contrib))"
>
>> Note: I use org-plus-contrib from melpa instead of org.  If you want just 
>> org, you could simply:
>>
>>   emacs -Q -batch -eval "(progn (require 'package) 
>> (package-initialize) (package-refresh-contents) (package-install 
>> 'org-plus-contrib))"
>
> Would not it be
> emacs -Q --batch --eval "(progn (require 'package)
> (package-initialize) (package-refresh-contents) (package-install
> 'org))"
> ?
>
>
> --
> - I am Brazilian.  I apologize for possibly bad English and I welcome
> corrections.
> - Please adopt free formats like PDF, ODF, LaTeX, Vorbis, Opus, WebM and 7z.
> - Free software for Android: https://f-droid.org/



-- 
- I am Brazilian.  I apologize for possibly bad English and I welcome
corrections.
- Please adopt free formats like PDF, ODF, LaTeX, Vorbis, Opus, WebM and 7z.
- Free software for Android: https://f-droid.org/

Re: [O] How to safely update from ver. 8.2.10 to 8.3.x

[Jorge]

On 15 August 2016 at 14:29, Cook, Malcolm  wrote:
>   emacs -Q -batch -eval "(progn (require 'package) (add-to-list 
> 'package-archives '(\"org\" . \"http://orgmode.org/elpa/\;))  
> (package-initialize) (package-refresh-contents) (package-install 
> 'org-plus-contrib))"
Here I plan to drop the "-Q" (because --batch already implies -q,
which I think is enough).  So my command would be
emacs --batch --eval "(progn (require 'package) (add-to-list
'package-archives '(\"org\" . \"http://orgmode.org/elpa/\;))
(package-initialize) (package-refresh-contents) (package-install
'org-plus-contrib))"

> Note: I use org-plus-contrib from melpa instead of org.  If you want just 
> org, you could simply:
>
>   emacs -Q -batch -eval "(progn (require 'package) 
> (package-initialize) (package-refresh-contents) (package-install 
> 'org-plus-contrib))"

Would not it be
emacs -Q --batch --eval "(progn (require 'package)
(package-initialize) (package-refresh-contents) (package-install
'org))"
?


-- 
- I am Brazilian.  I apologize for possibly bad English and I welcome
corrections.
- Please adopt free formats like PDF, ODF, LaTeX, Vorbis, Opus, WebM and 7z.
- Free software for Android: https://f-droid.org/

Re: [O] Feature request: "Figure #:" in labels of listings

[Clément Pit--Claudel]

On 2016-08-15 11:43, Nicolas Goaziou wrote:
> Hello,
>
> [...]
>
> I agreed we can add it unconditionally, using (org-html--translate
> "Listing %d:" info).

Neat, thanks!

> What class do you suggest for the listing number, " class=\"listing-number\">"? 

Sounds good :) 

> If so, should `org-html-style-default' be modified?

Maybe? It currently doesn't mention the related "figure-number" class, so it 
doesn't really need to mention "listing-number" class IMO; for backwards 
compatibility, though, we could consider adding 

  .listing-number { display: none; }

to it. I don't like this option too much, since it might create confusion in 
the future (I'd wonder why such a default — visible figure numbers, but hidden 
listing numbers — was chosen). It might be better to add this snippet to the 
NEWS file if users want to revert to the old behaviour. 

Cheers,
Clément.



signature.asc
Description: OpenPGP digital signature

Re: [O] ob-lua

[Thibault Marin]

>> The attached patch (using git format-patch) is adding test-ob-lua.el and
>> ob-lua.el.  My contribution to ob-lua.el is only a tiny patch on top of
>> Dieter's ob-lua.el but it appears as a new file in the patch, since
>> ob-lua.el is not currently in the repository.
>
> That is not a problem. We can make this appear as two patches.
OK, should I send two patches then?

>
>> I am still a bit confused about this (make test complains about a
>> missing dependency for ob-lua, maybe because it is in contrib/lisp?),
>> but I can run the test using the command line emacs --batch command
>> described in testing/README, and it does not require any change to
>> org-test.el, so I'll run tests this way from now on.
>
> The point is to add it to core Org, not to contrib/, isn't it?
I wasn't sure, attached is a new patch with ob-lua in lisp/.

Thanks,
thibault

>From 61dd519d763db6714be6b66ca4fdd7ddab126317 Mon Sep 17 00:00:00 2001
From: thibault 
Date: Mon, 22 Aug 2016 07:48:06 -0500
Subject: [PATCH] ob-lua.el: Add lua support to org-babel

* lisp/ob-lua.el: Resurrect ob-lua.el from
https://lists.gnu.org/archive/html/emacs-orgmode/2014-05/msg01149.html,
replace deprecated functions `org-babel-get-header' and
`org-babel-trim' by `org-babel--get-vars' and `org-trim'
respectively.  Sessions are not supported.

* testing/test-ob-lua.el: Testing for ob-lua.el.  Test table
variable passing and results with `value' and `output' options.
---
 lisp/ob-lua.el  | 405 
 testing/lisp/test-ob-lua.el | 141 +++
 2 files changed, 546 insertions(+)
 create mode 100644 lisp/ob-lua.el
 create mode 100644 testing/lisp/test-ob-lua.el

diff --git a/lisp/ob-lua.el b/lisp/ob-lua.el
new file mode 100644
index 000..a81ec66
--- /dev/null
+++ b/lisp/ob-lua.el
@@ -0,0 +1,405 @@
+;;; ob-lua.el --- org-babel functions for lua evaluation
+
+;; Copyright (C) 2009-2014 Free Software Foundation, Inc.
+
+;; Authors: Dieter Schoen
+;;	 Eric Schulte, Dan Davison
+;; Keywords: literate programming, reproducible research
+;; Homepage: http://orgmode.org
+
+;; This file is part of GNU Emacs.
+
+;; GNU Emacs is free software: you can redistribute it and/or modify
+;; it under the terms of the GNU General Public License as published by
+;; the Free Software Foundation, either version 3 of the License, or
+;; (at your option) any later version.
+
+;; GNU Emacs is distributed in the hope that it will be useful,
+;; but WITHOUT ANY WARRANTY; without even the implied warranty of
+;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;; GNU General Public License for more details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with GNU Emacs.  If not, see .
+
+;; Requirements:
+;; for session support, lua-mode is needed.
+;; lua-mode is not part of GNU Emacs/orgmode, but can be obtained
+;; from marmalade or melpa.
+;; The source respository is here:
+;; https://github.com/immerrr/lua-mode
+
+;; However, sessions are not yet working.
+
+;; Org-Babel support for evaluating lua source code.
+
+;;; Code:
+(require 'ob)
+(eval-when-compile (require 'cl))
+
+(declare-function org-remove-indentation "org" )
+(declare-function lua-shell "ext:lua-mode" ( argprompt))
+(declare-function lua-toggle-shells "ext:lua-mode" (arg))
+(declare-function run-lua "ext:lua" (cmd  dedicated show))
+
+(defvar org-babel-tangle-lang-exts)
+(add-to-list 'org-babel-tangle-lang-exts '("lua" . "lua"))
+
+(defvar org-babel-default-header-args:lua '())
+
+(defcustom org-babel-lua-command "lua"
+  "Name of the command for executing Lua code."
+  :version "24.5"
+  :package-version '(Org . "8.3")
+  :group 'org-babel
+  :type 'string)
+
+(defcustom org-babel-lua-mode 'lua-mode
+  "Preferred lua mode for use in running lua interactively.
+This will typically be 'lua-mode."
+  :group 'org-babel
+  :version "24.5"
+  :package-version '(Org . "8.3")
+  :type 'symbol)
+
+(defcustom org-babel-lua-hline-to "None"
+  "Replace hlines in incoming tables with this when translating to lua."
+  :group 'org-babel
+  :version "24.5"
+  :package-version '(Org . "8.3")
+  :type 'string)
+
+(defcustom org-babel-lua-None-to 'hline
+  "Replace 'None' in lua tables with this before returning."
+  :group 'org-babel
+  :version "24.5"
+  :package-version '(Org . "8.3")
+  :type 'symbol)
+
+(defun org-babel-execute:lua (body params)
+  "Execute a block of Lua code with Babel.
+This function is called by `org-babel-execute-src-block'."
+  (let* ((session (org-babel-lua-initiate-session
+		   (cdr (assoc :session params
+ (result-params (cdr (assoc :result-params params)))
+ (result-type (cdr (assoc :result-type params)))
+	 (return-val (when (and (eq result-type 'value) (not session))
+		   (cdr (assoc :return params
+	 (preamble (cdr (assoc :preamble params)))
+ (full-body
+	  (org-babel-expand-body:generic
+	   

Re: [O] How can I get multiple references to the same footnote in org table [ox-latex]

[Kaushal Modi]

On Mon, Aug 22, 2016 at 6:11 AM Nicolas Goaziou 
wrote:

> Footnotes in tables are quite to solve on the LaTeX side. Anyway,
> I think this issue is now fixed in master.
>
> Thank you.
>

Thanks! I confirm the fix.

PS: You meant "quite (easy?/difficult?) to solve on the LaTeX side"? :)
-- 

Kaushal Modi

Re: [O] How can I get multiple references to the same footnote in org table [ox-latex]

[Nicolas Goaziou]

Hello,

Kaushal Modi  writes:

> I'm just bumping this email as it could have got missed.

Indeed.

>> Here is a minimum working example:
>>
>> =
>> | abcd | efgh[fn:1] |
>> | ijkl | mnop[fn:1] |
>> | qrst | uvwx   |
>> | y| z  |
>> * Footnotes
>>
>> [fn:1] Some interesting footnote
>>
>> =
>>
>> When I export it to PDF, this is the generated intermediate .tex file:

[...]

>> \begin{center}
>> \begin{tabular}{ll}
>> abcd & efgh\footnotemark\\
>> ijkl & mnop\textsuperscript{\ref{org76fc583}}\\
>> qrst & uvwx\\
>> y & z\\
>> \end{tabular}
>> \end{center}\footnotetext[1]{Some interesting footnote}
>> \end{document}
>> =
>>
>> Notice that the second reference to the same footnote is some random
>> reference: \ref{org76fc583}
>>
>> As a result, the second reference to the exact same footnote looks like
>> this (question marks: ??):
>>
>> [image: pasted1]
>>
>> Is there a fix for this? Or a workaround in org/latex?

Footnotes in tables are quite to solve on the LaTeX side. Anyway,
I think this issue is now fixed in master.

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] ob-lua

[Nicolas Goaziou]

Hello,

Thibault Marin  writes:

> The attached patch (using git format-patch) is adding test-ob-lua.el and
> ob-lua.el.  My contribution to ob-lua.el is only a tiny patch on top of
> Dieter's ob-lua.el but it appears as a new file in the patch, since
> ob-lua.el is not currently in the repository.

That is not a problem. We can make this appear as two patches.

> I am still a bit confused about this (make test complains about a
> missing dependency for ob-lua, maybe because it is in contrib/lisp?),
> but I can run the test using the command line emacs --batch command
> described in testing/README, and it does not require any change to
> org-test.el, so I'll run tests this way from now on.

The point is to add it to core Org, not to contrib/, isn't it?

> Please let me know if some other changes are needed.  Thanks for the
> guidance.

It looks good. Thank you.

I noticed stardiviner (Cc'ed) also provides "ob-lua" on MELPA, although
Dieter's predates it.

Stardiviner, what is the status of your library wrt to the one provided
in this thread ? Is the latter a superset of yours, or are there some
features that could be merged/improved with your code?


Regards,

-- 
Nicolas Goaziou

Re: [O] ox-md.el: Export TOC and Footnotes as Markdown rather than HTML

[Nicolas Goaziou]

Hello,

Jake Romer  writes:

> Thanks for the pointers! I appreciate your patience -- I'm still a noob
> with Org :-)
>
> Here's the updated patch with entries in ORG-NEWS and the manual.

It looks good. However, I realized this is not a "tiny change" (per
), so you
need to sign FSF papers before I can apply it.

Have you done so already ? If not, would you be willing to do it ?
Details are given at
.


Thank you.

Regards,

-- 
Nicolas Goaziou

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

[Nicolas Goaziou]

Hello,

Sriram Karra  writes:

> I find the above reasoning completely broken. Why is the above choice
> considered the right tradeoff when there is no easy way to get something
> sensible (with or without configuration) for display? Do more people export
> rather than view?

The display for clock reports has been changed some months ago in
development version. I think this bug can be closed.

Regards,

-- 
Nicolas Goaziou

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

[Sriram Karra]

On Wed, Mar 18, 2015 at 2:39 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> Ben Finney  writes:
>

 [...]

> The "\emsp" should be space characters (of some kind; either U+0020 SPC
> > or U+2003 EM SPACE) with correct alignment for the character width.
> > Displaying literal "\emsp" is a regression and should not happen.
>
> This is not a regression. This change favors a correct export over
> a correct display.
>

I recently upgraded to a new machine and got the updated org-mode (8.2.10)
with Aquamacs 3.2 and ran into this problem

I find the above reasoning completely broken. Why is the above choice
considered the right tradeoff when there is no easy way to get something
sensible (with or without configuration) for display? Do more people export
rather than view?