Re: [O] Table latex exporting ignores #+ATTR_LATEX:

[Peter Mukhachev]

$ cat table-source.org
#+ATTR_LATEX: :align lp{2cm}l
| Name   | Text | Rationale  |
| height | 18 m | ATC requriment |

# Here I export with M-x org-table-export RET org-table-export-
result.tex RET orgtbl-to-latex RET

It gives the following (note the alignment string is "lll")
$ cat org-table-export-result.tex
\begin{tabular}{lll}
Name & Text & Rationale\\
height & 18 m & ATC requriment\\
\end{tabular}

However, when I dispatch it via M-x org-latex-export-to-latex, the
output is the following (alignment stirg is the same as in org file)
$ tail -n 6 table_source.tex
\begin{tabular}{lp{2cm}l}
Name & Text & Rationale\\
height & 18 m & ATC requriment\\
\end{tabular}
\end{center}
\end{document}%



On Sun, 2018-03-25 at 12:55 +0100, Eric S Fraga wrote:
> On Tuesday, 20 Mar 2018 at 15:43, Peter Mukhachev wrote:
> > (org-table-export) can probably do the thing I want. However,
> > dispatching it with latex backend ends up with #+ATTR_LATEX: line
> > ignored and exports bare table only in its tabular environment.
> > However, I would like to be able to control the alignment either at
> > my
> > .org file with #+ATTR_LATEX (preferred) or at my top-level .tex
> > file
> > using tabular environment.
> 
> Maybe show us a minimal example that does not work?  Ideally, you
> should
> have something along the lines of
> 
> #+attr_latex: ...
> > a | table |
> 
> 

[O] Fix spelling in worg beamer

[Oscar Najera]

Hello,

I was reading about ox-beamer and exporter and came across some spelling
typos. I'm sending you a patch for those with write access. I tried to
register an account on code.orgmode.org but since yesterday I'm still
waiting for the confirmation email.

Best regards,
>From da968587567483fb7f6151ef7d41659381c8cb0f Mon Sep 17 00:00:00 2001
From: Oscar Najera 
Date: Sat, 24 Mar 2018 02:36:05 +0100
Subject: [PATCH] Fix spelling mistakes
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

From: Óscar Nájera 

---
 exporters/beamer/ox-beamer.org | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/exporters/beamer/ox-beamer.org b/exporters/beamer/ox-beamer.org
index d470a9ad..0c532b79 100644
--- a/exporters/beamer/ox-beamer.org
+++ b/exporters/beamer/ox-beamer.org
@@ -210,15 +210,15 @@ below adds support for =only= environment and associates to the letter
'("onlyenv" "O" "\\begin{onlyenv}%a" "\\end{onlyenv}"))
 #+end_src
 
-** Special enviroments
+** Special environments
   :PROPERTIES:
   :CUSTOM_ID: special-environments
   :END:
 
 Environments can be put in a column by setting the =BEAMER_col=
 property on a headline.  It accepts decimal point numbers which is
-interpreted as a fraction of the text width.  If the beadline does not
-have an enviroment the headline text is ignored and all the contents
+interpreted as a fraction of the text width.  If the headline does not
+have an environment the headline text is ignored and all the contents
 are put inside the column environment.
 #+begin_example
   ,* A block in a column
@@ -238,7 +238,7 @@ You can start an appendix by setting the =BEAMER_env= property to
 =appendix= on a headline.  Similarly you can insert notes by setting
 the property to =note= (use =noteNH= to exclude the headline from the
 note).  You can also use Beamer's =againframe= command by setting the
-same property.  The frame being refered to by =againframe= is
+same property.  The frame being referred to by =againframe= is
 specified by the =BEAMER_ref= property.  You can also ignore a
 headline by using =ignoreheading=.  This can also be used to close a
 =column= environment.
-- 
2.16.2

[O] Temporary delay like --2d does not work correctly.

[hhkg]

Hi,

With the latest release, --2d not work correctly.
Use the test case in 
http://lists.gnu.org/archive/html/emacs-orgmode/2013-02/msg00554.html

