Re: Release 9.6

[Charles Millar]

On 12/1/22 18:10, Tim Cross wrote:


Max Nikulin  writes:


On 29/11/2022 13:58, Bastien wrote:

Last but not least: thanks to Ihor his
truly amazing work and for being the de facto maintainer.


I think, Ihor's role in this release is crucial. He spent a lot of time fixing 
bugs and
reviewing patches, not to mention the org-fold framework to overcome performance
limitation of overlays (the latter has been recently addressed in Emacs though).


I agree. The amount of time and effort Ihor has put into org mode is
both crucial and hugely appreciated.

One question I do have is with respect to the new folding code, the
changes in Emacs to improve overlay performance and the correct way
forward.

On one hand, it was an immense amount of work for Ihor to implement a
better performing solution and something I'm sure those with large org
files will appreciate. However, on the other hand, I guess it also puts
a greater burden from a maintenance perspective on org maintainers as
org is now using its own unique approach to hiding/showing content
(folding).

Has anyone done any comparisons between the new overlay implementation
in Emacs 29 and the new folding approach in org 9.6? Is there still
sufficient performance benefit with org's approach over using Emacs
overlays or do we need to seriously consider changing the default back
to native Emacs overlays?


Is this the cause for the behavior I described a few days ago in

Bug org-cycke fails after "replace-string"

Charlie Millar

P.S. Sorry for the typo

Bug org-cycke fails after "replace-string" is

[Charles Millar]

Attached is an example

1. Open all headings etc. show the contents then Collapse all headings
2. Cycle First Heading to show its content
3. Cycle Second Heading to show only the subheadings, but not the 
content of each subheading

3. Cycle Subheading B, to show its content.
4. go to point-min and then replace "Charlie" with a string of your choice

After the replace string is executed, I cannot cycle Subheading A or 
Subheading B


Likewise if all headings are collapsed and I execute a replace-string 
"Chas" I cannot org-cycle through "First heading" and "Second heading", 
but I can cycle "Third heading"


If you add a Fourth heading with the string to be replaced, you cannot 
cycle through any headings if a string.is replaced in the fourth heading


I just pulled Org 9.6 from git. However I noticed this behavior a while 
ago but cannot recall exactly when. I searched the list but no luck.


Org mode version 9.6 (release_9.6 @ /usr/local/share/org-mode/lisp/)

GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.34, 
cairo version 1.16.0) of 2022-11-25


Charlie Millar* First heading
Chas


* Second heading
** Subheading A
Chas
** Subheading B
Chaz
** Subheading C
Chat


* Third heading
some more text

Re: Init.el need just for org-mode?

[Charles Millar]

On 11/2/22 13:31, Renato Pontefice wrote:

I’m sorry for this simply question, but I’m starting using emacs and org-mode 
and I made some confusion.

Init.el

Need just for org -mode? Not for emacs right?

Thank you

Renato

Forgot to mention, and you may already be aware of this,

use

C-h v user-init-file

to find your init.el file

Re: Init.el need just for org-mode?

[Charles Millar]

On 11/2/22 13:31, Renato Pontefice wrote:

I’m sorry for this simply question, but I’m starting using emacs and org-mode 
and I made some confusion.

Init.el

Need just for org -mode? Not for emacs right?


You  may use init.el (or .emacs of .emacs.d/init.el) file for all of 
emacs.not just Org mode.


For instance my init.el includes settings for the display, printer 
selection, what spelling package to use,  and others.


Is also is used to load packages that are not included in the "basic" 
emacs distribution (which contains quite a few).


HTH.

Charlie Millar

:eval yes use and documentation

[Charles Millar]

