Re: [O] Org agenda

2018-01-07 Thread Eric S Fraga
On Saturday,  6 Jan 2018 at 14:13, M. P. wrote:
> I create a TODO and save the file but I can’t see the todo when I
> select todo view in agenda? What am I doing wrong?

Ignore my previous response.  I misread your email.

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


signature.asc
Description: PGP signature


Re: [O] Org agenda

2018-01-07 Thread Eric S Fraga
On Saturday,  6 Jan 2018 at 14:13, M. P. wrote:
> I create a TODO and save the file but I can’t see the todo when I
> select todo view in agenda? What am I doing wrong?

TODO items without schedule or deadline will not appear in the default
agenda view.  Did you schedule the TODO?

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


signature.asc
Description: PGP signature


[O] Stop org from deleting empty lines between the previous heading.

2018-01-07 Thread Shiyao MA
Hi,

I use M-ret org-meta-return to insert a new headline below the current line.

I want org to insert a new heading right below the current line without
inserting any empty line.

However,  setting  ;; org-blank-before-new-entry '((heading . nil)
(plain-list-item . nil))

will make org *delete* the empty lines between the newly inserted heading
and its previous heading.


-- 
Best,
Shiyao


[O] org-tempo and org-structure-template-alist changes

2018-01-07 Thread Rustom Mody
Recent changes to org (not sure when), seem to have changed the type
of org-structure-template-alist

This broke org-reveal : https://github.com/yjwen/org-reveal