* TODO 1a
  SCHEDULED: <2018-02-24 Sat +1m --2d>
* TODO 2a
  SCHEDULED: <2018-03-24 Sat +1m --2d>
* TODO 1b
  SCHEDULED: <2018-02-25 Sun +1m --2d>
* TODO 2b
  SCHEDULED: <2018-03-25 Sun +1m --2d>
* TODO 1c
  SCHEDULED: <2018-02-26 Mon +1m --2d>
* TODO 2c
  SCHEDULED: <2018-03-26 Mon +1m --2d>

In the agenda of today ([2018-03-26 Mon]) shows 1a 2a 1b 2b 1c,
but 1a 2a 1b 1c are expected.

Please help fix it.

Thanks,
hhkg

Re: [O] [PATCH] ob-clojure.el support :ns header argument

[stardiviner]

Previous `ob-clojure.el` patch implement method is not good enough. Here 
is a better implementation.

Sorry for this over posting.


On 03/26/2018 09:59 AM, stardiviner wrote:


- support :ns header (as discussed at here 
https://github.com/clojure-emacs/clojure-mode/pull/465#discussion_r158009538)


- supoort inject CIDER outside of project

- support :varinitialization when :session initialization prepare.


On 03/22/2018 01:49 AM, stardiviner wrote:


Two patches

One is to support ob-clojure.el future coming header argument :ns.

The second is to support jack-in CIDER outside of Clojure project by 
default. Not no need to ob-clojure project to be created anymore.






>From 8315773aaee24d49996aa26c543cc56f9adc8414 Mon Sep 17 00:00:00 2001
From: Bastien 
Date: Mon, 26 Mar 2018 11:35:21 +0800
Subject: [PATCH] * ob-clojure.el (org-babel-execute:clojure) support :ns
 header argument.

---
 lisp/ob-clojure.el | 17 +++--
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/lisp/ob-clojure.el b/lisp/ob-clojure.el
index 890f60ada..5989a254b 100644
--- a/lisp/ob-clojure.el
+++ b/lisp/ob-clojure.el
@@ -83,16 +83,21 @@ If the value is nil, timeout is disabled."
 (defun org-babel-expand-body:clojure (body params)
   "Expand BODY according to PARAMS, return the expanded body."
   (let* ((vars (org-babel--get-vars params))
+	 (ns (cdr (assq :ns params)))
 	 (result-params (cdr (assq :result-params params)))
 	 (print-level nil) (print-length nil)
 	 (body (org-trim
 		(if (null vars) (org-trim body)
-		  (concat "(let ["
-			  (mapconcat
-			   (lambda (var)
-			 (format "%S (quote %S)" (car var) (cdr var)))
-			   vars "\n  ")
-			  "]\n" body ")")
+		  (concat
+		   ;; src block specified namespace :ns
+		   "(ns " ns ")"
+		   ;; variables binding
+		   "(let ["
+		   (mapconcat
+		(lambda (var)
+		  (format "%S (quote %S)" (car var) (cdr var)))
+		vars "\n  ")
+		   "]\n" body ")")
 (if (or (member "code" result-params)
 	(member "pp" result-params))
 	(format "(clojure.pprint/pprint (do %s))" body)
-- 
2.16.2

Re: [O] [PATCH] ob-clojure.el support :ns header argument

[stardiviner]

This is an extra patch. Should be with previous email's three patches.


On 03/26/2018 09:59 AM, stardiviner wrote:


- support :ns header (as discussed at here 
https://github.com/clojure-emacs/clojure-mode/pull/465#discussion_r158009538)


- supoort inject CIDER outside of project

- support :varinitialization when :session initialization prepare.


On 03/22/2018 01:49 AM, stardiviner wrote:


Two patches

One is to support ob-clojure.el future coming header argument :ns.

The second is to support jack-in CIDER outside of Clojure project by 
default. Not no need to ob-clojure project to be created anymore.






>From 624e9ab91bb09caf4c438cb9eb1cedb7680755d9 Mon Sep 17 00:00:00 2001
From: Bastien 
Date: Mon, 26 Mar 2018 11:35:21 +0800
Subject: [PATCH] * ob-clojure.el (org-babel-execute:clojure) support :ns
 header argument.

---
 lisp/ob-clojure.el | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/lisp/ob-clojure.el b/lisp/ob-clojure.el
index 890f60ada..62c65e971 100644
--- a/lisp/ob-clojure.el
+++ b/lisp/ob-clojure.el
@@ -55,6 +55,7 @@
 (declare-function slime-eval "ext:slime" (sexp  package))
 
 (defvar nrepl-sync-request-timeout)
+(defvar cider-buffer-ns)
 
 (defvar org-babel-tangle-lang-exts)
 (add-to-list 'org-babel-tangle-lang-exts '("clojure" . "clj"))
@@ -109,7 +110,9 @@ using the :show-process parameter."
   (cider
(require 'cider)
(let ((result-params (cdr (assq :result-params params)))
-	 (show (cdr (assq :show-process params
+	 (show (cdr (assq :show-process params)))
+	 (ns (cdr (assq :ns params
+	 (when ns (setq-local cider-buffer-ns ns))
  (if (member show '(nil "no"))
 	 ;; Run code without showing the process.
 	 (progn
-- 
2.16.2

[O] [PATCH] Fix git-annex-get call in org-attach

[Matt Lundin]

I've attached a patch that fixes a minor issue in org-attach related to
git annex. Basically, it ensures that a shell command is called from
within the git-annex repository (i.e., the org-attach-directory).
Otherwise, the command results in an error because it is called in the
incorrect directory.

Best,
Matt

>From 6158eee0a36f41d90e78ae59df3cfac03f291157 Mon Sep 17 00:00:00 2001
From: Matt Lundin 
Date: Sun, 25 Mar 2018 22:11:09 -0500
Subject: [PATCH] Fix default directory for git-annex checks

* lisp/org-attach.el: (org-attach-annex-get-maybe) Ensure shell
  command that checks whether a git-annex file exists is called from
  within the git-annex repository. Otherwise, it will result in an
  error.
---
 lisp/org-attach.el | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lisp/org-attach.el b/lisp/org-attach.el
index fdf652822..192815f4f 100644
--- a/lisp/org-attach.el
+++ b/lisp/org-attach.el
@@ -320,7 +320,8 @@ the ATTACH_DIR property) their own attachment directory."
 (defun org-attach-annex-get-maybe (path)
   "Call git annex get PATH (via shell) if using git annex.
 Signals an error if the file content is not available and it was not retrieved."
-  (let ((path-relative (file-relative-name path)))
+  (let* ((default-directory (expand-file-name org-attach-directory))
+	 (path-relative (file-relative-name path)))
 (when (and (org-attach-use-annex)
 	   (not
 		(string-equal
-- 
2.16.2

Re: [O] [PATCH] ob-clojure-literate.el add some new functions

[stardiviner]

- support :ns header (as discussed at here 
https://github.com/clojure-emacs/clojure-mode/pull/465#discussion_r158009538)


- supoort inject CIDER outside of project

- support :varinitialization when :session initialization prepare.


On 03/22/2018 01:49 AM, stardiviner wrote:


Two patches

One is to support ob-clojure.el future coming header argument :ns.

The second is to support jack-in CIDER outside of Clojure project by 
default. Not no need to ob-clojure project to be created anymore.




>From bc575705704ebff7f7630cd35ff936844c89f66a Mon Sep 17 00:00:00 2001
From: stardiviner 
Date: Thu, 22 Mar 2018 01:21:22 +0800
Subject: [PATCH 1/3] * ob-clojure-literate.el: CIDER jack-in outside of
 project by default.

---
 contrib/lisp/ob-clojure-literate.el | 50 ++---
 1 file changed, 30 insertions(+), 20 deletions(-)

diff --git a/contrib/lisp/ob-clojure-literate.el b/contrib/lisp/ob-clojure-literate.el
index a7ab1894d..8d419b0b4 100644
--- a/contrib/lisp/ob-clojure-literate.el
+++ b/contrib/lisp/ob-clojure-literate.el
@@ -35,8 +35,10 @@ Don't auto jack in by default for not rude."
   :type 'boolean
   :group 'ob-clojure-literate)
 
-(defcustom ob-clojure-literate-project-location (concat user-emacs-directory "Org-mode/")
-  "The location for `ob-clojure-literate' scaffold project."
+(defcustom ob-clojure-literate-project-location nil
+  "The location for `ob-clojure-literate' scaffold project.
+If it is nil, then `cider-jack-in' will jack-in outside of Clojure project.
+If it is a directory, `ob-clojure-literate' will try to create Clojure project automatically."
   :type 'string
   :group 'ob-clojure-literate)
 
@@ -45,7 +47,7 @@ Don't auto jack in by default for not rude."
 (defvar ob-clojure-literate-session-ns nil)
 (defvar ob-clojure-literate-cider-connections nil)
 
-(defcustom ob-clojure-literate-default-session "*cider-repl ob-clojure*"
+(defcustom ob-clojure-literate-default-session "*cider-repl localhost*"
   "The default session name for `ob-clojure-literate'."
   :type 'string
   :group 'ob-clojure-literate)
@@ -104,23 +106,31 @@ Don't auto jack in by default for not rude."
 (defun ob-clojure-literate-auto-jackin ()
   "Auto setup ob-clojure-literate scaffold and jack-in Clojure project."
   (interactive)
-  (unless (file-directory-p (expand-file-name ob-clojure-literate-project-location))
-(make-directory ob-clojure-literate-project-location t)
-(let ((default-directory ob-clojure-literate-project-location))
-  (shell-command "lein new ob-clojure")))
-  (unless (or
-   (and (cider-connected-p)
-(if (not (null ob-clojure-literate-session))
-(seq-contains cider-connections (get-buffer ob-clojure-literate-session
-   cider-connections
-   (not (null ob-clojure-literate-session)))
-;; return back to original file.
-(if (not (and (= (length (ob-clojure-literate-get-session-list)) 1)
-  (-contains-p (ob-clojure-literate-get-session-list) ob-clojure-literate-default-session)))
-(save-window-excursion
-  (find-file (expand-file-name (concat ob-clojure-literate-project-location "ob-clojure/src/ob_clojure/core.clj")))
-  (with-current-buffer "core.clj"
-(cider-jack-in))
+  (cond
+   ;; jack-in outside of Clojure project.
+   ((null ob-clojure-literate-project-location)
+(if (member (get-buffer "*cider-repl localhost*") cider-connections)
+	(message "CIDER default session already launched.")
+  (cider-jack-in nil)))
+   ((not (null ob-clojure-literate-project-location))
+(unless (file-directory-p (expand-file-name ob-clojure-literate-project-location))
+  (make-directory ob-clojure-literate-project-location t)
+  (let ((default-directory ob-clojure-literate-project-location))
+	(shell-command "lein new ob-clojure")))
+(unless (or
+ (and (cider-connected-p)
+  (if (not (null ob-clojure-literate-session))
+		  (seq-contains cider-connections (get-buffer ob-clojure-literate-session
+ cider-connections
+ (not (null ob-clojure-literate-session)))
+  ;; return back to original file.
+  (if (not (and (= (length (ob-clojure-literate-get-session-list)) 1)
+(-contains-p (ob-clojure-literate-get-session-list) ob-clojure-literate-default-session)))
+  (save-window-excursion
+(find-file (expand-file-name (concat ob-clojure-literate-project-location "ob-clojure/src/ob_clojure/core.clj")))
+(with-current-buffer "core.clj"
+	  (cider-jack-in))
+   ))
 
 (defun ob-clojure-literate-set-local-cider-connections (toggle?)
   "Set buffer local `cider-connections' for `ob-clojure-literate-mode' `TOGGLE?'."
-- 
2.16.2

>From 25e75ded1466b413a0d098041ad40f52e1707432 Mon Sep 17 00:00:00 2001
From: stardiviner 
Date: Thu, 22 Mar 2018 01:43:18 +0800
Subject: [PATCH 2/3] * 

Re: [O] [PATCH] add :session support for ob-js.el

[stardiviner]

Thanks for your refactoring. I must be recklessof this. I will be 
careful next time.



On 03/26/2018 05:09 AM, Nicolas Goaziou wrote:

Hello,

stardiviner  writes:


I attached my new generated patches.


On 03/17/2018 07:14 PM, Nicolas Goaziou wrote:

Some comments follow.

+  (result (if (not (string= (cdr (assq :session params)) "none"))

You can integrate the test above in the `cond':

(cond
   ((string= "none" (cdr (assq :session params))) nil)
   ((string= "*JS REPL*" session) ...)
   ...)

This is modified in new patch.

+ (sit-for .5) (goto-char (point-max))

(sit-for .5)
(goto-char (point-max))

This is in original code, might because ob-js initialize REPL backend
need some time so original author added `site-for`. After test, this
seems does not matter. So remote the sit-for now.

+ (mapc (lambda (var)
+   (insert var) (comint-send-input nil t)
+   (org-babel-comint-wait-for-output session)
+   (sit-for .1) (goto-char (point-max))) var-lines)))
   session))

(dolist (var ...)
 ...)

modified in new patch.

I don't know how to apply master branch new update on my local
`ob-js-session` branch so to get ob-js related commits on top to
generate new patches. (Do you have any idea on this?) The new patches
are behind latest `master` branch. But should be compatible still. If
generating patches based on latest `master` branch commit is must,
I can do that.

I applied you patch. However, I rewrote your commit messages: they need
to refer to modified variables and functions. I also fixed dangling
parenthesis, and fixed a typo in a move from `mapc' + `lambda' to
`dolist'.

Thank you.

Regards,

Re: [O] does this pandoc error look familiar to anybody?

[Samuel Wales]

On 3/25/18, Julius Dittmar  wrote:
> On 25.03.2018 00:58, Samuel Wales wrote:
>> i then tried .latex and went to line 590 and did not find anything
>> unusual, nor that line.
>> but it was a list.  must lists not be nested?
>
> How deeply are those lists nested? LaTeX has a maximum on that as well:
> 4 levels of a specific kind of list, and 6 levels total (so you could
> put for levels of bullet-list into an enumerated list for example).

interesting.  big document [org subtree] with lots of lists and idk
what to do to measure the max depth.  maybe about 4 total though.
mixed 1) and - style.

Re: [O] How to escape # character in #+begin_src bash block for html export?

[Nick Dokos]

Michael Welle  writes:

> Hello,
>
> Abigaile Johannesburg  writes:
>
>> Dear community,
>>
>> I have a minor question about how to escape '#' character in
>> #+begin_src bash block. For example, when I export the source code
>> block for bash, I can use
>>
>> #+begin_src bash
>> $
>> #+end_src
>>
>>
>> But if I want to use # for indicating commands for root or privileged
>> user, if I use
>>
>> #+begin_src bash
>> #
>> #+end_src 
>>
>> then the commands after '#' will be in italics, i.e., they are treated
>> as comments in html export.
>>
>> How do I solve this problem?
> I'm not sure if I understand your problem correctly. # starts a comment
> in shell, and $ denotes (among others maybe) a variable name. In that
> sense 
>
> #+begin_src bash
> $ls
> #+end_src
>
>
> delivers the value of the variable ls. The semantic of $ is not to
> execute the command ls as a non-root user. Same goes for #. If you want
> to put your own semantics into $ and # it might be better to not use a
> bash code block.
>
> If you want to note that some commands in a script needs root privilege,
> maybe something like this would do the trick:
>
> #+begin_src bash
> ls
> su - -c 'fdisk /dev/rdsk/c0d1/p0'
> emacs&
> #+end_src
>
> Regards
> hmw
>
>

As Michael Welle points out

#+begin_src shell
# date
#+end_src

is a do-nothing source block since the command is commented out.

If you are trying to produce documentation and want to show commands
that the user should type then you probably need an example block:

#+begin_example 
# date
#+end_example

-- 
Nick

Re: [O] [PATCH v2 0/3] org-sbe fixes

[Vladimir Panteleev]

Hi,

On 2018-03-25 21:06, Nicolas Goaziou wrote:

I agree "org-sbe" should be rewritten. However, it is specific to tables
because it is meant to be used in a TBLFM line. Its replacement could
live in "org-table.el", though.


What about org-sbe is specific to tables?

I'm thinking that the generic replacement could be used elsewhere, e.g.:

(with-current-buffer some-org-mode-buffer
  (org-sbe-v2 "func" ...args...))

The main obstacle preventing using the current org-sbe in this manner is 
that it is a macro, and will eagerly evaluate some things that it shouldn't.


--
Best regards,
 Vladimir

[O] ical2org release

[Robert Horn]

It's been over a week without problems, so ical2org is released at 1.0

It is a go command line program that is suitable for importing bulk Ical (.ics)
records, Ical attached to emails, and fetching Ical from google.  They
are converted into an org structured file.

Details are at https://github.com/rjhorniii/ical2org-go

The primary problem remaining is one that cannot easily be solved.
There are many sources of appointments.  They do not all implement Ical
the same way.  They do not all handle time zones the same way.  The
strategy that I used is based on the most common behavior that I've
revceived.  It does not alway work right in applying the right time to an
event.

An example of my mu4e integration and systemd integration for google
synchronization is also documented.

-- 
Robert Horn
rjhorn...@gmail.com

Re: [O] [PATCH] contrib: ob-sclang: Fix compilation issue.

[Nicolas Goaziou]

Hello,

Maxim Cournoyer  writes:

> The attached patch fixes a byte compilation issue in ob-sclang.el.

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH] add :session support for ob-js.el

[Nicolas Goaziou]

Hello,

stardiviner  writes:

> I attached my new generated patches.
>
>
> On 03/17/2018 07:14 PM, Nicolas Goaziou wrote:
>> Some comments follow.
>>> +  (result (if (not (string= (cdr (assq :session params)) "none"))
>> You can integrate the test above in the `cond':
>>
>> (cond
>>   ((string= "none" (cdr (assq :session params))) nil)
>>   ((string= "*JS REPL*" session) ...)
>>   ...)
> This is modified in new patch.
>>> + (sit-for .5) (goto-char (point-max))
>> (sit-for .5)
>> (goto-char (point-max))
> This is in original code, might because ob-js initialize REPL backend
> need some time so original author added `site-for`. After test, this
> seems does not matter. So remote the sit-for now.
>>
>>> + (mapc (lambda (var)
>>> +   (insert var) (comint-send-input nil t)
>>> +   (org-babel-comint-wait-for-output session)
>>> +   (sit-for .1) (goto-char (point-max))) var-lines)))
>>>   session))
>>(dolist (var ...)
>> ...)
> modified in new patch.
>
> I don't know how to apply master branch new update on my local
> `ob-js-session` branch so to get ob-js related commits on top to
> generate new patches. (Do you have any idea on this?) The new patches
> are behind latest `master` branch. But should be compatible still. If
> generating patches based on latest `master` branch commit is must,
> I can do that.

I applied you patch. However, I rewrote your commit messages: they need
to refer to modified variables and functions. I also fixed dangling
parenthesis, and fixed a typo in a move from `mapc' + `lambda' to
`dolist'.

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH v2 0/3] org-sbe fixes

[Nicolas Goaziou]

Hello,

Vladimir Panteleev  writes:

> One ugly fix would be to patch over this by checking for some common
> lisp forms that result in a list, such as (list ...) and (quote ...),
> and treat the remaining ones in a backwards-compatible way. However,
> the more time I spend on org-sbe, the more I think that perhaps
> a better approach would be to deprecate org-sbe (or outright remove
> it, I could argue that due to the overwhelming number of flaws its
> mere presence is downright harmful), and replace it with something
> more sensible: a function (not macro) defined somewhere other than
> ob-table (because it is not specific to tables) without any of the
> crazy string escaping logic.
>
> What do you think?

I have reverted your changes from maint.

I agree "org-sbe" should be rewritten. However, it is specific to tables
because it is meant to be used in a TBLFM line. Its replacement could
live in "org-table.el", though.

Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] [PATCH v2 0/3] org-sbe fixes

[Vladimir Panteleev]

On 2018-03-25 20:26, Nicolas Goaziou wrote:

I think this has been applied to the maint branch, but I cannot find a
mention of it in the ORG-NEWS file. Maybe it should be mentioned there
as it is a breaking change. For instance,(I had to modify table formulas like


Sorry, I did not intend this to be a breaking change (for any reasonably 
valid use cases).


The problem is that because org-sbe is a macro, it attempts to parse the 
sexpr without evaluating it. The intention was to check what kind of 
lisp object the argument is, and preserve the old behavior if it's a 
string, but do something more sensible if it's a list. I.e. "foo" and 
(identity "foo") are currently treated differently in org-sbe arguments. 
However, it currently can't do that because the actual evaluation occurs 
elsewhere (the sexpr is stringified mostly-as-is into a babel header and 
then parsed as such).


One ugly fix would be to patch over this by checking for some common 
lisp forms that result in a list, such as (list ...) and (quote ...), 
and treat the remaining ones in a backwards-compatible way. However, the 
more time I spend on org-sbe, the more I think that perhaps a better 
approach would be to deprecate org-sbe (or outright remove it, I could 
argue that due to the overwhelming number of flaws its mere presence is 
downright harmful), and replace it with something more sensible: a 
function (not macro) defined somewhere other than ob-table (because it 
is not specific to tables) without any of the crazy string escaping logic.


What do you think?

--
Best regards,
 Vladimir

Re: [O] [PATCH v2 0/3] org-sbe fixes

[Nicolas Goaziou]

Hello,

Alan Schmitt  writes:

> I think this has been applied to the maint branch, but I cannot find a
> mention of it in the ORG-NEWS file. Maybe it should be mentioned there
> as it is a breaking change. For instance,(I had to modify table formulas like
>
> #+TBLFM: @2$3..@>>$3='(org-sbe call_ledger (bucket (concat "\"" $1 "\"")) 
> (prefix "\"Bucket:Expenses:\""))
>
> into
>
> #+TBLFM: @2$3..@>>$3='(org-sbe call_ledger (bucket $$1) (prefix
> "\"Bucket:Expenses:\""))

I'm going to revert these changes from maint, then. I though that was
innocuous.

Vladimir, would you mind writing a small entry in ORG-NEWS about the
induced changes in master?

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH v2 0/3] org-sbe fixes

[Alan Schmitt]

Hello,

On 2018-03-20 00:07, Nicolas Goaziou  writes:

> Hello,
>
> Vladimir Panteleev  writes:
>
>> OK, here is v2 with table-based tests.
>>
>> Vladimir Panteleev (3):
>>   ob-table: Fix org-sbe's handling of quotes in cell values
>>   ob-table: Fix org-sbe's handling of list arguments
>>   ob-table: Mention passing ranges as lists in org-sbe's documentation
>
> Applied. Thank you!

I think this has been applied to the maint branch, but I cannot find a
mention of it in the ORG-NEWS file. Maybe it should be mentioned there
as it is a breaking change. For instance,(I had to modify table formulas like

#+TBLFM: @2$3..@>>$3='(org-sbe call_ledger (bucket (concat "\"" $1 "\"")) 
(prefix "\"Bucket:Expenses:\""))

into

#+TBLFM: @2$3..@>>$3='(org-sbe call_ledger (bucket $$1) (prefix 
"\"Bucket:Expenses:\""))

Best,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2018-02: 408.35, 2017-02: 406.42


signature.asc
Description: PGP signature

Re: [O] org-latex-image-default-width ignored

[Eric S Fraga]

On Sunday, 25 Mar 2018 at 09:52, Julien Cubizolles wrote:
> Found the cause of the problem, my default configuration exports in
> async mode, so this variable should be set in
> org-export-async-init.el.
>
> Is there a way to have a variable set during export to avoid setting it
> for all exports?

I've never used the async export so I am not sure but maybe check out
the #+bind: directive?

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-347-gd73a5e


signature.asc
Description: PGP signature

Re: [O] Table latex exporting ignores #+ATTR_LATEX:

[Eric S Fraga]

On Tuesday, 20 Mar 2018 at 15:43, Peter Mukhachev wrote:
> (org-table-export) can probably do the thing I want. However,
> dispatching it with latex backend ends up with #+ATTR_LATEX: line
> ignored and exports bare table only in its tabular environment.
> However, I would like to be able to control the alignment either at my
> .org file with #+ATTR_LATEX (preferred) or at my top-level .tex file
> using tabular environment.

Maybe show us a minimal example that does not work?  Ideally, you should
have something along the lines of

#+attr_latex: ...
| a | table |


-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-347-gd73a5e


signature.asc
Description: PGP signature

Re: [O] what settings would make original export to pdf as good as pandoc conversion?

[Eric S Fraga]

On Saturday, 24 Mar 2018 at 17:23, Samuel Wales wrote:
> it looks much better now.  i think the main thing i would want is to
> color links differently from the default red box, like maybe color the
> text "#8968cd" and underline it so it looks kind of like a web page.

You can specify settings to the hyperref package.  See the LaTeX
documentation for that package and then use #+latex_header: to give your
settings.

> also, the pronoun "I" is boldface, which is disconcerting.  Acronyms
> are also, but that is less disconcerting.

Strange.  Maybe create a very small org file and the resulting LaTeX
file for us to look at?

> this seemed to work [when i run it twice at least].  thank you!

Maybe because the first time, the actual configuration is modified but
after the configuration of LaTeX classes has been used by org so it only
takes into effect the second time.  LaTeX classes should probably be
defined in your org initialisation files.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-347-gd73a5e


signature.asc
Description: PGP signature

Re: [O] does this pandoc error look familiar to anybody?

[Julius Dittmar]

On 25.03.2018 00:58, Samuel Wales wrote:

i then tried .latex and went to line 590 and did not find anything
unusual, nor that line.
but it was a list.  must lists not be nested?


How deeply are those lists nested? LaTeX has a maximum on that as well: 
4 levels of a specific kind of list, and 6 levels total (so you could 
put for levels of bullet-list into an enumerated list for example).


HTH,
Julius

Re: [O] How to escape # character in #+begin_src bash block for html export?

[Michael Welle]

Hello,

Abigaile Johannesburg  writes:

> Dear community,
>
> I have a minor question about how to escape '#' character in
> #+begin_src bash block. For example, when I export the source code
> block for bash, I can use
>
> #+begin_src bash
> $
> #+end_src
>
>
> But if I want to use # for indicating commands for root or privileged
> user, if I use
>
> #+begin_src bash
> #
> #+end_src 
>
> then the commands after '#' will be in italics, i.e., they are treated
> as comments in html export.
>
> How do I solve this problem?
I'm not sure if I understand your problem correctly. # starts a comment
in shell, and $ denotes (among others maybe) a variable name. In that
sense 

#+begin_src bash
$ls
#+end_src

delivers the value of the variable ls. The semantic of $ is not to
execute the command ls as a non-root user. Same goes for #. If you want
to put your own semantics into $ and # it might be better to not use a
bash code block.

If you want to note that some commands in a script needs root privilege,
maybe something like this would do the trick:

#+begin_src bash
ls
su - -c 'fdisk /dev/rdsk/c0d1/p0'
emacs&
#+end_src

Regards
hmw

Re: [O] org-latex-image-default-width ignored

[Julien Cubizolles]

Eric S Fraga  writes:

> On Saturday, 24 Mar 2018 at 16:20, Julien Cubizolles wrote:
>> I'd like all inline images resized during beamer and latex export. I
>> tried setting org-latex-image-default-width to ".3\\linewidth" but after
>> export the latex file still uses the default .9\linewidth default. See
>> the following examples.
>
> Your example works for me with up to date org from git.  What version
> are you using?

Found the cause of the problem, my default configuration exports in
async mode, so this variable should be set in
org-export-async-init.el.

Is there a way to have a variable set during export to avoid setting it
for all exports?

Julien.