Org mode version 9.5.1 (release_9.5.1-279-g8908fb @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 28.0.50 (build 344, x86_64-pc-linux-gnu, GTK+ Version 3.24.23, 
cairo version 1.16.0) of 2020-12-31


Here is a use case.

I have many files each with as many as 60 tables that are generated 
using ob -rec. So that the tables are not evaluated during export it is 
convenient for me to set a buffer wide


#+PROPERTY: header-args :eval never-export.

On other hand, each file may also include, under a sub-tree latex source 
code blocks for signature lines, letter heads, etc.


In another sub-tree, called correspondence, those source code blocks are 
called using :noweb yes, such as


  #+begin_src latex :noweb yes
  <>
  #+end_src

\begin{center}
\today
\end{center}

[Body of letter]

  #+begin_src latex :noweb yes
  <>
  #+end_src

If I include in the correspondence sub-tree
:PROPERTIES:
:header-args: :eval yes
:END:

the results are a complete letter, i.e. letterhead followed by the body 
and then signature line.


If I do not include the ":eval yes" property in the sub-tree, only the 
body of the letter results, as expected.


So after all that, here are some questions:

Is ":eval yes" officially allowed and, if so, why is it not documented?

Should it be?

May its use be inferred from other examples such as those from :cache or 
colnames?


I found the following discussion, but it is fairly old:

https://emacs.stackexchange.com/questions/2945/org-babel-eval-with-no-confirmation-is-explicit-eval-yes

Charlie Millar

Fwd: Greater than, less than bug in emacs-lisp source block

[Charles Millar]

Thank you, Arthur.


 Forwarded Message 
Subject: Re: Greater than, less than bug in emacs-lisp source block
Date: Fri, 03 Sep 2021 00:36:23 +0200
From: Arthur Miller 
To: John Kitchin 
CC: Charles Millar , emacs-orgmode@gnu.org 



John Kitchin  writes:


I think this issue is described in
https://emacs.stackexchange.com/questions/50216/org-mode-code-block-parentheses-mismatch.
 There are also some
solutions there.


I wasn't able to get that to work in my Emacs. I did something simpler 
though,

that seems to work for me:

#+begin_src emacs-lisp
(defmacro gt (n1 n2)
  `(> ,n1 ,n2))

(defmacro gte (n1 n2)
  `(>= ,n1 ,n2))

(defmacro lt (n1 n2)
  `(< ,n1 ,n2))

(defmacro lte (n1 n2)
  `(<= ,n1 ,n2))

;; example usage

(dolist (s templist)
 (while (lt (length s) l)
 (setq s (concat s " ")))
 (push (concat "[ " s " ]") kwdlist))

#+end_src

re: Bug Re: Greater than, less than bug in emacs-lisp source block

[Charles Millar]

Thank you, John.

I will give it a try.

However, is this a bug that should be fixed within org source code?

Charlie Millar


On 9/2/21 2:24 PM, John Kitchin wrote:

I think this issue is described in
https://emacs.stackexchange.com/questions/50216/org-mode-code-block-parentheses-mismatch.
There are also some solutions there.


John

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



On Thu, Sep 2, 2021 at 2:10 PM Charles Millar  wrote:


Set up:
GNU Emacs 28.0.50 (build 344, x86_64-pc-linux-gnu, GTK+ Version 3.24.23,
cairo version 1.16.0) of 2020-12-31
Org mode version 9.4.6 (release_9.4.6-637-gd70f28 @
/usr/local/share/org-mode/lisp/)

The following code will evaluate

#+begin_src emacs-lisp
(defun Foo ()
(if (= 2 4) bar))
#+end_src

#+RESULTS:
: Foo
and the opening and closing parentheses match.

If a greater than is inserted instead of equals, thus

#+begin_src emacs-lisp
(defun Foo ()
(if (> 2 4) bar))
#+end_src

it apparently evaluates, however, the closing parenthesis immediately
following the "4" is paired with the opening paren before "if" and not
the opening paren immediately before the ">"

A "less than" results with stranger parenthesis matching - the closing
paren after the "4" matches no others; the closing paren immediately
after "bar" matches the opening paren before "if"

Charlie Millar

Greater than, less than bug in emacs-lisp source block

[Charles Millar]

Set up:
GNU Emacs 28.0.50 (build 344, x86_64-pc-linux-gnu, GTK+ Version 3.24.23, 
cairo version 1.16.0) of 2020-12-31
Org mode version 9.4.6 (release_9.4.6-637-gd70f28 @ 
/usr/local/share/org-mode/lisp/)


The following code will evaluate

#+begin_src emacs-lisp
(defun Foo ()
(if (= 2 4) bar))
#+end_src

#+RESULTS:
: Foo
and the opening and closing parentheses match.

If a greater than is inserted instead of equals, thus

#+begin_src emacs-lisp
(defun Foo ()
(if (> 2 4) bar))
#+end_src

it apparently evaluates, however, the closing parenthesis immediately 
following the "4" is paired with the opening paren before "if" and not 
the opening paren immediately before the ">"


A "less than" results with stranger parenthesis matching - the closing 
paren after the "4" matches no others; the closing paren immediately 
after "bar" matches the opening paren before "if"


Charlie Millar

proposed additions to org-collector code

[Charles Millar]

First, I thank Slava Barinov for his proposed patch to appending a 
#+tblfm line to an org-collector table. Date: 17 Mar 2019 13:22:58 +0300

Message-ID: <87sgvl4wes@gmail.com> (raw)

Attached is my, in all modesty named, cm-org-collector.el in which I 
have added code to prepend name and attribute headers to the table, for 
example:


* orgcollector experiment
:PROPERTIES:
:ID: test
:END:

** Heading One


** Heading two

#+BEGIN: propview :id "test" :cols (ITEM) :noquote t :defaultval "" 
:tblfm "@>$>" :tblname "That" :tblattributes "#+attr_latex: 
somethingelse" :content ""

#+name: That
#+attr_latex: somethingelse
| ITEM|
|-|
| orgcollector experiment |
| Heading One |
| Heading two |
|-|
| |
#+tblfm: @>$>
#+END:

Please note that the :content param must be set to an empty string on 
the #+BEGIN: propview line. Without doing so, upon evaluation of the 
block, the table is updated; however, the following conditions result:

(error "(user-error Not at a table)")
the #+tblfm line is not replaced but an additional #+tblfm line is 
added, and
the #+name and #+attr headers do not reflect any changes to :tblname and 
tblattributes if made in the propview line.


I realize that org-collector is an orphan and that it requires 
additional documentation. (See Bastien's comments to Slava's message.)


That said, if anyone so desires, please consider these additions, make 
all appropriate changes and corrections and patch them to 
org-coolector.el. I believe that this additional code makes 
org-collector more useful as database tool. Instead of having to add 
headers after evaluation, those headers would be inserted at the correct 
point when the propview is evaluated. The resulting table can be called 
from other code blocks. Also, the #+attr header allows, I believe, for 
exporting as desired. (I tried only a latex to pdf and it worked OK.)


I imagine other header params may be included as well.

Charlie Millar

;;; cm-org-collector --- Eric Schulte's org-collector modified to for Charlie

;; Copyright (C) 2008-2021 Free Software Foundation, Inc.

;; Author: Eric Schulte 
;; Keywords: outlines, hypermedia, calendar, wp, experimentation,
;;   organization, properties
;; Homepage: https://orgmode.org
;; Version: 0.01

;; This file is not yet part of GNU Emacs.

;; This program 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, or (at your option)
;; any later version.

;; This program 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 .

;;; Commentary:

;; Pass in an alist of columns, each column can be either a single
;; property or a function which takes column names as arguments.
;;
;; For example the following propview block would collect the value of
;; the 'amount' property from each header in the current buffer
;;
;; #+BEGIN: propview :cols (ITEM amount)
;; | "ITEM"  | "amount" |
;; |-+--|
;; | "December Spending" |0 |
;; | "Grocery Store" |56.77 |
;; | "Athletic club" | 75.0 |
;; | "Restaurant"|30.67 |
;; | "January Spending"  |0 |
;; | "Athletic club" | 75.0 |
;; | "Restaurant"|50.00 |
;; |-+--|
;; | |  |
;; #+END:
;;
;; This slightly more selective propview block will limit those
;; headers included to those in the subtree with the id 'december'
;; in which the spendtype property is equal to "food"
;;
;; #+BEGIN: propview :id "december" :conds ((string= spendtype "food")) :cols (ITEM amount)
;; | "ITEM"  | "amount" |
;; |-+--|
;; | "Grocery Store" |56.77 |
;; | "Restaurant"|30.67 |
;; |-+--|
;; | |  |
;; #+END:
;;
;; Org Collector allows arbitrary processing of the property values
;; through elisp in the cols: property.  This allows for both simple
;; computations as in the following example
;;
;; #+BEGIN: propview :id "results" :cols (ITEM f d list (apply '+ list) (+ f d))
;; | "ITEM" | "f" | "d" | "list"  | "(apply (quote +) list)" | "(+ f d)" |
;; |+-+-+-+--+---|
;; | "run1" |   2 |  33 | (quote (9 2 3 4 5 6 7)) | 36   |35 |
;; | "run2" |   2 |  34 | :na | :na  |36 |
;; | "run3" |   2 |  35 | :na | :na 

Re: Headings and Headlines

[Charles Millar]

On 7/23/21 10:06 PM, Tim Cross wrote:


André A. Gomes  writes:


Hi,

The project's documentation refers to headings and headlines as
synonyms.  Relying on a single definition would be beneficial.  If I had
to choose between the two, I'd go with heading.

If the community finds this valuable, I could prepare a patch.



I think heading is better than headline - to me headline is a line at
the top of the buffer (like a newpaper headline). Note that in addition
to changes in the manual, it will probably be necessary to make changes
to variable and function names in the code. This may require marking
some old names as obsolete and creating aliases to allow a transition to
the new names and avoid breakage etc.



Since org requires outline.el, org.el line 4793, why not follow and 
mirror outline.el conventions?


It appears that outline.el uses
`
"header" for some early set-up(?) functions and

"heading" for what appears to provide the outline itself.

Furthermore, "headline" shows up only in comments, and only four or five 
times, at that.


After all, org is an, "Outline-based notes management and organize."


Best,

Charlie Millar

Re: org-capture-template: table lines including newline of sorts

[Charles Millar]

On 3/16/21 3:34 AM, Uwe Brauer wrote:


> On 3/15/21 5:00 PM, Uwe Brauer wrote:
> My bad; I did not pay attention to a four line comment, so here it is
> again, with the comment and final line for the template, etc.

> (setq org-capture-template '(

> . . . some capture templates

> ("s" "timeslip" table-line
> (file "/mnt/Data/ActiveFiles/timeslips.org")
>;;  (file "d:/ActiveFiles/timeslips.org")
>  "\| %(org-read-date)\| %^{FileName} %i\|
>  %^{Narrative} %i\| %^{Time} %i\| %^{Expense} %i"

> ;; Note that there is no escape and pipe after the final content input
>expansion
> ;; if there were a \| then an empty column is added
> ;; (org-read-date) added 2013-07-12; see Sacha Chua's use of same as in
> ;; the ledger templates below.
>  :empty-lines 1)

> , , , some more capture templates

> ))


I still obtain

| Bad template


Even copying your code without any modifications! I am running org
9.3.7

I'm running org 9.4.4 and emacs 28.0.50, (both from source) on Debian 
testing. According to my notes in my init file I created the template in 
early July 2011, modified it slightly two years later. I do not recall 
any problems with it.


Just to  make sure that there is no problem with the timeslips template, 
at least on my system, I commented out all of the capture templates 
before and after the timeslips template and reloaded my init file. I ran 
org-capture (bound to C-cm). The timeslips came up in the dispatcher and 
it ran OK.


I notice that I was off by a key and typed periods and not semicolons in 
the two lines "some capture templates," and, "some more capture templates."


Charlie Millar

Re: org-capture-template: table lines including newline of sorts

[Charles Millar]

On 3/15/21 5:00 PM, Uwe Brauer wrote:

"CM" == Charles Millar  writes:


> On 3/15/21 10:13 AM, Uwe Brauer wrote:
>>
>>> Hi,
>>> On 3/14/21 1:00 PM, TRS-80 wrote:
>>> You may have to escape the pipes. I did that in a similar capture 
template.
>> Can you give me an example, please?
>>

> HTH

> ("s" "timeslip" table-line
> (file "/mnt/Data/ActiveFiles/timeslips.org")
>  "\| %(org-read-date)\| %^{FileName} %i\|
>  %^{Narrative} %i\| %^{Time} %i\| %^{Expense} %i"

There is a ) missing, no?

I tried

("s" "timeslip" table-line
(file "/home/oub/timeslips.org")
  "\| \| %fromname\|
  :%subject\| %a \| %:date")

But I obtain bad template when executing the code


My bad; I did not pay attention to a four line comment, so here it is
again, with the comment and final line for the template, etc.

(setq org-capture-template '(

. . . some capture templates

("s" "timeslip" table-line
 (file "/mnt/Data/ActiveFiles/timeslips.org")
   ;;   (file "d:/ActiveFiles/timeslips.org")
	  "\| %(org-read-date)\| %^{FileName} %i\| %^{Narrative} 
%i\| %^{Time} %i\| %^{Expense} %i"


;; Note that there is no escape and pipe after the final content input 
expansion

;; if there were a \| then an empty column is added
;; (org-read-date) added 2013-07-12; see Sacha Chua's use of same as in
;; the ledger templates below.
 :empty-lines 1)

, , , some more capture templates

))

Re: org-capture-template: table lines including newline of sorts

[Charles Millar]

On 3/15/21 10:13 AM, Uwe Brauer wrote:



Hi,
On 3/14/21 1:00 PM, TRS-80 wrote:
You may have to escape the pipes. I did that in a similar capture template.


Can you give me an example, please?



HTH

("s" "timeslip" table-line
(file "/mnt/Data/ActiveFiles/timeslips.org")
	  "\| %(org-read-date)\| %^{FileName} %i\| %^{Narrative} 
%i\| %^{Time} %i\| %^{Expense} %i"



Charlie Millar

Re: org-capture-template: table lines including newline of sorts

[Charles Millar]

Hi,

On 3/14/21 1:00 PM, TRS-80 wrote:

On 2021-03-13 02:24, Uwe Brauer wrote:

Hi

Currently I have the following setting for one org-capture-template:


("mu" "Stat+Num:Exercises English"
table-line (file+headline "~/Somefile.org" "Exercise Group-E")
"| %:fromname|%:fromaddress |
%(my-extract-cc)|%^{Sheet|1|2|3|4|5|6}|%^{Exercise|1|} |  %a|%:date |
"  :prepend t
)

That line is too long, I'd like something like this
("mu" "Stat+Num:Exercises English"
table-line (file+headline "~/Somefile.org" "Exercise Group-E")
"| %:fromname|%:fromaddress\n
%(my-extract-cc)|%^{Sheet|1|2|3|4|5|6}|%^{Exercise|1|} |  %a|%:date |
"  :prepend t
)

Or

("mu" "Stat+Num:Exercises English"
table-line (file+headline "~/Somefile.org" "Exercise Group-E")
"| %:fromname|%:fromaddress\n
%(my-extract-cc)|%^{Sheet|1|2|3|4|5|6}|%^{Exercise|1|} |  %a|%:date |
"  :prepend t
"|   | %(my-extract-cc) |   |   |   |   |   |   |    |  |   |   |    |
   | "  :prepend t
)


But nothing worked, any ideas?

Thanks and regards

Uwe Brauer


Do you need to add more pipes to keep the table structure on the line
after the newline?

Cheers,
TRS-80


You may have to escape the pipes. I did that in a similar capture template.

Charlie Millar

Call org-collector dynamic block

[Charles Millar]

I'd like to format (latex export) the output from a captured 
org-collector dynamic block by  using the resulting org-collector table 
as a variable for  source code block.


I have place #+name: before the collector block.

#+name: bar
#+BEGIN: propview :id "conveyances" :match "BreezyCorners" :cols (ITEM 
CUSTOM_ID CONVEYANCEDATE RECORDDATE BOOK PAGE) :colnames (Title ID Dated 
Recorded Book Page) :noquote t :defaultval "" :inherit (CONVEYANCEDATE 
DEEDDATE RECORDDATE BOOK PAGE)


#+END:

When called from the source block (using :var table=bar) results
(error "Reference not found")

I have placed the #+name inside the block, e.g.,

#+BEGIN: propview :id "conveyances" :match "BreezyCorners" :cols (ITEM 
CUSTOM_ID CONVEYANCEDATE RECORDDATE BOOK PAGE) :colnames (Title ID Dated 
Recorded Book Page) :noquote t :defaultval "" :inherit (CONVEYANCEDATE 
DEEDDATE RECORDDATE BOOK PAGE)

#+name: bar
#+END:

When I attempt to generate the table -Lisp error: (error "(user-error 
Not at a table)")


The above idea was in StackOverflow concerning a columnview block - see

https://emacs.stackexchange.com/questions/30700/calling-dynamic-blocks.

Additionally I have reviewed the org-collector source code and I find no 
provision concerning formatting the output, such as, I believe, 
clocktable has in its code. I have attempted to use


#+BEGIN: propview :id "conveyances" :match "BreezyCorners" :cols (ITEM 
CUSTOM_ID CONVEYANCEDATE RECORDDATE BOOK PAGE) :colnames (Title ID Dated 
Recorded Book Page) :noquote t :defaultval "" :inherit (CONVEYANCEDATE 
DEEDDATE RECORDDATE BOOK PAGE)

#+attr_latex: :mode table :align p{150pt}p{10pt}p{75pt}p{75pt}p{20pt}p20pt}
#+END:

again the Lisp error: (error "(user-error Not at a table)")

Any suggestions?

Charlie Millar

Re: accounting

[Charles Millar]

On 1/4/21 3:54 AM, Uwe Brauer wrote:


Hi

https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-ledger.html

Points out how to use ledger within org mode.

Is there any simpler solution?

Regards

Uwe Brauer


If "simpler" means just making entries into your ledger.dat file using 
orgmode you may wish to refer to Sacha Chua's capture template for that 
very purpose. She posted it a few years ago.


https://sachachua.com/blog/2010/11/emacs-recording-ledger-entries-with-org-capture-templates/

Charlie Millar

Re: [PATCH] doc/org-manual.org: Extend table formulas Lisp form documentation

[Charles Millar]

On 11/18/20 2:42 PM, TEC wrote:


I have 2c on the use of "interpolated".

1. I tend to think of "interpolated" in terms of it's mathematical
   meaning
2. The other denotations relate to insertion and renewing, which simply
   doesn't fit.

I appreciate that other people may have used this too, but as I see it
that just means that other people have engaged in strange word choices.

Suggested alternatives: Substituted, transpiled, or translated.

Timothy.

-

For context, here's the definition, etymology, and symonyms.

Definition
  Intransitive Verb
   1. To renew; to carry on with intermission. [Obs.] 
   2. To alter or corrupt by the insertion of new or foreign 
  matter; especially, to change, as a book or text, by the
  insertion of matter that is new, or foreign to the purpose
  of the author.
   3. (Mathematics) To fill up intermediate terms of, as of a series, 
  according to the law of the series; to introduce, as a
  number or quantity, in a partial series, according to the
  law of that part of the series.
  Adjective
   1. Inserted in, or added to, the original; introduced; 
  foisted in; changed by the insertion of new or spurious
  matter.

   2. (Math.) 
​  (a) Provided with necessary interpolations; as, an 
  interpolated table.
​  (b) Introduced or determined by interpolation; as, 
  interpolated quantities or numbers.

​​Etymology
 
​​​interpolate verb 

1610s, "to alter or enlarge (a writing) by inserting new material," from 
Latin interpolatus, past participle of interpolare "alter, freshen up, 
polish;" of writing, "falsify," from inter "among, between" (see inter-) 
+ polare, which is related to polire "to smoothe, polish," from PIE root 
*pel- ( 5) "to thrust, strike, drive," the connecting notion being "to 
full cloth" [Watkins].


Sense evolved in Latin from "refurbish," to "alter appearance of," to 
"falsify (especially by adding new material)." Middle English had 
interpolen (early 15c.) in a similar sense. Related: Interpolated; 
interpolating.


​​Synonyms
 
​​​verb adjective 
1. Insert (wrongfully),  foist in.
2. (Math .) Introduce, intercalate (terms to complete a series).


Tim Cross  writes:


Daniele Nicolodi  writes:


On 16/11/2020 11:25, Eric S Fraga wrote:

Daniele,

this looks good.  One minor pedantic point: I think you mean
"interpreted" when you say "interpolated" (several times in the
text).  Otherwise, this is a very useful addition to the manual.


Thank you for reading and for the comment.

"interpolated" looks strange to me in this context too, but it is the
word that is currently used in the manual. I decided to stick to this
term for consistency, however, I haven't check if it is used with the
same meaning elsewhere.

I don't think it is wrong to use "interpolated", but if you thing it
should be changed I can change it and check the manual for consistency.
However, I don't think "interpreted" is the right word either. Probably
"replaced" or "substituted" are better choices in this context.



I agree. Interpolated is consistent with manuals for other programming
languages which have similar functionality. However, org is also used by
a more diverse community than typical programming languages, so perhaps
'replaced' or 'substituted' would be a better choice?




Just my 2 cents, not being a programmer so I see one way that 
interpolate may be correct


Are the cell references actually inserted into the lisp form when the 
formula is evaluated Please note that the word "the" is used not an 
indefinite 'a", i.e.


Cell table +references are interpolated into the Lisp form before execution

as opposed to

Cell table
+references are interpolated into a lisp form before execution

Charlie Millar

Re: Bug: org-table-sort-lines returns error [9.3.7 (release_9.3.7-705-gea9463 @ /home/oub/emacs/site-lisp/packages/org/)]

[Charles Millar]

On 8/13/20 8:03 AM, Uwe Brauer wrote:

"NG" == Nicolas Goaziou  writes:



Hello,
Uwe Brauer  writes:



I am running emacs 28 master 84ec57fe06e187f41a3546131d5dae3b185c3511

Steps to reproduce

#+TBLNAME: original
| Day   | Color | Level | Quantity |

|---+---+---+--|
| Monday| Red   |30 |   11 |
| Monday| Blue  |25 |3 |
| Tuesday   | Red   |51 |   12 |
| Tuesday   | Red   |45 |   15 |
| Tuesday   | Blue  |33 |   18 |
| Wednesday | Red   |27 |   23 |
| Wednesday | Blue  |12 |   16 |
| Wednesday | Blue  |15 |   15 |
| Thursday  | Red   |39 |   24 |
| Thursday  | Red   |41 |   29 |
| Thursday  | Red   |49 |   30 |
| Friday| Blue  | 7 |5 |
| Friday| Blue  | 6 |8 |
| Friday| Blue  |11 |9 |

Put curso on number 30 in the third column call the function and select
numercial sorting, a bug trace occurs which I attach.



I cannot reproduce it. I'm using neither Emacs 28 nor Org Ref, tho.



I run undo, widen and repeat the operation and then it works

   ^
???



You didn't say you were narrowing something.



Anyway, for the time being the error may come from Org Ref 
(org-ref-delete-labels).



I run more tests.
I upgraded org-ref

Still the following table gives me problems


#+TBLNAME: original
| Day   | Color | Level | Quantity |
|---+---+---+--|
| Tuesday   | Red   |51 |   12 |
| Thursday  | Red   |49 |   30 |
| Tuesday   | Red   |45 |   15 |
| Thursday  | Red   |41 |   29 |
| Thursday  | Red   |39 |   24 |
| Tuesday   | Blue  |33 |   18 |
| Monday| Red   |30 |   11 |
| Wednesday | Red   |27 |   23 |
| Monday| Blue  |25 |3 |
| Wednesday | Blue  |15 |   15 |
| Wednesday | Blue  |12 |   16 |
| Friday| Blue  |11 |9 |
| Friday| Blue  | 7 |5 |
| Friday| Blue  | 6 |8 |


While  this table



| Day   | Color | Level | Quantity |
|---+---+---+--|
| Tuesday   | Red   |51 |   12 |
| Thursday  | Red   |49 |   30 |
| Tuesday   | Red   |45 |   15 |
| Thursday  | Red   |41 |   29 |
| Thursday  | Red   |39 |   24 |
| Tuesday   | Blue  |33 |   18 |
| Monday| Red   |30 |   11 |
| Wednesday | Red   |27 |   23 |
| Monday| Blue  |25 |3 |
| Wednesday | Blue  |15 |   15 |
| Wednesday | Blue  |12 |   16 |
| Friday| Blue  |11 |9 |
| Friday| Blue  | 7 |5 |
| Friday| Blue  | 6 |8 |


Works fine. When I said it worked in the past I should also add, that I
usually did not use tablenames (labels)

@John I think this is your call?

Uwe

Two or three days ago when I started emacs it did not load correctly. ,I 
commented out my org-ref setup and no problem loading emacs.


Current set up
GNU Emacs 28.0.50 (build 214, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, 
cairo version 1.16.0) of 2020-08-13
Org mode version 9.3.7 (release_9.3.7-708-g5417e3 @ 
/usr/local/share/org-mode/lisp/)


I uncommented my org-ref setup in my init file and upon restarting the 
following error was generated:


Debugger entered--Lisp error: (void-variable browse-url-mosaic-program)

byte-code("\306\300!\203\n\0\10\206\13\0\307\310B\11\311B\n\312B\13\313B\f\314B\15\315B\16\26\316B\16\27\317B\16\30\320B\16\31\321B\16\32\322B\16\33..." 
[w3m-command browse-url-firefox-program helm-browse-url-chromium-program 
helm-browse-url-conkeror-program helm-browse-url-opera-program 
helm-browse-url-uzbl-program boundp "/usr/bin/w3m" w3m-browse-url 
browse-url-firefox helm-browse-url-chromium helm-browse-url-conkeror 
helm-browse-url-opera helm-browse-url-uzbl browse-url-kde 
browse-url-gnome-moz browse-url-mozilla browse-url-galeon 
browse-url-netscape browse-url-mosaic browse-url-text-xterm (("emacs" . 
eww-browse-url)) browse-url-kde-program browse-url-gnome-moz-program 
browse-url-mozilla-program browse-url-galeon-program 
browse-url-netscape-program browse-url-mosaic-program 
browse-url-xterm-program] 14)
  (defvar helm-browse-url-default-browser-alist (byte-code 
"\306\300!\203\n\0\10\206\13\0\307\310B\11\311B\n\312B\13\313B\f\314B\15\315B\16\26\316B\16\27\317B\16\30\320B\16\31\321B\16\32\322B\16\33..." 
[w3m-command browse-url-firefox-program helm-browse-url-chromium-program 
helm-browse-url-conkeror-program helm-browse-url-opera-program 
helm-browse-url-uzbl-program boundp "/usr/bin/w3m" w3m-browse-url 
browse-url-firefox helm-browse-url-chromium helm-browse-url-conkeror 
helm-browse-url-opera helm-browse-url-uzbl browse-url-kde 
browse-url-gnome-moz browse-url-mozilla browse-url-galeon 
browse-url-netscape browse-url-mosaic browse-url-text-xterm (("emacs" . 
eww-browse-url)) browse-url-kde-program 

Re: Bug - all org files open as if visibilty is set to "showeverything"

[Charles Millar]

Nicholas,
-- cut --


That is correct. It's been discussed in the list and Nicolas announced that it's
been merged into master on Tuesday. Look for the thread entitled

[RFC] Change default value for `org-startup-folded'?

It can also be found at 


C-h v org-startup-folded RET

You can get the previous default by setting it to t in your init file.



Thanks.

Before posting I searched the list and did not find the thread or, more 
likely, it was included in the search results and did not realize it.


Charlie

Manual 2.2.2 and 16.7 needs to amended

[Charles Millar]

I think the following changes are required: in the manual, if they 
already have not been made in the past few hours:


2.2.2
When Emacs first visits an Org file, the global state is set to
SHOWEVERYTHING, i.e., all file content is visible(1).

(No idea if the footnote needs to be changed.)

Likewise in section 16.7 the explanation for #+STARTUP, to wit:

responding variable for global default
settings is ‘org-startup-folded’ with a default value of ‘t’, which
is the same as ‘overview’.

needs amendment to reflect the current change in default visibility 
behavior.


Current version Org mode version 9.3.6 (release_9.3.6-619-g434940 @ 
/usr/local/share/org-mode/lisp/)


Best,

Charlie

Re: Bug - all org files open as if visibilty is set to "showeverything"

[Charles Millar]

Hoi Nicholas,

On 5/13/20 2:13 PM, Nicolas Goaziou wrote:

Hello,

Charles Millar  writes:


In the last two or three days, all my org files open as if I have set
the visibility in every file to

#+STARTUP: showeverything



[...]


As far as I recall, I have not changed any settings in my init or
elsewhere.


I changed `org-startup-folded' default value to `showeverything'
yesterday.

You may want to use:

   (setq org-startup-folded t)

to get the old behaviour back.


Thanks.

I did that already.

However, I still stand by comments that I forwarded in reply to Josiah's 
response. I do not believe that the original message was clear.


Charlie

Re: Bug - all org files open as if visibilty is set to "showeverything"

[Charles Millar]

On 5/13/20 1:58 PM, Josiah Schwab wrote:

As far as I recall, I have not changed any settings in my init or elsewhere.


The default was changed.  See

https://lists.gnu.org/archive/html/emacs-orgmode/2020-04/msg00452.html
https://lists.gnu.org/archive/html/emacs-orgmode/2020-05/msg00201.html

Josiah



Thank you.

I recall seeing these messages, but did not realize that this change was 
going to effect all org files and by default, use lots and lots of space 
when an org file is opened.


As dar as I am concerned,the past default was OK and it took only a 
brief time to learn the past behavior and the visibility settings on a 
per file basis.


I may be only a user but if I had I would have voted no.

Charlie Millar

Bug - all org files open as if visibilty is set to "showeverything"

[Charles Millar]

Hi,

In the last two or three days, all my org files open as if I have set 
the visibility in every file to


#+STARTUP: showeverything


Org mode version 9.3.6 (release_9.3.6-619-g434940 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 28.0.50 (build 123, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, 
cairo version 1.16.0) of 2020-05-13


As far as I recall, I have not changed any settings in my init or elsewhere.

Charlie Millar

Re: bug org-open-at-point zotero link

[Charles Millar]

Hi,

Re-posting.

Have I missed documentation that states that "org-open-at-point os not 
available for a Zotero (Zotxt) link?


On 4/10/20 9:45 AM, Charles Millar wrote:

Hi,

Current versions

Org mode version 9.3.6 (release_9.3.6-472-g8e3b73 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 28.0.50 (build 91, x86_64-pc-linux-gnu, GTK+ Version 3.24.14, 
cairo version 1.16.0) of 2020-04-10


 From reading the documentation zotero is a valid link type and I would 
expect that org-open-at-point, C-c C-o, would open the following link


[[zotero://select/items/1_XPZL74VM][Behr, Michael. “A Research Workflow 
with Zotero and Org Mode.” mkbehr.com, September 19, 2015. 
http://www.mkbehr.com/posts/a-research-workflow-with-zotero-and-org-mode/.]] 



Instead I receive the following error

request-default-error-callback: http://127.0.0.1:23119/zotxt/select error

I saved the link in Zotero with a snapshot.

I can open the link using org-zotxt-open-attachement.

If, however I save the link without a snapshot,

[[zotero://select/items/1_3AH6WNKZ][“A Research Workflow with Zotero and 
Org Mode | Mkbehr.Com.” Accessed April 10, 2020. 
http://www.mkbehr.com/posts/a-research-workflow-with-zotero-and-org-mode/.]] 



and try org-zotxt-open-attachment I receive the following error

No attachments for item!
deferred error : (error "No attachments for item!")

If I org-open-at-point for the same link I receive

request-default-error-callback: http://127.0.0.1:23119/zotxt/select error

In the first instance is this a bug? Or is there a setting that I have 
to add to my localhost?


In the second case is this a org-zotxt or Zotero issue?

Charlie Millar

bug? org-lint issues warning when ;PROPERTIES: drawer before first headline

[Charles Millar]

Org mode version 9.3.6 (release_9.3.6-528-gf874b6 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 28.0.50 (build 102, x86_64-pc-linux-gnu, GTK+ Version 3.24.18, 
cairo version 1.16.0) of 2020-04-21


AFAIU this is now allowed. Should org-lint be modified?

bug org-open-at-point zotero link

[Charles Millar]

Hi,

Current versions

Org mode version 9.3.6 (release_9.3.6-472-g8e3b73 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 28.0.50 (build 91, x86_64-pc-linux-gnu, GTK+ Version 3.24.14, 
cairo version 1.16.0) of 2020-04-10


From reading the documentation zotero is a valid link type and I would 
expect that org-open-at-point, C-c C-o, would open the following link


[[zotero://select/items/1_XPZL74VM][Behr, Michael. “A Research Workflow 
with Zotero and Org Mode.” mkbehr.com, September 19, 2015. 
http://www.mkbehr.com/posts/a-research-workflow-with-zotero-and-org-mode/.]]


Instead I receive the following error

request-default-error-callback: http://127.0.0.1:23119/zotxt/select error

I saved the link in Zotero with a snapshot.

I can open the link using org-zotxt-open-attachement.

If, however I save the link without a snapshot,

[[zotero://select/items/1_3AH6WNKZ][“A Research Workflow with Zotero and 
Org Mode | Mkbehr.Com.” Accessed April 10, 2020. 
http://www.mkbehr.com/posts/a-research-workflow-with-zotero-and-org-mode/.]]


and try org-zotxt-open-attachment I receive the following error

No attachments for item!
deferred error : (error "No attachments for item!")

If I org-open-at-point for the same link I receive

request-default-error-callback: http://127.0.0.1:23119/zotxt/select error

In the first instance is this a bug? Or is there a setting that I have 
to add to my localhost?


In the second case is this a org-zotxt or Zotero issue?

Charlie Millar

Re: Problem

[Charles Millar]

On 4/6/20 8:33 AM, Nicolas Goaziou wrote:

Hello,

Eric S Fraga  writes:


On Monday,  6 Apr 2020 at 07:49, Charles Millar wrote:

Just ran the same file with the following versions

Org mode version 9.3.6 (release_9.3.6-449-gb99357 @
/usr/local/share/org-mode/lisp/)
GNU Emacs 28.0.50 (build 87, x86_64-pc-linux-gnu, GTK+ Version
3.24.14, cairo version 1.16.0) of 2020-04-06


okay, one less variable.

have you tried this with "emacs -Q" in case there's something in your
configuration?


This happens because `org-latex-hyperref-template' is empty, which is
a valid use-case. I fixed it in both maint and master.  Thanks to you
two for the report and the debugging help.

Regards,


Downloaded and installed

Org mode version 9.3.6 (release_9.3.6-454-g3c87b8 @ 
/usr/local/share/org-mode/lisp/)


and I confirm that I have now produce the letter to Juliet using 
ox-koma-letter. BTW, it matches the Worg example-pdf.


Thank you Eric and everyone else, who have guided me.

Charlie Millar

Re: Problem

[Charles Millar]

On 4/6/20 4:37 AM, Eric S Fraga wrote:

On Saturday,  4 Apr 2020 at 13:13, Charles Millar wrote:

OK, started over.

Please see attached backtrace and the file I used.


Strange.  Your example file works just fine for me.

What version of org are you using?  And LaTeX?


Just ran the same file with the following versions

Org mode version 9.3.6 (release_9.3.6-449-gb99357 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 28.0.50 (build 87, x86_64-pc-linux-gnu, GTK+ Version 3.24.14, 
cairo version 1.16.0) of 2020-04-06


attached is the backtrace.



Can you export to LaTeX (C-c C-e k l) and see if that LaTeX file
compiles manually?
no Latex file produced.
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
  format-spec(nil ((116 . #("Mis-shapen chaos of well-seeming forms!" 0 39 
(:parent (#("Mis-shapen chaos of well-seeming forms!" 0 39 (:parent #7)) 
(97 . #("Romeo" 0 5 (:parent (#("Romeo" 0 5 (:parent #8)) (116 . 
#("Mis-shapen chaos of well-seeming forms!" 0 39 (:parent (#("Mis-shapen chaos 
of well-seeming forms!" 0 39 (:parent #9)) (115 . "") (107 . "") (100 . "") 
(99 . "Emacs 28.0.50 (Org mode 9.3.6)") (108 . "english") (76 . "English") (68 
#("1580" 0 4 (:parent #13)
  (concat (if (and with-subject (not (eq with-subject t))) (progn (format 
"\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject 
(mapconcat #'symbol-name with-subject ",") (format-spec hyperref-template 
spec) "\\begin{document}\n\n" (if subject (progn (format 
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format 
"\\setkomavar{title}{%s}\n" title))) (if (or (org-string-nw-p title) 
(org-string-nw-p subject)) (progn "\n")))
  (let* ((with-subject (plist-get info :with-subject)) (with-title (plist-get 
info :with-title)) (title-as-subject (and with-subject (plist-get info 
:with-title-as-subject))) (subject* (org-string-nw-p (org-export-data 
(plist-get info :subject) info))) (title* (and with-title (org-string-nw-p 
(org-export-data (plist-get info :title) info (subject (cond ((not 
with-subject) nil) (title-as-subject (or subject* title*)) (t subject*))) 
(title (cond ((not with-title) nil) (title-as-subject (and subject* title*)) (t 
title*))) (hyperref-template (plist-get info :latex-hyperref-template)) (spec 
(append (list (cons 116 (or title subject ""))) (org-latex--format-spec 
info (concat (if (and with-subject (not (eq with-subject t))) (progn 
(format "\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject 
(mapconcat #'symbol-name with-subject ",") (format-spec hyperref-template 
spec) "\\begin{document}\n\n" (if subject (progn (format 
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format 
"\\setkomavar{title}{%s}\n" title))) (if (or (org-string-nw-p title) 
(org-string-nw-p subject)) (progn "\n"
  (concat (and (plist-get info :time-stamp-file) (format-time-string "%% 
Created %Y-%m-%d %a %H:%M\n")) (org-latex--insert-compiler info) 
(org-latex-make-preamble info) (org-koma-letter--build-settings 'global info) 
(mapconcat #'(lambda (file) (format "\\LoadLetterOption{%s}\n" file)) 
(split-string (or (plist-get info :lco) "")) "") 
(org-koma-letter--build-settings 'buffer info) (format "\\date{%s}\n" 
(org-export-data (org-export-get-date info) info)) (let* ((with-subject 
(plist-get info :with-subject)) (with-title (plist-get info :with-title)) 
(title-as-subject (and with-subject (plist-get info :with-title-as-subject))) 
(subject* (org-string-nw-p (org-export-data (plist-get info :subject) info))) 
(title* (and with-title (org-string-nw-p (org-export-data (plist-get info 
:title) info (subject (cond ((not with-subject) nil) (title-as-subject (or 
subject* title*)) (t subject*))) (title (cond ((not with-title) nil) 
(title-as-subject (and subject* title*)) (t title*))) (hyperref-template 
(plist-get info :latex-hyperref-template)) (spec (append (list (cons 116 (or 
title subject ""))) (org-latex--format-spec info (concat (if (and 
with-subject (not (eq with-subject t))) (progn (format 
"\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject 
(mapconcat ... with-subject ",") (format-spec hyperref-template spec) 
"\\begin{document}\n\n" (if subject (progn (format 
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format 
"\\setkomavar{title}{%s}\n" title))) (if (or (org-string-nw-p title) 
(org-string-nw-p subject)) (progn "\n" (let ((keyword-val (plist-get info 
:to-address)) (heading-val (org-koma-letter--get-tagged-contents 'to))) (format 
"\\begin{letter}{%%\n%s}\n\n" (org-koma-letter--add-

Re: Problem

[Charles Millar]

On 4/4/20 7:30 AM, Eric S Fraga wrote:

On Friday,  3 Apr 2020 at 16:49, Charles Millar wrote:

org-latex-classes includes

"default-koma-letter" "\\documentclass[11pt]{scrlttr2}"

There are no other entries that include scrlttr2 in org-latex-classes

I have a barebones header

#+LATEX_CLASS: scrlttr2 (I also have tried 'default-koma-letter')


It should be default-koma-letter here.

To figure out what is wrong, you may wish to export to LaTeX first and
then have a look at what has been generated.

In any case, to use the letter style, I have the following in my org
customization:

   (require 'ox-koma-letter)

and then use the "k" option for the exporter (C-c C-e k) to export as a
letter.



OK, started over.

Please see attached backtrace and the file I used.

Also, in my init file I commented out my customized latex classes, just 
in case. See attached latex-classes file for the org-latex-classes.
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
  format-spec(nil ((116 . #("Mis-shapen chaos of well-seeming forms!" 0 39 
(:parent (#("Mis-shapen chaos of well-seeming forms!" 0 39 (:parent #7)) 
(97 . #("Romeo" 0 5 (:parent (#("Romeo" 0 5 (:parent #8)) (116 . 
#("Mis-shapen chaos of well-seeming forms!" 0 39 (:parent (#("Mis-shapen chaos 
of well-seeming forms!" 0 39 (:parent #9)) (115 . "") (107 . "") (100 . "") 
(99 . "Emacs 28.0.50 (Org mode 9.3.6)") (108 . "english") (76 . "English") (68 
#("1580" 0 4 (:parent #13)
  (concat (if (and with-subject (not (eq with-subject t))) (progn (format 
"\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject 
(mapconcat #'symbol-name with-subject ",") (format-spec hyperref-template 
spec) "\\begin{document}\n\n" (if subject (progn (format 
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format 
"\\setkomavar{title}{%s}\n" title))) (if (or (org-string-nw-p title) 
(org-string-nw-p subject)) (progn "\n")))
  (let* ((with-subject (plist-get info :with-subject)) (with-title (plist-get 
info :with-title)) (title-as-subject (and with-subject (plist-get info 
:with-title-as-subject))) (subject* (org-string-nw-p (org-export-data 
(plist-get info :subject) info))) (title* (and with-title (org-string-nw-p 
(org-export-data (plist-get info :title) info (subject (cond ((not 
with-subject) nil) (title-as-subject (or subject* title*)) (t subject*))) 
(title (cond ((not with-title) nil) (title-as-subject (and subject* title*)) (t 
title*))) (hyperref-template (plist-get info :latex-hyperref-template)) (spec 
(append (list (cons 116 (or title subject ""))) (org-latex--format-spec 
info (concat (if (and with-subject (not (eq with-subject t))) (progn 
(format "\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject 
(mapconcat #'symbol-name with-subject ",") (format-spec hyperref-template 
spec) "\\begin{document}\n\n" (if subject (progn (format 
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format 
"\\setkomavar{title}{%s}\n" title))) (if (or (org-string-nw-p title) 
(org-string-nw-p subject)) (progn "\n"
  (concat (and (plist-get info :time-stamp-file) (format-time-string "%% 
Created %Y-%m-%d %a %H:%M\n")) (org-latex--insert-compiler info) 
(org-latex-make-preamble info) (org-koma-letter--build-settings 'global info) 
(mapconcat #'(lambda (file) (format "\\LoadLetterOption{%s}\n" file)) 
(split-string (or (plist-get info :lco) "")) "") 
(org-koma-letter--build-settings 'buffer info) (format "\\date{%s}\n" 
(org-export-data (org-export-get-date info) info)) (let* ((with-subject 
(plist-get info :with-subject)) (with-title (plist-get info :with-title)) 
(title-as-subject (and with-subject (plist-get info :with-title-as-subject))) 
(subject* (org-string-nw-p (org-export-data (plist-get info :subject) info))) 
(title* (and with-title (org-string-nw-p (org-export-data (plist-get info 
:title) info (subject (cond ((not with-subject) nil) (title-as-subject (or 
subject* title*)) (t subject*))) (title (cond ((not with-title) nil) 
(title-as-subject (and subject* title*)) (t title*))) (hyperref-template 
(plist-get info :latex-hyperref-template)) (spec (append (list (cons 116 (or 
title subject ""))) (org-latex--format-spec info (concat (if (and 
with-subject (not (eq with-subject t))) (progn (format 
"\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject 
(mapconcat ... with-subject ",") (format-spec hyperref-template spec) 
"\\begin{document}\n\n" (if subject (progn (format 
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format 
"\\setkomavar

Re: Problem

[Charles Millar]

On 4/4/20 7:34 AM, Eric S Fraga wrote:

On Saturday,  4 Apr 2020 at 09:43, Robert Klein wrote:


Thank you for your suggestions, Eric.


I use ox-koma-letter, and have nothing concerning koma n
org-latex-classes:

- #+LaTeX_CLASS: scrlttr2


I am surprised that this works.  ox-koma-letter does the following:

#+begin_src elisp
(unless (assoc "default-koma-letter" org-latex-classes)
   (add-to-list 'org-latex-classes
'("default-koma-letter" "\\documentclass[11pt]{scrlttr2}")))
#+end_src

and so you should be using default-koma-letter here.


I was alternating between scrlttr2 and default-koma-letter and the last 
time I put in the extra "t". I have corrected it and still receive the 
unknon latex class message.


Unless, of course, you have defined your own scrlttr2 org LaTeX class
somewhere (although you say you have not)?


Not that sophisticated - yet.

Re: Problem

[Charles Millar]

On 4/4/20 3:43 AM, Robert Klein wrote:

Hi,


Thank you for replying, Robert,


I use ox-koma-letter, and have nothing concerning koma n
org-latex-classes:

- ensure ox-koma-letter is installed
- to install it, add to your local.mk:
   #+begin_src text
 ORG_ADD_CONTRIB = ox-koma-letter
   #+end_src

- (require 'ox-koma-letter) in your .emacs


I had already added to my init file  (require 'ox-koma-letter) and 
(add-to-list 'org-latex-packages-alist '("AUTO" "babel" t ("pdflatex"))) 
as instructed in the Worg tutorial.


- export using C-c C-e k p  (for pdf; l for LaTeX)


Actually I tried all four koma-letter export options and had the same 
result.




- #+LaTeX_CLASS: scrlttr2

(two t's, not three)


I was alternating between scrlttr2 and default-koma-letter and the last 
time I put in the extra "t". I have corrected it and still receive the 
unknon latex class message. As mentioned in my earlier email I confirmed 
that my org-latex-classes includes  ("default-koma-letter" 
"\\documentclass[11pt]{scrlttr2}")


I also added (add-to-list 'org-latex-packages-alist '("AUTO" "babel" t 
("pdflatex"))) to my init file.



Best regards
Robert

On Fri, 3 Apr 2020 16:49:15 -0400
Charles Millar  wrote:


I am attempting to use ox-koma-letter, etc.

My set up

GNU Emacs 28.0.50 (build 84, x86_64-pc-linux-gnu, GTK+ Version
3.24.14, cairo version 1.16.0) of 2020-04-03
Org mode version 9.3.6 (release_9.3.6-449-gb99357 @
/usr/local/share/org-mode/lisp/)

org-latex-classes includes

"default-koma-letter" "\\documentclass[11pt]{scrlttr2}"

There are no other entries that include scrlttr2 in org-latex-classes

I have a barebones header

#+LATEX_CLASS: scrlttr2 (I also have tried 'default-koma-letter')

and then entered the Romeo to Juliet letter

and i receive the following error

Unknown LaTex class scrlttr2

I searched the list and one suggested problem does not seem to be
applicable - I do not have a mixed org installation.

Any suggestions.

Charlie Millar

Re: Problem with LaTeX class scrlttr2

[Charles Millar]

On 4/4/20 2:22 AM, Julius Dittmar wrote:

How do you produce (or try to produce) LaTeX/pdf?

The Unknown LaTeX class message is something emacs throws when using 
export to latex (C-c C-e l l). This has nothing to do with your LaTeX 
installation; it does not reach the point of invoking LaTeX. It tells 
you there's no setup for scrlttr2 class in org-latex-classes. There is 
no setup for default-koma-letter either in my version of 
org-latex-classes. Perhaps you need to load ox-koma-letter in org first?



Thanks for replying, Julius.


When I was setting up I added to my init file  (require 'ox-koma-letter) 
and (add-to-list 'org-latex-packages-alist '("AUTO" "babel" t 
("pdflatex"))) as instructed in the Worg tutorial.

Re: Problem with LaTeX class scrlttr2

[Charles Millar]

On 4/3/20 10:30 PM, John Hendy wrote:

Thanks! Saves a lot of time to recreate an example.

I get the same error, but wouldn't you know I'm on TexLive 2019 which
must have just hit end of life... tlmgr says it's frozen and won't let
me try and add new packages. I do want to help but am not going to
update to 2020 for this :)

One thing popped out to me...

#+LATEX_CLASS: scrltttr2

Is that a typo (ttt, not tt)? If someone doesn't get to this before
me, I'll try again after I update TL 2020 over the weekend.


Probably the third or fourth time I entered a LATEX_CLASS, and the last 
time if was a typo. I corrected it to make sure and still have the same 
result.


Also, I had already added to my init file  (require 'ox-koma-letter) and 
(add-to-list 'org-latex-packages-alist '("AUTO" "babel" t ("pdflatex"))) 
as instructed in the Worg tutorial.


On Fri, Apr 3, 2020 at 8:26 PM Charles Millar  wrote:


On 4/3/20 7:19 PM, John Hendy wrote:

Please attach an actual .org file so we can test/reproduce.



See attached

Generally "unknown latex class" means you don't have the package
installed. How about posting the output of this:

$ tlmgr list --only-installed | grep scrlttr2


  >
No output; however I have TeXlive package, Debian testing, installed. I
found an example that uses scrlttr2 at

https://tex.stackexchange.com/questions/229032/how-to-add-company-name-to-return-back-address-in-scrlttr2#229037

and ran it using TexStudio - no problem, i.e. resulted with a letter. So
I expect that scrlttr2 is installed as part of the TexLive komascript.


On Fri, Apr 3, 2020 at 4:06 PM Charles Millar  wrote:


I apologize for reposting - I forgot to complete my


 Forwarded Message 
Subject: Problem
Date: Fri, 3 Apr 2020 16:49:15 -0400
From: Charles Millar 
To: emacs-orgmode@gnu.org 

I am attempting to use ox-koma-letter, etc.

My set up

GNU Emacs 28.0.50 (build 84, x86_64-pc-linux-gnu, GTK+ Version 3.24.14,
cairo version 1.16.0) of 2020-04-03
Org mode version 9.3.6 (release_9.3.6-449-gb99357 @
/usr/local/share/org-mode/lisp/)

org-latex-classes includes

"default-koma-letter" "\\documentclass[11pt]{scrlttr2}"

There are no other entries that include scrlttr2 in org-latex-classes

I have a barebones header

#+LATEX_CLASS: scrlttr2 (I also have tried 'default-koma-letter')

and then entered the Romeo to Juliet letter

and i receive the following error

Unknown LaTex class scrlttr2

I searched the list and one suggested problem does not seem to be
applicable - I do not have a mixed org installation.

Any suggestions.

Charlie Millar

Re: Problem with LaTeX class scrlttr2

[Charles Millar]

On 4/3/20 7:19 PM, John Hendy wrote:

Please attach an actual .org file so we can test/reproduce.



See attached

Generally "unknown latex class" means you don't have the package
installed. How about posting the output of this:

$ tlmgr list --only-installed | grep scrlttr2


>
No output; however I have TeXlive package, Debian testing, installed. I
found an example that uses scrlttr2 at

https://tex.stackexchange.com/questions/229032/how-to-add-company-name-to-return-back-address-in-scrlttr2#229037

and ran it using TexStudio - no problem, i.e. resulted with a letter. So
I expect that scrlttr2 is installed as part of the TexLive komascript.


On Fri, Apr 3, 2020 at 4:06 PM Charles Millar  wrote:


I apologize for reposting - I forgot to complete my


 Forwarded Message 
Subject: Problem
Date: Fri, 3 Apr 2020 16:49:15 -0400
From: Charles Millar 
To: emacs-orgmode@gnu.org 

I am attempting to use ox-koma-letter, etc.

My set up

GNU Emacs 28.0.50 (build 84, x86_64-pc-linux-gnu, GTK+ Version 3.24.14,
cairo version 1.16.0) of 2020-04-03
Org mode version 9.3.6 (release_9.3.6-449-gb99357 @
/usr/local/share/org-mode/lisp/)

org-latex-classes includes

"default-koma-letter" "\\documentclass[11pt]{scrlttr2}"

There are no other entries that include scrlttr2 in org-latex-classes

I have a barebones header

#+LATEX_CLASS: scrlttr2 (I also have tried 'default-koma-letter')

and then entered the Romeo to Juliet letter

and i receive the following error

Unknown LaTex class scrlttr2

I searched the list and one suggested problem does not seem to be
applicable - I do not have a mixed org installation.

Any suggestions.

Charlie Millar






#+LATEX_CLASS: scrltttr2

* Preamble :noexport:
#+TITLE:  Mis-shapen chaos of well-seeming forms!
#+SUBJECT: Or: org-mode and KOMA-Script letters
#+DATE: 1580

#+AUTHOR: Romeo
#+PLACE: Verona, Italy

#+LCO: DINmtext
# NOTE: Check the KOMA-Script manual to find a LCO that fits the
#   envelope standards of your country.

# NOTE: Change the order of the backletter, use smart quotes and
#   include backaddress
#+OPTIONS: after-closing-order:(my_after_signature ps cc encl)
#+options: ':t backaddress:t subject:centered

# Remove the first header
#+LATEX_HEADER: \setkomavar{firsthead}{}

* To-address of the lovely Juliet:to:
# NOTE: Explicit newlines are not necessary in TO and FROM
Juliet
House of Capulet
Verona

* From :from:
House of Montague
Verona
* Location :location:
#+LATEX_HEADER: \usepackage{tikz}
#+BEGIN_CENTER
*Montague*
#+BEGIN_EXPORT latex
\tikz \draw (0,0) --+ (0,-1)
   arc [radius=1, start angle=-180, end angle=0]
   --+ (0,1) -- cycle
   node [below=1.5em,midway] {\bfseries M};
#+END_EXPORT
#+END_CENTER

* Dear Juliet,
# NOTE: Your letter is the first non-special heading.  The title of
# this heading may used as an opening.

#+BEGIN_VERSE
Then plainly know my heart's dear love is set
On the fair daughter of rich Capulet:
As mine on hers, so hers is set on mine;
And all combin'd, save what thou must combine
By holy marriage: when, and where, and how
We met, we woo'd, and made exchange of vow,
I'll tell thee as we pass; but this I pray,
That thou consent to marry us to-day.
#+END_VERSE

* Yours truly,  :closing:
Romeo of House Montague
* some arbitrary LaTeX code  :my_after_signature:
#+BEGIN_EXPORT latex
% this special heading was added dynamically.
#+END_EXPORT
* PS :ps:
PS: "PS" is not typeset automatically by KOMA-Script

@@latex:\noindent@@ PPS: This is a feature!
* CC :cc:
Paris and Lawrence.
* ENCL :encl:
See also [[https://en.wikisource.org/wiki/The_Tragedy_of_Romeo_and_Juliet][The 
Tragedy of Romeo and Juliet]]
* some more arbitrary LaTeX code   :after_letter:
#+BEGIN_EXPORT latex
% here we can place random LaTeX code, e.g. including PDFs via the pdfpages 
package.
#+END_EXPORT

Problem with LaTeX class scrlttr2

[Charles Millar]

I apologize for reposting - I forgot to complete my


 Forwarded Message 
Subject: Problem
Date: Fri, 3 Apr 2020 16:49:15 -0400
From: Charles Millar 
To: emacs-orgmode@gnu.org 

I am attempting to use ox-koma-letter, etc.

My set up

GNU Emacs 28.0.50 (build 84, x86_64-pc-linux-gnu, GTK+ Version 3.24.14, 
cairo version 1.16.0) of 2020-04-03
Org mode version 9.3.6 (release_9.3.6-449-gb99357 @ 
/usr/local/share/org-mode/lisp/)


org-latex-classes includes

"default-koma-letter" "\\documentclass[11pt]{scrlttr2}"

There are no other entries that include scrlttr2 in org-latex-classes

I have a barebones header

#+LATEX_CLASS: scrlttr2 (I also have tried 'default-koma-letter')

and then entered the Romeo to Juliet letter

and i receive the following error

Unknown LaTex class scrlttr2

I searched the list and one suggested problem does not seem to be 
applicable - I do not have a mixed org installation.


Any suggestions.

Charlie Millar

Problem

[Charles Millar]

I am attempting to use ox-koma-letter, etc.

My set up

GNU Emacs 28.0.50 (build 84, x86_64-pc-linux-gnu, GTK+ Version 3.24.14, 
cairo version 1.16.0) of 2020-04-03
Org mode version 9.3.6 (release_9.3.6-449-gb99357 @ 
/usr/local/share/org-mode/lisp/)


org-latex-classes includes

"default-koma-letter" "\\documentclass[11pt]{scrlttr2}"

There are no other entries that include scrlttr2 in org-latex-classes

I have a barebones header

#+LATEX_CLASS: scrlttr2 (I also have tried 'default-koma-letter')

and then entered the Romeo to Juliet letter

and i receive the following error

Unknown LaTex class scrlttr2

I searched the list and one suggested problem does not seem to be 
applicable - I do not have a mixed org installation.


Any suggestions.

Charlie Millar

Re: bug: org-table-convert-region-max-lines causes a "Code block produced nop output"

[Charles Millar]

On 2/5/20 3:11 AM, Bastien wrote:

Hi Charles,

Charles Millar via Emacs-orgmode  writes:


In an org file I have a source code block to convert entries into and
generate a recutils file

#+begin_src sh?? :file SomeFile.rec
cat << EOF
# -*- mode: rec -*-

 Begin recutils file

Approximately 770 records in recutils format each with about 20 entries;
over 17,000 lines including line feeds or carriage returns

#+end_src

The following error is produced:

Starting new Ispell process /usr/bin/aspell with en_US dictionary...
executing Sh code block...
Wrote /tmp/babel-k8j93s/ob-input-LL2cYo
Error reading results: (user-error Region is longer than
???org-table-convert-region-max-lines??? (999) lines; not converting)
Code block produced no output.


This bug is quite old -- before I try to digg in, can you confirm it
is still present with latest Org version from the maint branch?

Thanks!



I have not experienced this problem since I reported it.

As I recall at a later date you pointed out that I should have inserted
the header :results file.

Thanks

Charlie Millar

#+INCLUDE causes error when it attmepts to expand a LaTeX macro in source block

[Charles Millar]

Greetings,

In my init file I have

(setq org-confirm-babel-evaluate nil)

File "A" is attached as an org file. I evaluate the source blocks (C-c 
C-v s), the table is generated and then I export it to PDF. The source 
blocks do not evaluate during export.


In file B I have

#+INCLUDE: "/path/to/FileA::*SCHEDULE A1112"

When I attempt to export File B to PDF/LaTeX the following error occurs

Debugger entered--Lisp error: (error "Undefined Org macro: cmhfill; 
aborting")

  signal(error ("Undefined Org macro: cmhfill; aborting"))
  error("Undefined Org macro: %s; aborting" "cmhfill")

If I place a "#+HEADER: :eval no" in the source blocks in File A (after 
generating the table) File B will export the table to PDF. Also, please 
note that the cmhfill macro is in the table headings.


Is this an error, i.e. the #+INCLUDE does not honor the setting in my 
init file?


Is there a header or property setting for File B to prevent the exporter 
from evaluating the source blocks when executing through an #+INCLUDE, 
more particularly to prevent the attempted macro expansion within the 
source blocks?


Both File A and File B had identical LaTeX settings, i.e. the macro was 
defined in both files.


GNU Emacs 27.0.50 (build 8, x86_64-pc-linux-gnu, GTK+ Version 3.24.13) 
of 2019-12-07


Org mode version 9.3 (release_9.3-36-gbe7434 @ 
/usr/local/share/org-mode/lisp/)


Charlie Millar
* SCHEDULE A1112
#+NAME: SCHEDAP
#+begin_src rec :data somefile.rec :type Finance :fields 
AccountDate,Shares,Description,AccountAmount :sort AccountDate,Description 
:results silent
 (File = 'Estate' && AccountSchedule = 'A')
#+end_src
#+RESULTS: SCHEDAP
#+NAME: SCHEDA
#+begin_src emacs-lisp :var table=SCHEDAP :exports results
  (setq table (cons 'hline table))
  (setq table (cons '("Date" "{{{cmhfill}}} Shares" " Description " 
"{{{cmhfill}}} Inventory{{{cm1space}}}Value") table))
  (setq table (append table '(("| |Total Schedule A"
  (setq table (append table '(("\n#+TBLFM: @>$>=vsum(@I$>..@>>$>);%.2f::"
  table
#+end_src
#+ATTR_LATEX: :mode table :environment longtable :align  
p{60pt}N{5}{3}p{275pt}N{8}{2}
#+RESULTS: SCHEDA
| Date   | {{{cmhfill}}} Shares | Description  | {{{cmhfill}}} 
Inventory{{{cm1space}}}Value |
|+--+--+|
| 2018-03-18 |  | Something|
   49645.59 |
| etc|  | etc  |
4878.51 |
||  | Total Schedule A |
   54524.10 |
#+TBLFM: @>$>=vsum(@I$>..@>>$>);%.2f:: |

[O] add names to org-babel-header-arg-names

[Charles Millar via Emacs-orgmode]

Hi,

To avoid errors while running org-lint in an org file with many recutils
source blocks I have added the following to my init.el file

(setq recutils-babel-header-arg-names '(data type fields join sort groupby))
  ;; cmdline already included in org-babel-header-arg-names so not part 
of above list
(setq org-babel-header-arg-names (concatenate 'list 
org-babel-header-arg-names recutils-babel-header-arg-names))


It appears that there are no problems, Never the less,

Is there a "better" way? For that matter, is there a safer way?

Charlie Millar

Re: [O] Bug header argumednt :file does not produce a file or a link to the file

[Charles Millar via Emacs-orgmode]

Nicolas Goaziou  writes:



It changed between Org 9.2 and Org 9.3, for every language. There is an
ORG-NEWS entry about it, namely:

  *** ~:file~ header argument no longer assume "file" ~:results~



Thank you. I read that entry and others concerning ;file prior to
posting and it did not penetrate my thick skull.

Regards,

Re: [O] Bug header argumednt :file does not produce a file or a link to the file

[Charles Millar via Emacs-orgmode]

On 8/23/19 4:15 AM, Nicolas Goaziou wrote:

Hello,

Charles Millar via Emacs-orgmode  writes:


#+begin_src sh :file test.rec
cat << EOF
# -*- mode: rec -*-

%rec: somerecord

Account: something
Amount: 0.00

 end of file
EOF

#+end_src

I expect that when I execute the above code block that

1. An external file test.rec is produced with contents

# -*- mode: rec -*-

%rec: somerecord

Account: something
Amount: 0.00

 end of file

   and

2. A link to that file is placed below the source code block

Instead all I get is a table and no external file is created


You probably need to specify that the output is a file, which is not the
default for "sh" language. You may want to add ":results file" to the
header of the source block.

Regards,


Thank you, Nicolas. That solved it.

Now a "just curious," comment and question:

I had a few files that used the ECM source code block, just many more 
entries in each. The last time that I evaluated any of them was last 
October and it produced the results I expected, i.e. I did not specify 
":results file"


So, up until October was I just lucky or did something change in Org 
that affected the sh language?


Regards,

Charlie Millar

[O] Bug header argumednt :file does not produce a file or a link to the file

[Charles Millar via Emacs-orgmode]

Org mode version 9.2.5 (release_9.2.5-494-g4848b8 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 59, x86_64-pc-linux-gnu, GTK+ Version 3.24.10) 
of 2019-08-22


ECM

#+begin_src sh :file test.rec
cat << EOF
# -*- mode: rec -*-

%rec: somerecord

Account: something
Amount: 0.00

 end of file
EOF

#+end_src

I expect that when I execute the above code block that

1. An external file test.rec is produced with contents

# -*- mode: rec -*-

%rec: somerecord

Account: something
Amount: 0.00

 end of file

 and

2. A link to that file is placed below the source code block

Instead all I get is a table and no external file is created

#+RESULTS:
| # |   -*- | mode: | rec | -*- |
| %rec: | somerecord | | | |
| Account: | sometyhing | | | |
| Amount: | 0.0 | | | |
|  | end | of | file | |

I reported this earlier but my subject line was not correct.

Charlie Millar

Re: [O] bug: org-table-convert-region-max-lines causes a "Code block produced nop output"

[Charles Millar via Emacs-orgmode]

A follow up

On 8/20/19 9:32 AM, Charles Millar via Emacs-orgmode wrote:
In an org file I have a source code block to convert entries into and 
generate a recutils file


#+begin_src sh?? :file SomeFile.rec
cat << EOF
# -*- mode: rec -*-

 Begin recutils file

Approximately 770 records in recutils format each with about 20 
entries; over 17,000 lines including line feeds or carriage returns


#+end_src

The following error is produced:

Starting new Ispell process /usr/bin/aspell with en_US dictionary...
executing Sh code block...
Wrote /tmp/babel-k8j93s/ob-input-LL2cYo
Error reading results: (user-error Region is longer than 
???org-table-convert-region-max-lines??? (999) lines; not converting)

Code block produced no output.

I admit that I have not evaluated this code block since last 
October.At that time the SomeFile.rec file was produced, as expected. 
However, the size of the entries has not changed and now the above 
error results.


I modified my init.el file to include

(setq org-table-convert-region-max-lines 2)

closed emacs, etc. (load-file init.el did not change the default 999 
to 2)


When I C-c C-c'ed the code block again the process hung. I confirmed 
that org-table-convert-region-max-lines was set to 2.


Is org-table-convert-region-max-lines?? supposed to be invoked and if 
so what should I modify?


Version information

Org mode version 9.2.5 (release_9.2.5-488-g9ddba9 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 57, x86_64-pc-linux-gnu, GTK+ Version 
3.24.10) of 2019-08-20


Charlie Millar

It appears that the above now creates a table, not a recutils file. 
Spaces are the delimiter,



#+begin_src sh?? :file test.rec
cat << EOF
# -*- mode: rec -*-

%rec: somerecord

Account: something
Amount: 0.00

 end of file
EOF

#+end_src

#+RESULTS:
| #?? | -*-?? | mode: | rec?? | -*- |
| %rec:?? | somerecord | |?? | |
| Account: | sometyhing | |?? | |
| Amount:?? | 0.0?? | |?? | |
|  | end?? | of?? | file | |

[O] bug: org-table-convert-region-max-lines causes a "Code block produced nop output"

[Charles Millar via Emacs-orgmode]

In an org file I have a source code block to convert entries into and 
generate a recutils file


#+begin_src sh?? :file SomeFile.rec
cat << EOF
# -*- mode: rec -*-

 Begin recutils file

Approximately 770 records in recutils format each with about 20 entries; 
over 17,000 lines including line feeds or carriage returns


#+end_src

The following error is produced:

Starting new Ispell process /usr/bin/aspell with en_US dictionary...
executing Sh code block...
Wrote /tmp/babel-k8j93s/ob-input-LL2cYo
Error reading results: (user-error Region is longer than 
???org-table-convert-region-max-lines??? (999) lines; not converting)

Code block produced no output.

I admit that I have not evaluated this code block since last October.At 
that time the SomeFile.rec file was produced, as expected. However, the 
size of the entries has not changed and now the above error results.


I modified my init.el file to include

(setq org-table-convert-region-max-lines 2)

closed emacs, etc. (load-file init.el did not change the default 999 to 
2)


When I C-c C-c'ed the code block again the process hung. I confirmed 
that org-table-convert-region-max-lines was set to 2.


Is org-table-convert-region-max-lines?? supposed to be invoked and if so 
what should I modify?


Version information

Org mode version 9.2.5 (release_9.2.5-488-g9ddba9 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 57, x86_64-pc-linux-gnu, GTK+ Version 3.24.10) 
of 2019-08-20


Charlie Millar

[O] set :var to string inline code

[Charles Millar]

Hi,

I have recutils data base and from that I want to use inline source code 
to generate a list of names, addresses, etc. for instance the following 
inline code when exported in latex



src_sh[:results raw :results replace :exports results :eval yes]{recsel 
-t InterestedParties -e "IPName='Charles Millar'" -P IPPrintName Millar.rec}
src_sh[:results raw :results replace :exports results :eval yes]{recsel 
-t InterestedParties -e "IPName='Charles Millar'" -P IPAddress1 Millar.rec}
src_sh[:results raw :results replace :exports results :eval yes]{recsel 
-t InterestedParties -e "IPName='Charles Millar'" -P IPPAddress2 Millar.rec}


will give

Charles Millar
123 XYZ Street
Apt 678

However, there are (as there should be) many records in the database and 
rather than set each and every IPName= to a specific field I want to use 
something like the following


#+name: iponeshell
#+begin_src sh :results raw :exports results
iponeassign="Charles Millar"
echo "$iponeassign"
#+end_src

#+RESULTS: iponeshell
Charles Millar

src_sh[:results raw :results replace :var IPOne='iponeshell' :eval 
yes]{recsel -t InterestedParties -e "IPName=IPOne" -P IPPrintName 
Millar.rec}
src_sh[:results raw :results replace :var IPOne='iponeshell' :eval 
yes]{recsel -t InterestedParties -e "IPName=IPOne" -P IPAddress1 
Millar.rec}
src_sh[:results raw :results replace :var IPOne='iponeshell' :eval 
yes]{recsel -t InterestedParties -e "IPName=IPOne" -P IPAddress2 
Millar.rec}


The above example evaluates, but there is no output. I have tried 
:exports results as well as diggernet variations of dounle and sing 
quotes, at both where I define var and at the expression selection 
within recsel.


I believe that this is bash issue so I have also tries to use $ with the 
:var and recsel selection expression.


Any help would be gretly appreciated.

Charlie Millar


src_sh[:results raw :results replace :var IPOne=iponeshell :exports 
results :eval yes]{recsel -t InterestedParties -e "IPName='Charles 
Millar'" -P IPPrintName StreichertCatherine.rec}


I am

[O] Bug - #+begin_comment, etc surrounding minipage

[Charles Millar]

Hi,

When exporting to pdf via LaTeX, the region between the #+begin_comment 
and the #+end_comment does not comment out:


*** sub,sub-heading one
#+attr_latex: :options  [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage

#+begin_comment

*** sub,sub-heading two
#+attr_latex: :options  [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage

*** sub,sub-heading three
#+attr_latex: :options  [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage*** sub,sub-heading one
#+attr_latex: :options  [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage

#+end_comment

Instead the #+begin_comment and #+end_comment lines are printed out 
(sort of weirdly) and everything in between as well.


If I surround the region with a \begin{comment} and \end{comment} - all 
is well.


Org mode version 9.1.13 (release_9.1.13-901-g638f32 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 48, x86_64-pc-linux-gnu, GTK+ Version 3.22.29) 
of 2018-06-29


Charlie Millar

Re: [O] [bug] refiling puts random stuff in kill ring

[Charles Millar]

On 08/03/2018 08:21 PM, Samuel Wales wrote:

recent maint.

i kill with c-m-k, then move point, then refile an entry.  then i
yank.  that produces something that was earlier killed.

i expected what i killed.
I noticed this behavior two or three days ago (best as I remember), 
using M-w and C-w then C-y. I thought I was at fault, i.e. not hitting 
the correct keys. Also, it does not seem to occur consistently.


Org mode version 9.1.13 (release_9.1.13-895-gf79545 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 48, x86_64-pc-linux-gnu, GTK+ Version 3.22.29) 
of 2018-06-29


Charlie Millar

Re: [O] Curious as to message in echo area

[Charles Millar]

On 06/18/2018 02:51 AM, Nick Dokos wrote:

Charles Millar  writes:


Hello,

I have always concerned myself that a table column formula returns what is 
expected.and is correct.

However I never paid attention to the echo area and I just noticed that it 
displays the following message

"cells in region copied, use M-x org-table-paste-rectangle to paste them in a 
table"
when I C-c C-c on the formula in the following table

| 1 |
| 2 |
| 3 |
|   |
#+tblfm: @>$>=vsum(@1..@>>)

The correct result is returned.

Have I been ignoring something for the past several years, i.e. has the above 
message always been displayed?


No, it was added recently:

,
| $ git blame -L 1868,1870 -- org-table.el
| 5c8cb1e733 (Bastien 2018-04-28 12:52:20 +0200 1868) (setq 
org-table-clip (nreverse region))
| 5c8cb1e733 (Bastien 2018-04-28 12:52:20 +0200 1869) (message 
(substitute-command-keys "Cells in the region copied, use 
\\[org-table-paste-rectangle] to paste them in a table."
| fe939ecb95 (Carsten Dominik 2008-03-22 16:52:18 +0100 1870)
| $ git show 5c8cb1e733
| commit 5c8cb1e7332a9fd8ba71cd0a5fe7bdf5d19d09fd
| Author: Bastien 
| Date:   Sat Apr 28 12:52:20 2018 +0200
|
| Add messages for `org-table-copy-region' and `org-copy-visible'
|
| * lisp/org-table.el (org-table-copy-region):
| * lisp/org.el (org-copy-visible): Add a message.


thank you.

[O] Curious as to message in echo area

[Charles Millar]

Hello,

I have always concerned myself that a table column formula returns what 
is expected.and is correct.


However I never paid attention to the echo area and I just noticed that 
it displays the following message


"cells in region copied, use M-x org-table-paste-rectangle to paste them 
in a table"


when I C-c C-c on the formula in the following table

| 1 |
| 2 |
| 3 |
|   |
#+tblfm: @>$>=vsum(@1..@>>)

The correct result is returned.

Have I been ignoring something for the past several years, i.e. has the 
above message always been displayed?


Just wondering.

Charlie Millar

Re: [O] Bug ignoreheading not respected in lower level headlines latex export

[Charles Millar]

Hello again,


On 06/07/2018 08:29 AM, Charles Millar wrote:


Hi,

Set up -

Org mode version 9.1.13 (release_9.1.13-791-gcecbe4 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 30, x86_64-pc-linux-gnu, GTK+ Version 
3.22.11) of 2018-06-02


I group related documents as second level headlines, thus

* All docs :ignoreheading:

** Doc 1 :ignoreheading:

** Doc 2 :ignoreheading:

The first level has an export_file_name property so that I can export 
all the docs at once; likewise each second level has its own 
export_file_name for separate export, if necessary.


When I export all the docs from the first level headline the resulting 
export is


1. Doc 1

content

 (newpage)

2. Doc 2

content

I expect

content

(newpage)

content.

If I export each doc from its second level, the headline is ignored.


Sorry for the noise. I few days earlier I added org-export-with-tags nil 
ti my .emacs; commented this out and the export works as expected.


Charlie Millar

[O] Bug ignoreheading not respected in lower level headlines latex export

[Charles Millar]

Hi,

Set up -

Org mode version 9.1.13 (release_9.1.13-791-gcecbe4 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 30, x86_64-pc-linux-gnu, GTK+ Version 3.22.11) 
of 2018-06-02


I group related documents as second level headlines, thus

* All docs :ignoreheading:

** Doc 1 :ignoreheading:

** Doc 2 :ignoreheading:

The first level has an export_file_name property so that I can export 
all the docs at once; likewise each second level has its own 
export_file_name for separate export, if necessary.


When I export all the docs from the first level headline the resulting 
export is


1. Doc 1

content

 (newpage)

2. Doc 2

content

I expect

content

(newpage)

content.

If I export each doc from its second level, the headline is ignored.

[O] Cannot access repository

[Charles Millar]

I cannot access

https://code.orgmode.org/bzg/org-mode.git

requested url returned error 502

Charlie Millar

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Charles Millar]

Hi all,


On 04/29/2018 07:05 AM, Bastien wrote:

Hi Nicolas,

Nicolas Goaziou  writes:

    Let's just take a moment to see what users think.

I was aware of tempo.el and tempo from postings to the list. However It 
was not until I upgraded to version 9.1.12 from 9.1.11 that I realized 
that tempo was the default; I thought that it was optional. With 9.1.12 
installed I could not open any of my org files because of the blocks 
that I added through the years to the org-structure-template-alist.


I used the previous feature merely to insert blocks, which were not 
necessarily for coding; the first block I added was obtained from Dan 
Doherty, on this list, about six years ago and it had nothing to do with 
coding but to insert a debit and credit columns into a document.


I will adapt if I must, but I suspect that there are other users such as 
I who merely used the feature to insert a block of text or something 
else other than code.


Charlie Millar

Re: [O] add blocks to org-structure-template-alist

[Charles Millar]

Hi Bastien,

On 04/28/2018 02:22 AM, Bastien wrote:

Hi Charles,

Charles Millar <mill...@verizon.net> writes:


It is not clear to me - is it possible to write my own, fairly simple
template with a few modifications that are a result of some recent
changes or, for example, are elements such as those in
tempo-define-template now required?

you would need to use `tempo-define-template', yes.


OK - something new to learn!

Thank you.

Charlie

Re: [O] Please see attached debug-init

[Charles Millar]

Bastien,


On 04/28/2018 02:23 AM, Bastien wrote:

Hi Charles,

Charles Millar <mill...@verizon.net> writes:


I update org using the https:// access to the git repo.

Did you run ~$ make autoloads or ~$ make after you cloned?

You may need to compile a freshly cloned Org.


make autoloads did the trick. I previously ran "make" only.

Thank you.

charlie

Re: [O] Please see attached debug-init

[Charles Millar]

Hello,


On 04/26/2018 11:13 PM, Nick Dokos wrote:

Charles Millar <mill...@verizon.net> writes:


Hi Nicholas,

On 04/26/2018 07:34 PM, Bastien wrote:

 Hi Charles,
 
 Charles Millar <mill...@verizon.net> writes:


 Attached --debug-init when starting -
 
 is this with emacs -Q?  If not, can you bisect your configuration?
 
 Thanks,
 
emacs -Q starts fine.


The problem may be with

require 'ox-XXX

When I worked my way down to (require 'ox-texinfo) there was no problem. When I 
uncomment that line the startup error appeared.

In the warnings buffer part of the message is

error: Invalid byte opcode: op=183, ptr=31

Byte compilation is not necessarily backwards compatible.

If the file was compiled with emacs 27, then earlier versions of emacs
will not necessarily be able to deal with it. If you recompile all
*.el files with emacs 24, they should work with emacs 24 and *also*
with emacs 27.


I update org using the https:// access to the git repo.

the Emacs 24 version is the debian package. Is this a factor?

Charlie
Charlie

Re: [O] add blocks to org-structure-template-alist

[Charles Millar]

Hi, again,

On 04/27/2018 07:09 PM, Bastien wrote:

Hi Charles,

Charles Millar <mill...@verizon.net> writes:


Is this correct of has the format changed?

The format slightly changed, please check this option's docstring.

Also see ORG-NEWS here, which I just updated:

https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS#L65

Let me know if you think this is informative enough for other
users.
Prior to posting I did read the docstring for 
org-structure-template-alist in version 9.1.12 and I found nothing 
concerning "roll your own" templates. I have also read your org-news 
entry as well as the other replies.


It is not clear to me - is it possible to write my own, fairly simple 
template with a few modifications that are a result of some recent 
changes or, for example, are elements such as those in 
tempo-define-template now required?


Thanks.

Charlie Millar

[O] add blocks to org-structure-template-alist

[Charles Millar]

Hi,

in my .emacs I have a couple of (add-to-list 
'org-structure-template-alist) blocks of my own, for example


#+begin_src

(add-to-list 'org-structure-template-alist '("r" "#+begin_src rec :data? 
:type \n#+end_src" ""))


#+end_src

which I used until a few months ago.

Is this correct of has the format changed?

Charlie Millar

Re: [O] Please see attached debug-init

[Charles Millar]

Hi Nicholas,


On 04/26/2018 07:34 PM, Bastien wrote:

Hi Charles,

Charles Millar <mill...@verizon.net> writes:


Attached --debug-init when starting -

is this with emacs -Q?  If not, can you bisect your configuration?

Thanks,

emacs -Q starts fine.

The problem may be with

require 'ox-XXX

When I worked my way down to (require 'ox-texinfo) there was no problem. 
When I uncomment that line the startup error appeared.


In the warnings buffer part of the message is

error: Invalid byte opcode: op=183, ptr=31

As I mentioned earlier, very poorly, when I start emacs 27.0.50 with the 
same OS, org versio and .emacs file, I have no problem


Charlie

[O] Please see attached debug-init

[Charles Millar]

Attached --debug-init when starting -

Debian Stretch

GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.11) of 
2017-09-12 on hullmann, modified by Debian


Org mode version 9.1.11 (release_9.1.11-632-g60483f @ 
/usr/local/share/org-mode/lisp/)


However, it does not when starting emacs 27.0.50, same OS and org version

Charlie Millar



debu-error
Description: Binary data

Re: [O] Insert timestamp other than DEADLINE: or SCHEDULED: for heading

[Charles Millar]

Hello,


On 02/06/18 11:16, Tyler Smith wrote:

Hi,

I'm trying to take full advantage of scheduling, deadlines and timestamps for 
my TODO lists.  It's easy to add deadlines and schedule times via `C-c C-s` and 
`C-c C-d`. However,  if I want to set a time for a meeting, I should be using a 
regular timestamp, rather than a SCHEDULE: property. There doesn't seem to be a 
way to do this automatically.

I know I can enter a timestamp with `C-c .`, but that just inserts it at point, 
regardless of where point is with respect to the headline, logbook, property 
drawers etc. Is there a function I could use to do the equivalent of `C-c C-s`, 
i.e., jump back to the headline, move past any property drawers, and insert a 
timestamp at the beginning of a line, and then return me to where I started?

I looked at `org--deadline-or-schedule`, but there's a lot going on in there,  
and my naive hacking quickly broke it.

Not quite sure if I understand your question but it seems as if you want 
to "SCHEDULE" a meeting for a date and time using C-c C-s


Using that key combination after a TODO I usually enter the date then a 
space then the time. Also you may enter a duration such as 08:00+2


HTH.

Charlie Millar

Re: [O] Git repository error

[Charles Millar]

Hello,

Still cannot 'make update'

rm -f
git checkout
D    README_ELPA
Your branch is up-to-date with 'origin/master'.
git remote update
Fetching origin
fatal: read error: Connection reset by peer
error: Could not fetch origin
make: *** [up0] Error 1
mk/targets.mk:112: recipe for target 'up0' failed

Charlie Millar


On 12/16/17 04:43, Detlef Steuer wrote:

Am Thu, 14 Dec 2017 10:40:09 -0500
schrieb Josiah Schwab :


Hello,

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

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

I can confirm this issue at least since 13th of December.

Greetings
Detlef



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

Thanks,
Josiah

[O] Bug: RET at end of table creates new columand and new row

[Charles Millar]

Hello,

According to the manual

RET org-table-next-row
Re-align the table and move down to next row. Creates a new row if 
necessary.

At the beginning or end of a line, RET still does NEWLINE, so it can be used
to split a table.

ECM -

Create a one column, one row table, hit TAB which results in a two row, 
one column table. Point is then immediately after the last |. When I 
RET, a new column and new row are created.


Point is immediately before end-of-buffer. This may make a difference.

I would expect a new line and no continuation of the table, in any way.

Org mode version 9.1.3 (release_9.1.3-202-g326b2e.dirty @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)
GNU Emacs 25.1.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.5) of 
2016-07-21


also

Org mode version 9.1.3 (release_9.1.3-202-g326b2e.dirty @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)
GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 
2017-09-12 on hullmann, modified by Debian


Charlie Millar

Re: [O] How to suppress latex exporting as a list if a name that begins with a single letter

[Charles Millar]

On 09/27/2017 02:27, Michael Strey wrote:

Hi Charlie,

On Di, 2017-09-26 at 19:22, Charles Millar wrote:

A. Persons Name is exported as

1. Persons Name

not

A. Persons Name.

What about marking as verbatim?
=A. Person=

Best regards
Michael Strey


I will give this a try later on.

For the moment, as Eric suggested, I have reset 
org-list-allow-alphabetical to nil.


Thanks.

Charlie Millar

Re: [O] How to suppress latex exporting as a list if a name that begins with a single letter

[Charles Millar]

On 09/27/2017 02:00, Eric S Fraga wrote:

On Tuesday, 26 Sep 2017 at 19:22, Charles Millar wrote:

For example

A. Persons Name is exported as

1. Persons Name

You must have set org-list-allow-alphabetical to non-nil... maybe turn
this off?

You are correct. I did that s.. long ago I forgot.

I read the documentation and I suppose that there is no way to set that 
variable on a per file basis. Correct?


Could a header argument be implemented to override this?

Charlie Millar

[O] How to suppress latex exporting as a list if a name that begins with a single letter

[Charles Millar]

For example

A. Persons Name is exported as

1. Persons Name

not

A. Persons Name.

Charlie Millar

Re: [O] Inline source does not evaluate when inserted insie a minipage environment

[Charles Millar]

On 09/25/17 03:32, Eric S Fraga wrote:

On Sunday, 24 Sep 2017 at 16:59, Charles Millar wrote:


You might also want to consider using special blocks which could be a
more general solution:

#+attr_latex: :options [t]{4.0in}
#+begin_minipage
This is some text.
Some more test with an inline src_sh[:results raw]{echo 1} a bit more
#+end_minipage


Thanks again, I am using this suggestion.

Charlie Millar

Re: [O] Inline source does not evaluate when inserted insie a minipage environment

[Charles Millar]

On 09/23/2017 10:02, Eric S Fraga wrote:

On Friday, 22 Sep 2017 at 15:56, Charles Millar wrote:

[...]


However, when I C-c C-c the same code when inside a minipage, I get
the message " 'C-c C-c' can do nothing useful here"
\begin{minipage}[t]{4.0in} This is some text.
Some more test with an inline  src_sh[:results raw]{echo 1}
a bit more
\end{minipage}

I solve this aspect, and more generally allow the use of org formatting
directives within the text by doing:

#+latex: \begin{minipage}[t]{4.0in}
This is some text. Some more test with an inline src_sh[:results raw]{echo 1}
a bit more
#+latex: \end{minipage}


Thank you.

Re: [O] Inline source does not evaluate when inserted insie a minipage environment

[Charles Millar]

On 09/22/17 17:22, Nicolas Goaziou wrote:

Hello,

Charles Millar <mill...@verizon.net> writes:


This problem may not be limited to just \begin{minipage}, etc., but to
other latex commands which may precede text which contains inline
source code

The following inline code evaluates as expected to 1

This is some text.
Some more test with an inline  src_sh[:results raw]{echo 1}
a bit more

However, when I C-c C-c the same code when inside a minipage, I get
the message " 'C-c C-c' can do nothing useful here"
\begin{minipage}[t]{4.0in} This is some text.
Some more test with an inline  src_sh[:results raw]{echo 1}
a bit more
\end{minipage}

This is not a bug.

   \begin{minipage}
   ...
   \end{minipage}

defines a LaTeX environment, i.e., pure LaTeX code, and Org doesn't look
into this. This is like $...$ or \(...\), but as block element.

Thank you.

[O] Inline source does not evaluate when inserted insie a minipage environment

[Charles Millar]

Hi,

This problem may not be limited to just \begin{minipage}, etc., but to 
other latex commands which may precede text which contains inline source 
code


The following inline code evaluates as expected to 1

This is some text.
Some more test with an inline  src_sh[:results raw]{echo 1}
a bit more

However, when I C-c C-c the same code when inside a minipage, I get the 
message " 'C-c C-c' can do nothing useful here"

\begin{minipage}[t]{4.0in} This is some text.
Some more test with an inline  src_sh[:results raw]{echo 1}
a bit more
\end{minipage}

Org mode version 9.1.1 (release_9.1.1-62-g6e7d15.dirty @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)
GNU Emacs 25.1.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.5) of 
2016-07-21


I admit that I did only a cursory search in the list, so if the issue 
has been addressed before this, please point me in right direction.


Charlie Millar

Re: [O] Bug?? #+begin_src sh :file

[Charles Millar]

On 09/16/17 14:55, Grant Rettke wrote:

On Sat, Sep 16, 2017 at 9:09 AM, Charles Millar <mill...@verizon.net> wrote:

The following ECL is based on Grant Rettke's Org Scraps -

Correction: They are Eric Schulte's (https://www.cs.unm.edu/~eschulte/)

Thanks to Thierry and Achim for the correction and explanation and to  
Grant for the link.


Charlie

[O] Bug?? #+begin_src sh :file

[Charles Millar]

Hi,

The following ECL is based on Grant Rettke's Org Scraps - 
https://eschulte.github.io/org-scraps/scraps/2011-02-15-recutils.html


#+begin_src sh :file this.txt

cat << EOF > this.txt

1
2
3

EOF

#+end_src

When I execute the code block the file "this.txt" is created and so is a 
link, i.e.


#+RESULTS:
_file:this.txt

_However, the file is empty. According to the documentation for :file I 
expected the following in "this.txt"


1
2
3

I tried :exports results but this.txt is still empty

A bug? Or what am I missing?

Charlie Millar
__

Re: [O] Library of Babel

[Charles Millar]

On 09/15/17 19:15, Kyle Meyer wrote:

Charles Millar <mill...@verizon.net> writes:


On 09/14/17 09:47, Nicolas Goaziou wrote:

Hello,

Charles Millar <mill...@verizon.net> writes:


First. Should Sections 14.5 and 14.6 of the manual need revision since
lob has been moved to Worg? Or at least a reference to Worg site be
inserted.

Indeed. Would you want to provide a patch for that?

Thank you for the opportunity; I will leave this one to the experts.

Not an expert, but I've at least updated org.texi's Library of Babel
section (14.6) to point to Worg.  I'm not sure what needs updated in
section 14.5.

Nothing; you are correct.

Not only does the manual's pdf version need an update so does the
Library of Babel Node in Org Mode info. Please note, the pdf and the
info versions differ from each other. For example, the info version has
two additional paragraphs and states that the lob is in the contrib
directory, etc.

I don't understand.  Aren't the Info and PDF manuals generated from the
same org.texi file?

'make doc' runs

   makeinfo --no-split org.texi -o org

and

   texi2pdf --batch --clean --expand org.texi



My bad; the command line info pulls up an old orgmode info mode loaded 
with, I guess emacs 24.


Charlie

Re: [O] Library of Babel

[Charles Millar]

On 09/14/17 09:47, Nicolas Goaziou wrote:

Hello,

Charles Millar <mill...@verizon.net> writes:


First. Should Sections 14.5 and 14.6 of the manual need revision since
lob has been moved to Worg? Or at least a reference to Worg site be
inserted.

Indeed. Would you want to provide a patch for that?

Thank you for the opportunity; I will leave this one to the experts.

Not only does the manual's pdf version need an update so does the 
Library of Babel Node in Org Mode info. Please note, the pdf and the 
info versions differ from each other. For example, the info version has 
two additional paragraphs and states that the lob is in the contrib 
directory, etc.


Org mode version 9.1 (release_9.1-71-g8383f7.dirty @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/


Charlie Millar

[O] Library of Babel

[Charles Millar]

First. Should Sections 14.5 and 14.6 of the manual need revision since 
lob has been moved to Worg? Or at least a reference to Worg site be 
inserted.


Second: Am I correct that ob-lob.el has not been removed so that I can 
ingest my own source code blocks into, e.g. some/directory/cm-lob?


Charlie Millar

Re: [O] Git repository error

[Charles Millar]

HI,

On 05/26/17 06:35, Gregor Zattler wrote:

Hi org-mode developers,
* claude fuhrer  [2017-05-26; 09:39]:

On 26/05/17 01:10, Vicente Vera wrote:

Hi. For a while i've been getting this error upon running 'make up0'
from my local Org repository:

fatal: read error: Connection reset by peer



Same here - since yesterday morning.

Charlie Millar

Re: [O] bug - longtables fail to export

[Charles Millar]

Forget the noise; it appears to be a gremlin attack - a ) not }. I don't 
recall even opening the file since it was last exported.



On 04/13/2017 03:10 PM, Charles Millar wrote:
This past December the following exported with no problem (I have not 
exported a table of any type since then)


* TestTableExport :ignoreheading:
:PROPERTIES:
:EXPORT_FILE_NAME: /mnt/Data/ActiveFiles/testthetable
:END:


#+LATEX_COMPILER: pdflatex
#+LATEX_CLASS: koma-article
#+LATEX_CLASS_OPTIONS: 
[letterpaper.twoside=false,fontsize=11pt,DVI=15,parskip=half,parindent=1.2cm,headings=small]

#+LATEX_HEADER: \usepackage{verbatim}
#+LATEX_HEADER: \usepackage[T1]{fontenc}
#+LATEX_HEADER: \usepackage[math]{anttor}
#+LATEX_HEADER: \usepackage[utf8]{inputenc}
#+LATEX_HEADER: \usepackage{charter}
#+LATEX_HEADER: \usepackage{calc}
#+LATEX_HEADER: \usepackage{setspace}
#+LATEX_HEADER: \usepackage{layout}
#+LATEX_HEADER: \usepackage{array}
#+LATEX_HEADER: \usepackage{graphicx}
#+LATEX_HEADER: \usepackage{tabulary}
#+LATEX_HEADER: \usepackage{longtable}
#+LATEX_HEADER: \usepackage{numprint}
#+LATEX_HEADER: \npstyleenglish
#+LATEX_HEADER: \npthousandthpartsep{}
# #+LATEX_HEADER: \usepackage{siunitx}
# #+LATEX_HEADER: 
\sisetup{group-separator={,},group-minimum-digits={3},output-decimal-marker={.},table-number-alignment=right}
#+LATEX_HEADER: 
\usepackage[at]{easylist}{\ListProperties(Hang1=False,Indent1=1.2cm)}

#+LATEX_HEADER: \usepackage{csquotes}
# #+LATEX_HEADER: 
\usepackage[letterpaper,left=1.00in,right=1.00in,top=1.00in,bottom=1.00in]{geometry}

#+LATEX_HEADER: \pagenumbering{arabic}
#+LATEX_HEADER: \usepackage{lastpage}
#+LATEX_HEADER: \usepackage{scrlayer-scrpage}
#+LATEX_HEADER: \pagestyle{scrheadings}
#+LATEX_HEADER: \setkomafont{pagefoot}{\normalfont\rmfamily}
#+LATEX_HEADER: \cfoot[\pagemark]{\thepage}
# latex headers for this file only
#+LATEX_HEADER: \ifoot{Rita A. Sator Estate}
#+MACRO: cm2space @@latex:\ \ @@
#+MACRO: cmbcenter @@latex:\begin{center}@@
#+MACRO: cmecenter @@latex:\end{center}@@
#+MACRO: cmhfill @@latex:\hspace\fill@@



#+ATTR_LATEX: :mode table :environment longtable :align 
p{20pt}p{200pt}p{60pt)p{60pt}

| 1. | Verizon inventory value upon sale  |   | |
|| Date   |   | |
|| received 2016-12-14|   | 3142.77 |
|| reinvested dividend 2015-02-01 |  1.341086 | 51.15 |
|| reinvested dividend 2015-05-01 |  2.793883 | 113.59 |
|| reinvested dividend 2016-02-03 |  1.532931 | 51.24 |
|| Total  |   | |
|||   | |
| 2. | Vodafone PLC inventory value upon sale |   | |
|| Date   |   | |
|| received 2016-12-14| 94.910515 | 3142.77 |
|| reinvested dividend 2015-02-05 |  1.341086 | 51.15 |
|| reinvested dividend 2015-08-06 |  2.793883 | 113.59 |
|| reinvested dividend 2016-02-03 |  1.532931 | 51.24 |
|| Total  | 99.678415 | 3358.75 |
|||   | |

#+ATTR_LATEX: :mode table :environment longtable :align p{20pt}p{350pt}
| 3. | lost of stuff for this note   |
| 4. | more information for full disclosure  |
||   |
\newpage

my init has the following

(add-to-list 'org-latex-classes
 '("koma-article"
"\\documentclass{scrartcl}
\\newcommand{\\foo}{bar}
[NO-DEFAULT-PACKAGES]
[NO-PACKAGES]
[EXTRA]"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

Today the four column table does not export; the two column table 
(items labeled 3 and 4) does export; . Please see the attached report.


Org mode version 9.0.5 (release_9.0.5-444-g998576.dirty @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)
GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 
2015-03-07 on trouble, modified by Debian


If I remove the last two columns in the four column table and also 
remove the last aligns, i.e. p{60pt}, the first table then exports as 
two columns.


THEN, for the first table I re-enter the two p{60pt} and also insert 
the last two columns, with numbers, it exports as expected.

[O] bug - longtables fail to export

[Charles Millar]

This past December the following exported with no problem (I have not 
exported a table of any type since then)


* TestTableExport :ignoreheading:
:PROPERTIES:
:EXPORT_FILE_NAME: /mnt/Data/ActiveFiles/testthetable
:END:


#+LATEX_COMPILER: pdflatex
#+LATEX_CLASS: koma-article
#+LATEX_CLASS_OPTIONS: 
[letterpaper.twoside=false,fontsize=11pt,DVI=15,parskip=half,parindent=1.2cm,headings=small]

#+LATEX_HEADER: \usepackage{verbatim}
#+LATEX_HEADER: \usepackage[T1]{fontenc}
#+LATEX_HEADER: \usepackage[math]{anttor}
#+LATEX_HEADER: \usepackage[utf8]{inputenc}
#+LATEX_HEADER: \usepackage{charter}
#+LATEX_HEADER: \usepackage{calc}
#+LATEX_HEADER: \usepackage{setspace}
#+LATEX_HEADER: \usepackage{layout}
#+LATEX_HEADER: \usepackage{array}
#+LATEX_HEADER: \usepackage{graphicx}
#+LATEX_HEADER: \usepackage{tabulary}
#+LATEX_HEADER: \usepackage{longtable}
#+LATEX_HEADER: \usepackage{numprint}
#+LATEX_HEADER: \npstyleenglish
#+LATEX_HEADER: \npthousandthpartsep{}
# #+LATEX_HEADER: \usepackage{siunitx}
# #+LATEX_HEADER: 
\sisetup{group-separator={,},group-minimum-digits={3},output-decimal-marker={.},table-number-alignment=right}
#+LATEX_HEADER: 
\usepackage[at]{easylist}{\ListProperties(Hang1=False,Indent1=1.2cm)}

#+LATEX_HEADER: \usepackage{csquotes}
# #+LATEX_HEADER: 
\usepackage[letterpaper,left=1.00in,right=1.00in,top=1.00in,bottom=1.00in]{geometry}

#+LATEX_HEADER: \pagenumbering{arabic}
#+LATEX_HEADER: \usepackage{lastpage}
#+LATEX_HEADER: \usepackage{scrlayer-scrpage}
#+LATEX_HEADER: \pagestyle{scrheadings}
#+LATEX_HEADER: \setkomafont{pagefoot}{\normalfont\rmfamily}
#+LATEX_HEADER: \cfoot[\pagemark]{\thepage}
# latex headers for this file only
#+LATEX_HEADER: \ifoot{Rita A. Sator Estate}
#+MACRO: cm2space @@latex:\ \ @@
#+MACRO: cmbcenter @@latex:\begin{center}@@
#+MACRO: cmecenter @@latex:\end{center}@@
#+MACRO: cmhfill @@latex:\hspace\fill@@



#+ATTR_LATEX: :mode table :environment longtable :align 
p{20pt}p{200pt}p{60pt)p{60pt}

| 1. | Verizon inventory value upon sale  |   | |
|| Date   |   | |
|| received 2016-12-14|   | 3142.77 |
|| reinvested dividend 2015-02-01 |  1.341086 |   51.15 |
|| reinvested dividend 2015-05-01 |  2.793883 |  113.59 |
|| reinvested dividend 2016-02-03 |  1.532931 |   51.24 |
|| Total  |   | |
|||   | |
| 2. | Vodafone PLC inventory value upon sale |   | |
|| Date   |   | |
|| received 2016-12-14| 94.910515 | 3142.77 |
|| reinvested dividend 2015-02-05 |  1.341086 |   51.15 |
|| reinvested dividend 2015-08-06 |  2.793883 |  113.59 |
|| reinvested dividend 2016-02-03 |  1.532931 |   51.24 |
|| Total  | 99.678415 | 3358.75 |
|||   | |

#+ATTR_LATEX: :mode table :environment longtable :align p{20pt}p{350pt}
| 3. | lost of stuff for this note   |
| 4. | more information for full disclosure  |
||   |
\newpage

my init has the following

(add-to-list 'org-latex-classes
 '("koma-article"
"\\documentclass{scrartcl}
\\newcommand{\\foo}{bar}
[NO-DEFAULT-PACKAGES]
[NO-PACKAGES]
[EXTRA]"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

Today the four column table does not export; the two column table (items 
labeled 3 and 4) does export; . Please see the attached report.


Org mode version 9.0.5 (release_9.0.5-444-g998576.dirty @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)
GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 
2015-03-07 on trouble, modified by Debian


If I remove the last two columns in the four column table and also 
remove the last aligns, i.e. p{60pt}, the first table then exports as 
two columns.


THEN, for the first table I re-enter the two p{60pt} and also insert the 
last two columns, with numbers, it exports as expected.



This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2015/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(.//Tesgtliongtable.tex
LaTeX2e <2014/05/01>
Babel <3.9l> and hyphenation patterns for 79 languages loaded.
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls
Document Class: scrartcl 2013/12/19 v3.12 KOMA-Script document class (article)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package scrlfile, 

Re: [O] org manual not updating when pulling from git

[Charles Millar]

On 02/08/2017 11:39 AM, Nick Dokos wrote:

Charles Millar <mill...@verizon.net> writes:


So, how do you update?


I forgot about make doc; in the past I used it whenever I had to
recompile org from source; after that the pdf "just updated" each time
I pulled from git.


The question was: *how* do you pull from git? If you use one of the make
targets (e.g. make update), that's one thing; but if you use "git pull" or
some variant thereof that does *not* involve make, then the pdf would *not*
"just update" (unless you've set up some git hook to do some post-processing).


I use make update. Now it is "working" as before.

Charlie

Re: [O] org manual not updating when pulling from git

[Charles Millar]

Hi,


On 02/07/2017 02:41 PM, Nick Dokos wrote:

Charles Millar <mill...@verizon.net> writes:


When pulling from git, shouldn't the manual be updated if for no other
reason than to refelct the most recent org version?


It depends on what you mean by "the manual" - the texinfo source is updated,
but any derived files (info, pdf) are not: they are not under source control
at all.


Up unitl two or three days ago, this was my experience. Now, however,
none of the documentation seems to be updating, e g.

current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @
/usr/local/share/emacs/site-lisp/org-mode/lisp/)

pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)


"make doc" or "make pdf" will update the PDF file. If you use one of
the update targets in the makefile, it may have been updating the pdf
doc under the covers. Taking a look through recent commits, the only one
that might be relevant seems to be this:

,
| commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
| Author: Marco Wahl <marcowahls...@gmail.com>
| Date:   Wed Feb 1 11:16:16 2017 +0100
|
| targets.mk: Drop the rule to clean at every compile
|
| Rationale: 1. Save time and energy.  2. Use the make tool for what
| it's been made.
`

So, how do you update?

I forgot about make doc; in the past I used it whenever I had to 
recompile org from source; after that the pdf "just updated" each time I 
pulled from git.


Charlie

[O] org manual not updating when pulling from git

[Charles Millar]

When pulling from git, shouldn't the manual be updated if for no other 
reason than to refelct the most recent org version?


Up unitl two or three days ago, this was my experience. Now, however, 
none of the documentation seems to be updating, e g.


current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)


pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)

As far as I know I have not changed any settings on my end.

Charlie MIllar

Re: [O] bug org-capture

[Charles Millar]

On 01/31/2017 04:53 PM, Nicolas Goaziou wrote:

Hello,

Charles Millar <mill...@verizon.net> writes:


Until yesterday the following capture template worked. A recent fix
may have caused another bug.
snip

Fixed. Thank you.

Regards,


Works fine. thank you.

Charlie Millar

[O] bug org-capture

[Charles Millar]

Until yesterday the following capture template worked. A recent fix may 
have caused another bug.


(setq org-capture-templates

;;; tasks todo on a specific date, not appointments
  (append '(("t" "Todo entries")
("ts" "Scheduled" entry
 (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
 "* TODO %?%^{What do you want to do?} %^g %i\n SCHEDULED: 
%^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other pertinent 
info} %i\n\t:END:\n\t\tDate Entered %U\n"

 :empty-lines 1)

;;; tasks todo date is nice, but not earth shattering
("tt" "Target dates" entry
 (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
 "* TODO %?%^{What do you want to do?} %^g\n %i\ 
TARGETDATE: %^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other 
pertinent info} %i\n\t:END:\n\t\tDate Entered %U\n"

 :empty-lines 1)

;;; tasks with definite deadlines
("td" "Deadline" entry
 (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
 "* TODO %?%^{What do you want to do?} %^g\n  %i\ DEADLINE: 
%^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other pertinent 
info} %i\n\t:END:\n\t\tDate Entered %U\n"

 :empty-lines 1)

;;; plain vanilla task todo's
("tp" "PlainTODO" entry
 (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
 "* TODO %?%^{What do you want to do?} %i\ %^{enter a 
timestamp}t %^g\n\t:OTHERINFO:\n\t\t%^{Enter other pertinent info} 
%i\n\t:END:\n\t\tDate Entered %U\n"

 :empty-lines 1))

  org-capture-templates))

I also have a capture for entering my time worked on files

snip

("s" "timeslip" table-line
 (file "/mnt/Data/ActiveFiles/timeslips.org")
  "\| %(org-read-date)\| %^{FileName} %i\| %^{Narrative} 
%i\| %^{Time} %i\| %^{Expense} %i"


snip

Today I called the capture for the TODOs "t", the sub items show up, 
however if I select "s" the capture goes to the timeslip capture.


Org mode version 9.0.4 (release_9.0.4-252-g6b30de @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)

GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 
2015-03-07 on trouble, modified by Debian


Charlie Millar

Re: [O] org-collector not working

[Charles Millar]

Hi Malte,


On 01/02/2017 01:07 PM, Malte Deiseroth wrote:

Hello

The org-collector seems to be broken. I followed the instructions on:
http://orgmode.org/worg/org-contrib/org-collector.html

Instead of:
#+BEGIN: propview :id "december" :conds ((string= spendtype "food"))
:cols (ITEM amount)
| "ITEM"   | "amount" |
|--+--|
| "Grocery Store [2008-12-01 Mon]" |56.77 |
| "Restaurant [2008-12-08 Mon]"|30.67 |
|--+--|
|  |  |
#+END:

I get:

#+BEGIN: propview :id "december" :conds ((string= spendtype "food"))
:cols (ITEM amount)
| ITEM | amount |
|--+|
|--+|
|  ||
#+END:

and instead of:

#+BEGIN: propview :cols (ITEM (+ 400 amount)) :scope tree :match "example"
|
"ITEM"
| "(+ 400 amount)" |
|-+--|
| "December Spending
:example:" |0 |
| "Week
One"
|0 |
| "Grocery Store [2008-12-01
Mon]"|   456.77 |
| "Athletic club [2008-12-02
Tue]"|475.0 |
| "Week Two
"
|0 |
| "Restaurant [2008-12-08
Mon]"   |   430.67 |
|-+--|
|
|  |
#+END:


I get:

#+BEGIN: propview :cols (ITEM (+ 400 amount)) :scope tree :match "example"
| ITEM | (+ 400 amount) |
|--+|
| "** December Spending"   |  0 |
| "*** Week One"   |  0 |
| " Grocery Store [2008-12-01 Mo]" |  0 |
| " Athletic club [2008-12-02 Di]" |  0 |
| "*** Week Two"   |  0 |
| " Restaurant [2008-12-08 Mo]"|  0 |
|--+|
|  ||
#+END:

Basically all the columns/properties are always 0. I tried also with
other properties, but nothing worked.
I have nothing in the *Messages* or *Warnigns* buffer to post here.
I might be doing something wrong. Its the first time using org-collector
for me.
I'm using emacs 25.1.1. I believe org-mode and org-collector are shipped
by default with this.
Any help would be appreciated.

Cheers Malte



See the discussion at the list 
https://www.mail-archive.com/emacs-orgmode@gnu.org/msg104915.html.
Nicolas Goaziou pointed out that

 'snip ((string= SPENDTYPE "food"))
snip
Properties are returned upper-cased by `org-entry-properties'.

Charlie Millar
 

Re: [O] [ANN] Add EXPORT_FILE_NAME keyword

[Charles Millar]

Hi again,


On 12/21/2016 04:32 AM, Nicolas Goaziou wrote:

Hello,

Charles Millar <mill...@verizon.net> writes:



However, I tried to export a subheading with, e.g.
#+EXPORT_FILE_NAME: /foo/baz,
and
the result is /foo/bar.pdf, not /foo/baz.pdf

Where does "bar" come from?


I was not clear.  I should have shown -

* this heading
#+EXPORT_FILE_NAME: /foo/bar

** next heading
#+EXPORT_FILE_NAME: /foo/baz

If i C-c C-e C-s l o "next heading" the document in that heading is 
exported as /foo/bar.pdf, not /foo/baz.pdf


Best,
Charlie Millar

Re: [O] [ANN] Add EXPORT_FILE_NAME keyword

[Charles Millar]

Hi Nicolas


On 12/20/2016 11:17 AM, Nicolas Goaziou wrote:

Hello,

I just introduced #+EXPORT_FILE_NAME keyword, which allows to change the
output file name upon exporting a document.



Thank you and a couple of questions/observations
1. Exporting to pdf latex -

I used #+EXPORT_FILE_NAME: /foo/bar at the beginning of a document - 
worked fine.

However, I tried to export a subheading with, e.g.
#+EXPORT_FILE_NAME: /foo/baz,
and
the result is /foo/bar.pdf, not /foo/baz.pdf

This is not the same result that using the PROPERTIES construct in a 
subheading, which will export with the subheading :EXPORT_FILE_NAME: 
/foo/baz, which does generate a short document named /foo/baz.pdf


Should we be able to apply the new #+EXPORT_FILE_NAME: to a subheading 
or does it work only for an entire buffer?


Org mode version 9.0.2 (release_9.0.2-132-gc130b2 @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)
GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 
2015-03-07 on trouble, modified by Debian


2. An editorial suggestion for the realted ORGNEWS item which currently 
reads:


Simiralry to ~:EXPORT_FILE_NAME:~ property, this keyword allow to
specify the name of the output file upon exporting the document. This
has also an effect on publishing.

be changed along the following lines?

Similar to ~:EPORT_FILE_NAME:~ property, this keyword allows the user to 
specify the name of the output file upon exporting the document. This 
also has an effect on publishing (or "This also effects publishing."


Regards,
Charlie Millar

Re: [O] org-lint how to include ob-rec parameters

[Charles Millar]

Hi, again,


On 11/22/2016 12:25 PM, Nicolas Goaziou wrote:

Hello,

Charles Millar <mill...@verizon.net> writes:


The following is not a critical issue.

I use ob-rec to generate tables from my recfiles.

org-lint issues a warning for ob-recs parameters, such as data, type,
fields, sort, etc.

Is there some code that I could include in my .emacs to avoid the
warnings? For that matter is this an issue for any other non-core
babel languages and is there a general solution?

It's a bug in ob-rec. Each Babel language needs to define allowed
headers and associated values, in a variable labelled
`org-babel-header-args:LANG' where LANG is obviously the language used,
e.g., `org-babel-header-args:R' or `org-babel-header-args:latex'.

Regards,


Thank you, Nicolas.

I will post this to the recutils list.

Charlie

[O] org-lint how to include ob-rec parameters

[Charles Millar]

Hi,

The following is not a critical issue.

I use ob-rec to generate tables from my recfiles.

org-lint issues a warning for ob-recs parameters, such as data, type, 
fields, sort, etc.


Is there some code that I could include in my .emacs to avoid the 
warnings? For that matter is this an issue for any other non-core babel 
languages and is there a general solution?


Charlie Millar

[O] inline code block within export block

[Charles Millar]

Hi,

What is the syntax so that the inline source code will evaluate (SUMMARY 
is a table elsewhere in the buffer)?


#+begin_export latex

some test here src_latex[:var 
printthis=SUMMARY[-1,-1]]{\numprint{printthis}}


#+end_export

The above src_latex block evaluates if it is not within an export block.

I have used a comma at the start of the code block and well as before 
and after.


Charlie Millar

Re: [O] Blank lines after headline and before :PROPERTIES: etc

[Charles Millar]

Hi,

On 11/09/2016 06:28 PM, Nicolas Goaziou wrote:

Hello,

Charles Millar <mill...@verizon.net> writes:


Is it stated anywhere in the Org manual that blank lines are not
allowed after headlines or certain other elements.

Quoting (info "(org) Property syntax"),

   Properties are key-value pairs. When they are associated with a single
   entry or with a tree they need to be inserted into a special drawer
   (@pxref{Drawers}) with the name @code{PROPERTIES}, which has to be
   located right below a headline, and its planning line
   (@pxref{Deadlines and scheduling}) when applicable.

Improvements are welcome.

Also, see

   http://orgmode.org/worg/dev/org-syntax.html

Eventually,

   M-x org-lint

should report such issue. Actually, it doesn't, but I fixed it so it
will eventually report it.

Regards,


Thank you.

[O] Blank lines after headline and before :PROPERTIES: etc

[Charles Millar]

Hi,

I am not  a programmer, coder, whatever, and realize that many of you 
are used to inferring certain conditions by examples given in manuals, etc.


Is it stated anywhere in the Org manual that blank lines are not allowed 
after headlines or certain other elements. If not, could such 
"enlightenment" be added to the manual? As an example,


* This is a headline
:PROPERTIES:
:EXPORT_FILE_NAME: /path/to/exported/file
:END:

works as expected whereas

* This is a headline

:PROPERTIES:
:EXPORT_FILE_NAME: /path/to/exported/file
:END:

exports to a file with the buffer name.

(The above sometimes occur when I kill and yank the properties block.

Another example would be the necessity that a table immediately follow 
all elements that are used to format and generate a table.


Charlie Millar

[O] use #+INDEX: for multiple indices latex export

[Charles Millar]

Hi,

Given as a very minimal example

#+latex_header: \usepackage{imakeidx}
#+latex_header: \makeindex[title=INDEX]
#+latex_header: \makeindex[name=foo, title=FOOINDEX]

is it possible to generate multiple indices using #+INDEX:

just as

* some heading on page 1
#+latex: \index[foo]{bar}

* some heading on page 2
#+latex: \index{baz}

#+latex: \printindex[foo]
#+latex: \printindex

will give

FOOINDEX

bar, 1

. . . .

INDEX

baz, 2

Charlie Millar

Re: [O] mailing list search given problems with gmane?

[Charles Millar]

On 09/08/2016 12:16 AM, Nick Dokos wrote:

Grant Rettke <g...@wisdomandwonder.com> writes:


On Wed, Sep 7, 2016 at 5:32 PM, Charles Millar <mill...@verizon.net> wrote:

Great! Then I can find who first reported that lists.gnu.org search was not
working and when. I know that it wasn't me.

So you aren't saying that just the list for org-mode is broken you are
saying that all GNU mailing list archives are broken?!



I don't know if Charles has tried other lists on lists.gnu.org - I have only
tried searching the org-mode list, so I can only confirm that that one seems
broken.


Just the org mode list. Apologize for the confusion!
Charlie

Re: [O] mailing list search given problems with gmane?

[Charles Millar]

On 09/07/2016 05:03 PM, Nick Dokos wrote:

Eric S Fraga <e.fr...@ucl.ac.uk> writes:


On Tuesday,  6 Sep 2016 at 11:07, Charles Millar wrote:

The mail list search has been broken for more than one year (close to
two). I and others have asked that it be repaired and nothing has
happened!

Are you sure it's been broken that long?  I don't use it often but I
thought I used it more recently than that.  Oh well, doesn't matter;
just curious.  The key is that it's broken now but at least there are
alternatives.


I'm not sure whether Charles is referring to Gmane search or the
lists.gnu.org search: I understood it to be the latter. If he indeed
means the latter, I can agree that it seems broken.  It might just be
that the index is not being rebuilt regularly, or there might be some
deeper problem, but I have found it to be unusable.
Yes I did mean lists.gnu.org. Since April 2015, at least, I have 
occasionally gone to the search engine for that list to see if it has 
been repaired and I have had no luck. Either it has never been repaired 
or I somehow mange to chose just the "right" time when it is down, again.

Gmane (while it was still alive) broke a few times but it was always
repaired fairly quickly (I nagged Lars a couple of times about it, so
I may have indirectly contributed to him giving up in disgust ;-) ).
Now that Gmane is being resurrected[1], I hope that things will be
more or less back to normal in fairly short order.

[1] see another post of mine in this thread - although bear in mind
 that my posts seem to take 12 hours to appear on the list; no
 idea why.
Great! Then I can find who first reported that lists.gnu.org search was 
not working and when. I know that it wasn't me.


As I recall Nicolas G. suggested that I contact whoever maintained the 
list (he gave the address) and report this. I did, but no response.


Charlie Millar

Re: [O] mailing list search given problems with gmane?

[Charles Millar]

On 09/05/2016 11:50 AM, Eric S Fraga wrote:

Dear all,

do we have any alternative means to search the mailing list given the
current problems with gmane?


I have been using MailArchive.  A few weeks ago. Lars Magne mentioned 
this as an alternative.


Also, I have added the newsgroup in my Thunderbir. However, I have not 
downloaded the entire 100,000+ messages (only about 1K). Maybe 
downloading headers only and searching through those would help?


gnus is having problems when I attempt to download the 
subscribed/unsubscribed lists.


Charlie Millar

Re: [O] mailing list search given problems with gmane?

[Charles Millar]

On 09/06/2016 02:29 AM, Eric S Fraga wrote:

On Tuesday,  6 Sep 2016 at 01:48, Grant Rettke wrote:

On Mon, Sep 5, 2016 at 10:50 AM, Eric S Fraga  wrote:

do we have any alternative means to search the mailing list given the
current problems with gmane?

https://lists.gnu.org/archive/html/emacs-orgmode/

Thanks!
I would be lost without access to the mailing list.
The mail list search has been broken for more than one year (close to 
two). I and others have asked that it be repaired and nothing has happened!


Charlie Millar

Re: [O] Something happened in git server

[Charles Millar]

On 09/03/2016 09:36 AM, Colin Baxter wrote:

On Sat, Sep 03 2016, Takaaki Ishikawa wrote:


Hi all,

I've received an error message like `fatal: read error: Connection
reset by peer` from the git server of orgmode when I ran fetch and
also pull command. Does anybody have the same problem now?

Best,
Takaaki

Yes, the org-mode git server appears to be not working.


Yesterday morning around 8:00 EDT I tried it and it was not working then.

[O] symbol's value as vatiable is void:: result-params

[Charles Millar]

When I evaluate the following the above error results (this source blosk 
and all others that are similar evaluated successfully  a few days ago)


#+NAME: SCHEDAP
#+begin_src rec :data foo.rec :type Finance :fields 
AccountDate,Description,AccountAmount :results silent

 (File = 'RevTrust' && AccountSchedule = 'A')
#+end_src

degug on error -

Debugger entered--Lisp error: (void-variable result-params)
  (member "scalar" result-params)
  (or (member "scalar" result-params) (member "html" result-params) 
(member "code" result-params) (member "verbatim" result-params) (equal 
(point-min) (point-max)))
  (let* ((in-file ((lambda (el) (or el (error "rec code block requires 
:data header argument"))) (cdr (assoc :data params (cmdline (cdr 
(assoc :cmdline params))) (rec-type (cdr (assoc :type params))) (fields 
(cdr (assoc :fields params))) (join (cdr (assoc :join params))) (sort 
(cdr (assoc :sort params))) (groupby (cdr (assoc :groupby params))) (cmd 
(concat "recsel" (if rec-type (progn (concat " -t " rec-type " "))) " " 
(expand-file-name in-file) (if (> (length (org-babel-trim body)) 0) 
(progn (concat " -e " "\"" (replace-regexp-in-string "\"" "\"" body) 
"\""))) (if join (progn (concat " -j " join " "))) (if sort (progn 
(concat " -S " sort " "))) (if groupby (progn (concat " -G " groupby " 
"))) (if fields (progn (concat " -p " fields " ") (do-raw (or 
(member "scalar" result-params) (member "html" result-params) (member 
"code" result-params) (member "verbatim" result-params) (equal 
(point-min) (point-max) (if do-raw nil (setq cmd (concat cmd " | 
rec2csv"))) (let ((temp-buffer (generate-new-buffer " *temp*"))) 
(save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn 
(shell-command cmd (current-buffer)) (if do-raw (buffer-string) 
(org-table-convert-region (point-min) (point-max) (quote ...)) (let 
(...) (cons ... ... (and (buffer-name temp-buffer) (kill-buffer 
temp-buffer))
  org-babel-execute:rec("(File = 'RevTrust' && AccountSchedule = 'A')" 
((:colname-names) (:rowname-names) (:result-params "silent") 
(:result-type . value) (:results . "silent") (:exports . "results") 
(:session . "none") (:cache . "no") (:noweb . "no") (:hlines . "no") 
(:tangle . "no") (:eval . "never-export") (:data . "foo.rec") (:type . 
"Finance") (:fields . "AccountDate,Description,AccountAmount")))

  org-babel-execute-src-block(nil nil ((:results . "silent")))
  #[0 "\305\302\306\307#\203l

GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 
2015-03-07 on trouble, modified by Debian
Org-mode version 8.3.4 (release_8.3.4-958-gf8eb0b @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)

Re: [O] [BUG] Loading ob-shell fails with lexical binding

[Charles Millar]

Hi,


On 06/20/2016 11:56 AM, Kyle Meyer wrote:

Hello,

After moving ob-shell.el over to lexical binding (2108f0c), emacs -Q
with "(require 'ob-shell)" reports

 Debugger entered--Lisp error: (wrong-type-argument sequencep function)
   concat("org-babel-execute:" function)
   (intern (concat "org-babel-execute:" name))
 [...]

It seems to be the :initialize value of org-babel-shell-names that is
problematic.


This morning in order to load my init file I had to comment out (shell . 
t) in org-babel-load-languages


Org-mode version 8.3.4 (release_8.3.4-957-g47fdeb @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)

Re: [O] vertically misplaced thousands separator

[Charles Millar]

I just realized this behavior also occurs for just a series of letters


On 06/13/2016 08:46 AM, Charles Millar wrote:


Forgot to mention that just a plain 9.99 (no code blocks) exports 
the same way, comma above the 9.99



On 06/13/2016 08:31 AM, Charles Millar wrote:


I am not sure if this is a bug in orgmode latex exporter or whether 
it is specific to LaTeX and that there is some code that will take 
care of this.


First, attached is a copy of my LaTeX setup.

I recently added \\usepackage[npthousnadsep{,}]{numprint} to my setup.

When I export the following in line code

This is inline src_emacs-lisp[:var totalcommissions=TOTALCOM[-1,-1] 
fmt="%.2f"]{(format fmt totalcommissions)} {{{results(=9.99=)}}} 
for some reason


the thousands separator is place above the exported line, thus

,
This is inline 9.99 for some reason

Likewise, a source block, e.g.

** Block

This is a block

#+begin_src emacs-lisp :var totalcommissions=TOTALCOM[-1,-1] 
fmt="%.2f" :exports results

(format fmt totalcommissions)
#+end_src

#+RESULTS:
: 9.99

for the same code

exports as

  ,
This is a block
9.99

|{group-separator ={,}|

for the same code

Of course I expected 99,999.99 in both cases.

I also tried this with \\usepackage{siunitx} and 
\\usepackage[group-separator={,}]{siunitx} (numprint separator was 
removed) and had the same results


Org-mode version 8.3.4 (release 8.3.4 -907-g65e437 @ 
usr/local/share/emacs/site-lisp/org-mode/lisp)


GNU Emacs 24.4.1 (x86 64 -pc-linux-gnu, GTK+ Version 3.14.5) of 
2015-03-07 on trouble, modified

by Debian

Charlie Millar