I suggested (without too much knowledge) the attached patch to the reveal folks
(Issue: https://github.com/yjwen/org-reveal/issues/315#issuecomment-355868192 )

Now someone has asked that that patch be made into a pull-request

It would be good if someone here can look at the patch in the light of
these recent changes and see
if the patch looks ok
--- ox-reveal.el2017-12-24 16:59:00.993293157 +0530
+++ ox-reveal-new.el2017-12-24 17:54:22.293899742 +0530
@@ -359,7 +359,7 @@
   :group 'org-export-reveal
   :type 'string)
 
-(defcustom org-reveal-note-key-char "n"
+(defcustom org-reveal-note-key-char ?n
   "If not nil, org-reveal-note-key-char's value is registered as
   the key character to Org-mode's structure completion for
   Reveal.js notes. When `<' followed by the key character are
@@ -1228,7 +1228,7 @@
 ;; Register auto-completion for speaker notes.
 (when org-reveal-note-key-char
   (add-to-list 'org-structure-template-alist
-   (list org-reveal-note-key-char 
"#+BEGIN_NOTES\n\?\n#+END_NOTES")))
+   (cons org-reveal-note-key-char "notes")))
 
 (provide 'ox-reveal)
 


[O] filter for svg latex-export

2018-01-07 Thread edgar

Hello,

I once tried to create a filter (is that the name?) to modify the 
function which exports SVG files. Verdict: I suck! Thus, I keep 
modifying the ox-latex.el every time that I upgrade (see attached). 
Would someone please tell me what is the right way to achieve that 
(without modifying the code, please? Thanks!


-

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

Commercial and Bulk Mail Options!  *** org-20180103/ox-latex.el2018-01-07 16:53:43.477464348 -0700
--- plugins/ox-latex.el 2018-01-07 16:39:52.117462098 -0700
***
*** 2425,2434 
  (t (format "[%s]" options)))
path))
(when (equal filetype "svg")
!   (setq image-code (replace-regexp-in-string "^includegraphics"
!  "\\includesvg"
!  image-code
!  nil t))
(setq image-code (replace-regexp-in-string "\\.svg}"
   "}"
   image-code
--- 2425,2437 
  (t (format "[%s]" options)))
path))
(when (equal filetype "svg")
! (setq image-code
!   (format "\\simplesvg%s{%s}"
!   (cond ((not (org-string-nw-p options)) "")
! ((string-prefix-p "," options)
!  (format "{%s}" (substring options 1)))
! (t (format "{%s}" options)))
!   path))
(setq image-code (replace-regexp-in-string "\\.svg}"
   "}"
   image-code


Re: [O] inherit priority

2018-01-07 Thread Jesse Johnson

Hi,

I am trying to determine the functions I need to add / update to respect 
priority inheritance.


I see that org-show-priority would need to be updated, and likely a new 
function, say org-get-priority-with-inheritance, should supplement 
org-get-priority.


However, I can't figure out where org-colview is getting the priority 
from. It seems to be parsing and validating the priority prior to 
display since it regresses to org-default-priority if I input 
[#NONSENSE] priorities.


I also don't know where sorting is considering priority.

Help with pointing me in the right direction for either of those would 
be much appreciated! Also let me know if other things touching priority 
need updating for inheritance.


Jesse


On 01/04/2018 11:24 PM, Nicolas Goaziou wrote:

Hello,

Jesse Johnson  writes:


There have been several requests for priority inheritance over the
years.

That doesn't ring a bell.


If it can't currently be done,

I don't think it can, atm.


I am willing to take a look at implementing it.

OK!

IMO, there should be a global variable to allow priority inheritance
(default off).

Regards,






[O] org-radio tables in latex |p{3cm}

2018-01-07 Thread Uwe Brauer

Hi

Consider please

\documentclass[12pt]{article}
\usepackage{commment}
\begin{document}

% BEGIN RECEIVE ORGTBL test
\begin{tabular}{l|l|}
this & that\\ \hline
\end{tabular}
% END RECEIVE ORGTBL test
\begin{comment}
#+ORGTBL: SEND test orgtbl-to-latex  :lend " \\hline" :environment tabular
| / | <>   | <>   |
|   | this | that |
\end{comment}


\end{document}

So the construct |<>| gets expanded to |l|
which is ok, but I also want to obtain a result such as |p{3cm}|

How can I achieve  that?

https://orgmode.org/manual/Radio-tables.html#Radio-tables

Did not give any hints, thanks

Uwe Brauer 




[O] org table with datestamp convert to csv and then xlsx or ods: problem

2018-01-07 Thread Uwe Brauer

Hi

consider please

| Entry | Date   |
|   100 | <2018-01-07 Sun> |

I first export this to csv


Entry,Date
100,<2018-01-07 Sun>



and then via gnumeric ssconvert or LO unoconv
to xlsx or ods, however the datestamp is not correctly converted to a
datestamp understood my xlsx or unoconv.

Is this a lacking feature or a bug?

Uwe Brauer 




Re: [O] Bug: Broken orgmode.org links in doc/misc/org.texi and lisp/org

2018-01-07 Thread Kaushal Modi
On Sun, Jan 7, 2018, 8:46 AM Tim Landscheidt  wrote:

> (All links to http://orgmode.org/ should be updated to
> https://orgmode.org/ and a slash should be added to
> https://orgmode.org/worg/org-contrib/babel to avoid a
> redirect.)
>
> The following links in Emacs master's doc/misc/org.texi and
> lisp/org are broken (404):
>
> - https://orgmode.org/org-remember.pdf
> - https://orgmode.org/worg/code/org-info-js/
> - https://orgmode.org/worg/org-contrib/babel/languages.html
> -
> https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html
> - https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-stan.html


Interesting the code/, org-contrib/babel/languages/ and sources/ links work
fine if I build Worg locally.

@Bastien: Can you please check what's preventing generation? Or  just
copying of those sub directories on the Worg server?

And there are many more broken links (250+) on Worg (most of those are now
external links to blogs, etc that people posted a long time back). I'll
slowly work through fixing the broken links. Help from others too in this
would be great. Simply run an online broken link or dead link tester, and
you'll see the full list. I used this: http://www.brokenlinkcheck.com/, and
it seems pretty good even with the 3000 page scanning limit in the free
version. The W3C broken link detector isn't very good. Does someone have a
better way to find *all* broken links?
-- 

Kaushal Modi


[O] Bug: Broken orgmode.org links in doc/misc/org.texi and lisp/org

2018-01-07 Thread Tim Landscheidt
(All links to http://orgmode.org/ should be updated to
https://orgmode.org/ and a slash should be added to
https://orgmode.org/worg/org-contrib/babel to avoid a
redirect.)

The following links in Emacs master's doc/misc/org.texi and
lisp/org are broken (404):

- https://orgmode.org/org-remember.pdf
- https://orgmode.org/worg/code/org-info-js/
- https://orgmode.org/worg/org-contrib/babel/languages.html
- https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html
- https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-stan.html



Re: [O] Org citations, CSL and citeproc-el

2018-01-07 Thread András Simonyi
Dear All,

thanks a lot for the helpful responses!

Richard Lawrence  wrote:
> I don't know if you are aware, but we had discussed the possibility
  > of building something like this on the list a few years back. [...]
  > And here is how I summarized the state of that discussion in June:
  > https://lists.gnu.org/archive/html/emacs-orgmode/2015-06/msg00426.html
  > The upshot was that we came to agreement on quite a few points about what
  > citation syntax should look like, and those points have been implemented in 
Org
  > syntax in the wip-cite branch of the Org repo.

I found some of the discussion, but not your summary and the
cite-related branches -- these are very useful.

  > 1) BibLaTeX support.
  > 2) org-bibtex support.

I'll have to look into BibLaTeX more but I suspect that both of these
should be doable relatively easily on the basis of the already existing
(albeit by no means complete) BibTeX support in citeproc-el. I'll create
corresponding enhancement issues in the github repo. A related thought:
was there any initiative to create something like org-bibtex but for CSL
bibliography descriptions? It could be an interesting alternative to
citeproc-YAML (see
http://blog.martinfenner.org/2013/07/30/citeproc-yaml-for-bibliographies/).

I've checked the citation/cite syntax in the wip-cite branch and it
seems to be a good starting point for trying to use citeproc-el to
render the citations. As a first step I could simply abstract away the
syntax and add a switch in citeproc-orgref to choose between the org-ref
and the the org-mode citation syntax (as it is in the wip-cite branch),
without touching other parts of the code. Currently citation rendering
is done (following org-ref's citeproc) by means of the
`org-export-before-parsing-hook' -- all citations are replaced with
their rendered versions before parsing. I'm not familiar enough with
org-mode's internals to assess how hackish this solution is, maybe there
is a much better way. One thing to consider is that I need all citations
together with their positional information (order, footnote number etc.)
for rendering in order to deal with disambiguation, ibid. forms etc.

Another question is the syntax for specifying the bibliography to be
used and, maybe, the location where the bibliography should be placed.
Org-ref (ab)uses links for these purposes as well. Was there a syntax
proposal for these things too?

Christian Moe  wrote:
  > Not many people liked my proposal: a link-based syntax similar to yours
  > but also including author and date in the link description. The idea was
  > to have descriptions that are both (1) human-readable even though the
  > citekeys are hidden away in the link path and (2) machine-readable to
  > determine the form of the citation (parenthetical or not, date-only or
  > not, etc.).

This is an interesting proposal -- I like the idea of human readable
citations in the unexported org-mode documents but I'm not sure what
would be the best way to achieve them. citeproc-el can render isolated
references on the fly so they could be perhaps used as tool-tips or
overlays? Another difficulty I see is the generation of this added
information -- would it be automatic? What happens if the author or the
year is missing, or is ambiguous etc. If I could get hold of your parser
then perhaps this could also be added as an alternative citation syntax
in citeproc-orgref. Another option could be to normalize the keys to a
disambiguated author-year format, but this would modify the bibliography
file which is not necessarily a good idea...

thanks again and best regards,

András



Re: [O] Bug: Clock times not summed correctly between years [9.0.9 (9.0.9-82-gb862c2-elpa @ ~/.emacs.d/elpa/org/)]

2018-01-07 Thread Paul Stansell
I see that the exact same "bug" was reported at the start of 2016 by
David Bremner.  Personally, I feel that fewer people would be confused
by this if the default value was set to "untilnow".

I also realised that the full list of values that I can use for
org-clock-display-default-range is described in org-clock.el.

By the way, you guys are brilliant and I thank you for your work on
org mode (which I'd struggle to live without now that I'm so dependent
on it).


Re: [O] clocktable :formula not working for columns > $9

2018-01-07 Thread Nicolas Goaziou
Hello,

Brian J Hoskins  writes:

> When generating a clocktable and using the :formula parameter, attempts
> to manipulate columns > $9 are unsuccessful.
>
> For example, consider the attached (anonymised) screen-grab of the
> output from a clocktable in one of my org files.
>
> As a test, I have used the :formula parameter to create sequential
> columns.  It works up to and including column 9, but fails thereafter.
> No error is generated.  Here is the generated #+TBLFM line:
>
> #+TBLFM: @1$4 = (4)::@1$5 = (5)::@1$6 = (6)::@1$7 = (7)::@1$8 =
> (8)::@1$9 = (9)::@1$10 = (10)::@1$11 = (11)
>
> This formula works fine on tables that I create myself.

It only works if the initial table contains enough columns. Try:

| 1 |
#+TBLFM: 
@1$1=(1)::@1$2=(2)::@1$3=(3)::@1$4=(4)::@1$5=(5)::@1$6=(6)::@1$7=(7)::@1$8=(8)::@1$9=(9)::@1$10=(10)::@1$11=(11)

> If this failure can be repeated by other org-mode users, perhaps we
> should file a bug report.

Confirmed and fixed. Thank you.

By default, according to `org-table-formula-create-columns', Org ought
to refuse to apply such a formula, which is now the case.

Consider setting `org-table-formula-create-columns' to a non-nil value.

Regards,

-- 
Nicolas Goaziou



Re: [O] Equation references in HTML export

2018-01-07 Thread Thibault Marin

Hi, thank you for the review.

> I'm not convinced that inserting label and, more importantly,
> caption within the environment is the way to go. For example, that
> will not work when `org-html-with-latex' is set `verbatim'. Couldn't
> we simply wrap a HTML label and caption above, or below, the whole
> environment so it DTRT in all cases?

It is true that my patch did not address the verbatim mode, I was
focusing on the MathJax output.  The reason I initially decided to rely
on MathJax is that I thought it would be better to take advantage of
MathJax support for LaTeX label and references.  It was then sufficient
to delegate rendering of the latex-environment and links to ox-latex,
although I ended with some unpleasant code to achieve that.

To make sure I understand the desired HTML output, do you mean that
instead of producing this HTML:
,
| \begin{align}
| \label{eq:orgbfedefe}
| 1 + 1 = 0
| \end{align}
`
and relying on MathJax to manage references, we should produce something
like the following?
,
| 
| \begin{align}
| 1 + 1 = 0
| \end{align}
| 
| 
`

Am I understanding correctly?

The advantage of this approach is that it is consistent with how the
other types of references (figures, source blocks, etc.) are managed and
it should work with the verbatim mode.

I have a few questions about the "caption" (i.e. the equation number):

1. Where should it be placed?  In a `' tag like it is done for
   figures?  Ideally, I would like to have the caption (i.e. the
   equation number) on the right side of the equation, as it is done in
   LaTeX, should this be done with CSS?  Should there be a user option
   for the position of the caption?
2. Should we disable MathJax's equation numbering and replace it with
   ours?  I am afraid this may break the setup of users already relying
   on MathJax to label and reference equations.
3. Should there be an option to customize the formatting of the equation
   number, both on the right of the equation itself and in links
   (e.g. wrap the number between parentheses, as `\eqref' dose)?

The attached patch tries to implement some version of this approach.
The code looks less hackish to me, but I still rely on a variable
external to ox-html.el: I use `org-latex-math-environments-re' to
determine if the LaTeX block is a math block; this is used to limit
counters to equations environments, ignoring other types of latex
environments.  Also note that I did not disable MathJax auto-numbering
in the attached patch, so equations have two numbers.

My main concern with this revised version of the patch is the possible
conflicts between MathJax and org equation numbers:
- Only one equation number should be shown, and MathJax and org counters
  may not match (e.g. with multiline equations).
- If we disable MathJax auto-numbering, it seems that we would be losing
  the possibility to have labels on individual lines of multiline
  equations.  Is it true?

Please let me know how you would like me to move forward with this.

Thanks in advance.

thibault

>From 4f57de3208bfe7a86f17c89c15fdc99283701e82 Mon Sep 17 00:00:00 2001
From: thibault 
Date: Sun, 7 Jan 2018 03:04:39 -0600
Subject: [PATCH] ox-html.el: Add label and number to equations in HTML export

* lisp/ox-html.el (org-html--wrap-latex-environment): New function
wrapping the content of latex environments in HTML  tags, adding
"id" and equation number.
(org-html--is-math-environment): New function determining if a latex
environment is a math environment.
(org-html-latex-environment): Use `org-html--wrap-latex-environment' to
wrap equation in HTML container.
(org-html-link): Calculate equation number limiting counter to equation
environments.
---
 lisp/ox-html.el | 57 +
 1 file changed, 53 insertions(+), 4 deletions(-)

diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index 90a6cede0..566f057ac 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -430,6 +430,18 @@ for the JavaScript code in this tag.
   .footdef  { margin-bottom: 1em; }
   .figure { padding: 1em; }
   .figure p { text-align: center; }
+  .equation-container {
+display: table;
+text-align: center;
+width: 100%;
+  }
+  .equation {
+vertical-align: middle;
+  }
+  .equation-label {
+display: table-cell;
+text-align: right;
+  }
   .inlinetask {
 padding: 10px;
 border: 2px solid gray;
@@ -2823,16 +2835,49 @@ INFO is a plist containing export properties."
 			"Creating LaTeX Image..." nil processing-type)
   (buffer-string
 
+(defun org-html--wrap-latex-environment (contents info &optional caption label)
+  "Wrap CONTENTS string within appropriate environment for equations.
+INFO is a plist used as a communication channel.  When optional
+arguments CAPTION and LABEL are given, use them for caption and
+\"id\" attribute."
+  (format "\n\n%s%s\n"
+  ;; ID.
+  (if (org-string-nw-p label) (format " id=\"%s\"" label) "")
+  ;; Contents.