[O] LaTeX Export

2017-08-09 Thread Scott Randby
I have a file with a large number of top-level headlines. Each subtree 
corresponding to a top-level headline is exported to its own PDF file. The 
subtrees all use the same LaTeX headers except for \hypersetup. Right now, I 
have to uncomment the \hypersetup manually whenever I export a subtree. I would 
like to have the export engine automatically recognize which \hypersetup to use 
instead.

I tried this in the properties associated with a subtree: 

:export_latex_header: 
\hypersetup{pdfauthor={foo},pdftitle={foo},pdfsubject={foo},pdfkeywords={foo},pdfproducer={foo},pdfcreator={foo}}

Unfortunately, all the other LaTeX headers are unrecognized when I do this. I 
could put all of the LaTeX headers in the properties of each subtree, but that 
would make it difficult to make universal changes to the overall style.

Is there some way to do what I want? Something like this?

:export_add_latex_header: 
\hypersetup{pdfauthor={foo},pdftitle={foo},pdfsubject={foo},pdfkeywords={foo},pdfproducer={foo},pdfcreator={foo}}

Scott Randby

-- 
Scott Randby

sran...@gmail.com

http://srandby.org/

PGP key ID: 0xF2D38A63

Key server: http://pool.sks-keyservers.net/

Key fingerprint: 5418 123E DCD3 7DA0 1770  0BDE 301E E657 F2D3 8A63



Re: [O] agenda configurable entry-text-mode

2017-08-09 Thread Adam Porter
Alexander Baier  writes:

> This looks really nice! A few things I discovered:

Thanks, I will fix these soon!




Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

2017-08-09 Thread Tim Cross

There are also some other alternatives on the emacs-devel list from when
I asked as a general question regarding package.el and dependencies.

Should be noted that this issue is primarily caused because, fro the
package.el perspective, org-plus-contrib is different to the org
package. Other ELPA/MELPA/etc packages have org as a dependency and not
org-plus-contrib. There is no support in package.el for alternative
dependencies.

I would be interested in understanding the rationale for having
org-plus-contrib rather than just an org package and an org-contrib
package? It should be possible to just have an org-contrib package which
depends on an org package (of same version). This would then avoid this
issue. As this is an obvious solution, I suspect there is something
subtle which unpins the rationale to have an org and org-plus-contrib
package approach, but don't know what that is.

Tim

Thomas S. Dye writes:

> In case it is useful, here is Achim's post:
>
> From: Achim Gratz
> To: emacs-orgmode@gnu.org
> Subject: Re: [O] Stable releases
> Flags: replied, seen, list
> Date: Sat Aug 22 07:44:14 2015
> Maildir: /TSDYE/INBOX
> List: emacs-orgmode.gnu.org
>
> Thomas S. Dye writes:
>> I do have a technical question that you or someone else on the list
>> might be able to answer for me.  When I downloaded the Babel languages
>> from melpa just now, the elpa version of Org mode was also downloaded
>> and installed, even though I didn't ask for it.  Why is this?
>
> Although you don't say which package you tried, I would guess that the
> "org" package is specified as a dependency, likely with some minimum
> version.
>
>> Can it be disabled? Must the elpa Org mode be installed and activated
>> in order for the Org mode packages to work?
>
> From the point of package manager anything installed from the outside
> doesn't exist.  You can fake that in various way, for instance by
> creating a package directory "org-21991231" and putting an org-pkg.el
> with
>
> (define-package "org" "21991231" "Fake Org package for dependency resolution" 
> 'nil)
>
> in it.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> Waldorf MIDI Implementation & additional documentation:
> http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
>
>
> Achim Gratz writes:
>
>> Adam Porter writes:
>>> I've had the same problem, I have to manually delete the extra org
>>> package now and then.  I wonder if a dummy package would prevent
>>> package.el from reinstalling it...
>>
>> Yes it does and I've provided instructions on how to do that quite some
>> time ago on this list.
>>
>>
>> Regards,
>> Achim.


-- 
Tim Cross



Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

2017-08-09 Thread Simon Guest
This is indeed useful, thanks.

I think this may be best done by some startup code, which when installing
org-plus-contrib with require-package, deletes any existing org package,
and makes this dummy org package.

Would it be useful if such code appeared within the org-plus-contrib
package itself, so we could have this sort of usage in our .emacs:

(require-package 'org-plus-contrib)
(org-plus-contrib-remove-and-stub-org-pkg)

I'm not particularly attached to the name, but you get the point.

What do you think?

cheers,
Simon

On 10 August 2017 at 07:37, Thomas S. Dye  wrote:

> In case it is useful, here is Achim's post:
>
> From: Achim Gratz
> To: emacs-orgmode@gnu.org
> Subject: Re: [O] Stable releases
> Flags: replied, seen, list
> Date: Sat Aug 22 07:44:14 2015
> Maildir: /TSDYE/INBOX
> List: emacs-orgmode.gnu.org
>
> Thomas S. Dye writes:
> > I do have a technical question that you or someone else on the list
> > might be able to answer for me.  When I downloaded the Babel languages
> > from melpa just now, the elpa version of Org mode was also downloaded
> > and installed, even though I didn't ask for it.  Why is this?
>
> Although you don't say which package you tried, I would guess that the
> "org" package is specified as a dependency, likely with some minimum
> version.
>
> > Can it be disabled? Must the elpa Org mode be installed and activated
> > in order for the Org mode packages to work?
>
> From the point of package manager anything installed from the outside
> doesn't exist.  You can fake that in various way, for instance by
> creating a package directory "org-21991231" and putting an org-pkg.el
> with
>
> (define-package "org" "21991231" "Fake Org package for dependency
> resolution" 'nil)
>
> in it.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> Waldorf MIDI Implementation & additional documentation:
> http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
>
>
> Achim Gratz writes:
>
> > Adam Porter writes:
> >> I've had the same problem, I have to manually delete the extra org
> >> package now and then.  I wonder if a dummy package would prevent
> >> package.el from reinstalling it...
> >
> > Yes it does and I've provided instructions on how to do that quite some
> > time ago on this list.
> >
> >
> > Regards,
> > Achim.
>
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
>


Re: [O] agenda configurable entry-text-mode

2017-08-09 Thread Alexander Baier

On 07/29/2017 03:20 AM, Adam Porter wrote:

Alexander Baier  writes:


Hi Adam,

I hadn't heard of org-quick-peek.  I found
https://github.com/alphapapa/org-quick-peek but could not find the
package on MELPA, do you know why this is the case?


Hi Alexander,

Actually I haven't submitted it to MELPA yet.  I've been hoping to get
some more feedback and testing before doing that.  I guess I should have
adjusted the readme accordingly.  I would appreciate if you could give
it a quick test and let me know any feedback you may have.  :)


This looks really nice! A few things I discovered:

1. If the peek contains a link and I click on it with the left mouse 
button, the message "No link found" is displayed.


2. If a headline in the agenda contains a link to another headline and 
point is somewhere on that headline and I call org-quick-peek-link I get 
"Lisp error: (wrong-type-argument stringp nil)".


3. If point is on a link to another headline in a normal org buffer and 
I call org-quick-peek-link I get "Lisp error: (void-variable path)". 
This is fixed applying this patch:


@@ -80,7 +80,7 @@
 (org-show-following-heading nil)
 (org-show-entry-below nil)
 (org-show-siblings nil)
-link type marker)
+link type marker path)

 ;; From org.el
 (when (and (looking-at org-complex-heading-regexp))


Regards,
--
Alex




Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

2017-08-09 Thread Thomas S. Dye
In case it is useful, here is Achim's post:

From: Achim Gratz
To: emacs-orgmode@gnu.org
Subject: Re: [O] Stable releases
Flags: replied, seen, list
Date: Sat Aug 22 07:44:14 2015
Maildir: /TSDYE/INBOX
List: emacs-orgmode.gnu.org

Thomas S. Dye writes:
> I do have a technical question that you or someone else on the list
> might be able to answer for me.  When I downloaded the Babel languages
> from melpa just now, the elpa version of Org mode was also downloaded
> and installed, even though I didn't ask for it.  Why is this?

Although you don't say which package you tried, I would guess that the
"org" package is specified as a dependency, likely with some minimum
version.

> Can it be disabled? Must the elpa Org mode be installed and activated
> in order for the Org mode packages to work?

>From the point of package manager anything installed from the outside
doesn't exist.  You can fake that in various way, for instance by
creating a package directory "org-21991231" and putting an org-pkg.el
with

(define-package "org" "21991231" "Fake Org package for dependency resolution" 
'nil)

in it.


Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs


Achim Gratz writes:

> Adam Porter writes:
>> I've had the same problem, I have to manually delete the extra org
>> package now and then.  I wonder if a dummy package would prevent
>> package.el from reinstalling it...
>
> Yes it does and I've provided instructions on how to do that quite some
> time ago on this list.
>
>
> Regards,
> Achim.


--
Thomas S. Dye
http://www.tsdye.com



[O] [PATCH] Fix org-open-at-point to work with tags

2017-08-09 Thread Galen Menzel

Hi all,

I notice that org-open-at-point reports "no link found" when the point 
is on the tags in a headline, even though the mouse pointer indicates 
that emacs regards org tags as a link. I believe this is a bug, which 
the attached patch addresses.


Please let me know if I can provide any more information.

Best,

GalenFrom 151da3ae7a495d46f9a14f130e4e2022cecb9fe1 Mon Sep 17 00:00:00 2001
From: Galen Menzel 
Date: Wed, 9 Aug 2017 11:57:38 -0700
Subject: [PATCH] org.el: Fix org-open-at-point for tags.

lisp/org.el (org-open-at-point): Move case for tags up so that it's
not shortcutted by the case for no valid context.

TINYCHANGE
---
 lisp/org.el | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index 2d98ba814..52460d8f6 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -10633,6 +10633,14 @@ a timestamp or a link."
  (org-open-at-point))
  (require 'org-attach)
  (org-attach-reveal 'if-exists
+;; On tags within a headline or an inlinetask.
+((and (memq type '(headline inlinetask))
+  (let ((case-fold-search nil))
+(save-excursion (beginning-of-line)
+(looking-at org-complex-heading-regexp))
+(and (match-beginning 5)
+ (>= (point) (match-beginning 5)
+ (org-tags-view arg (substring (match-string 5) 0 -1)))
 ;; On a footnote reference or at definition's label.
 ((or (eq type 'footnote-reference)
  (and (eq type 'footnote-definition)
@@ -10668,14 +10676,6 @@ a timestamp or a link."
(point)))
  (user-error "No link found"))
 ((eq type 'timestamp) (org-follow-timestamp-link))
-;; On tags within a headline or an inlinetask.
-((and (memq type '(headline inlinetask))
-  (let ((case-fold-search nil))
-(save-excursion (beginning-of-line)
-(looking-at org-complex-heading-regexp))
-(and (match-beginning 5)
- (>= (point) (match-beginning 5)
- (org-tags-view arg (substring (match-string 5) 0 -1)))
 ((eq type 'link)
  (let ((type (org-element-property :type context))
(path (org-link-unescape (org-element-property :path context
-- 
2.14.0



Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

2017-08-09 Thread Achim Gratz
Adam Porter writes:
> I've had the same problem, I have to manually delete the extra org
> package now and then.  I wonder if a dummy package would prevent
> package.el from reinstalling it...

Yes it does and I've provided instructions on how to do that quite some
time ago on this list.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada




Re: [O] Change in appearance of org-todo-keywords

2017-08-09 Thread Adam Porter
Colin Baxter  writes:

> Considering how fundamental keywords and tags are to org-mode, I'm a
> little surprised that only two other users have reported the issue.

It's because of the bravery of users like you that I don't run master.
;)




Re: [O] Change in appearance of org-todo-keywords

2017-08-09 Thread Colin Baxter
> Colin Baxter  writes:

> Hello,

> As of today, TODO now appears with three sets of un-requested
> double colons after it, as in TODO :: :: ::

> The behaviour doesn't occur with emacs -q, so the cause is
> presumably in my ~/.emacs. I can't work out what's wrong with my
> org-todo-sequence, which is:

> (setq org-todo-keywords (quote((sequence "TODO(t)" "STARTED(s)"
> "NEXT(n@/!)" "WAITING(w@/!)"  "HOLD(h@/!)" "CANCELLED(c@/!)"
> "PHONE(p)" "BREAK(b)" "MEETING(m)" "DONE(d@/!)"  

> Also, HOLD now appears as a tag when I change from TODO to
> HOLD. Any suggestions as to how I might begin tracking down the
> cause? It's driving me nuts.

These colons now appear in agenda habits, so the "fix" of 07 Aug 2017
doesn't work. To make them disappear or at least not appear, I must not
associate any tags with the habit.

Considering how fundamental keywords and tags are to org-mode, I'm a
little surprised that only two other users have reported the issue.


-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8




Re: [O] Bug: Beamer export error

2017-08-09 Thread Rasmus
Hi Jarmo,

Thanks for your report.

Jarmo Hurri  writes:

> I get an error (pdflatex hangs up) when trying to Beamer export the
> following simple Org file (key command C-c C-e l O).
>
> # -
>
> #+STARTUP: beamer
>
> * This is a simple test
>   - let us see what happens
> # -
>
> I have traced the issue to the extra comma in the following line in the
> exported TeX file:
>
> \begin{frame}[,label={sec:org03f80c8}]{This is a simple test}
>
> If you remove the extra comma, then the file compiles just fine.

This is caused by this commit, which changes how org-split-string works.

f776e65373fa135fffb51e201698823fbfb3865b

Before (org-split-string "" ",") would return ‘nil’.  Now it returns "".

Depending on whether the new behavior is desired or not, the fix should
either be in ‘org-split-string’ or in ‘org-beamer--format-frame’.  I’ll
wait for Nicolas’ verdict.

For now, if necessary, you can hot-patch the function in ox-beamer.el to
something like,

(options (cl-remove-if-not 'org-string-nw-p (append ...)))

Rasmus

-- 
Vote for proprietary math!




Re: [O] how do you get an OPTIONS value during export?

2017-08-09 Thread Nick Dokos
John Kitchin  writes:

> Hi,
>
> In my ipynb exporter, I generate md strings for cells using something like
>
> (org-export-string-as
> s
> 'md t '(:with-toc nil :with-tags nil))
>
> This works unless there is a broken link:
>
> https://github.com/jkitchin/ox-ipynb/issues/2#issuecomment-321061051
>
> I figured out I can make it work with :with-broken-links mark, but that might 
> overrule what is in an #+OPTIONS line.
>
> So, my question is how do I get the value of what :with-broken-links should 
> be that has the right prececedence, i.e. OPTIONS > 
> org-export-with-broken-links, during the export?
>

I'm probably being dense, but I don't understand the question. Isn't
the point to overrule what the #+OPTIONS line says (for this particular
string) by adding  '( ... :with-broken links mark) to the list?

-- 
Nick




Re: [O] how do you get an OPTIONS value during export?

2017-08-09 Thread Rasmus
Hi John,

John Kitchin  writes:

> In my ipynb exporter, I generate md strings for cells using something like
>
> (org-export-string-as
> s
> 'md t '(:with-toc nil :with-tags nil))
>
> This works unless there is a broken link:
>
> https://github.com/jkitchin/ox-ipynb/issues/2#issuecomment-321061051
>
> I figured out I can make it work with :with-broken-links mark, but that
> might overrule what is in an #+OPTIONS line.
>
> So, my question is how do I get the value of what :with-broken-links should
> be that has the right prececedence, i.e. OPTIONS
> org-export-with-broken-links, during the export?

Assuming you have access to the settings, typically called ‘info’ in ox,
it should be easy,

(plist-get info :with-broken-links)

See ‘org-export-as’ in ox.el for how it’s populated.

For a user-function see ‘org-export-get-environment’.  In an export
backend, it should not be necessary as you should have the info-plist
already.  For usage of ‘org-export-get-environment’ see ox-publish.el.

Hope it helps,
Rasmus

-- 
And when I’m finished thinking, I have to die a lot




[O] iCalendar export and missed deadlines.

2017-08-09 Thread Michaël Cadilhac
Hi there;

When I miss a deadline and scheduled todo, the org-agenda neatly
prints the item until I've turned it to DONE.  In iCalendar export, I
expect/wish that it is also the case when deadlines and scheduled
todos are exported as Events (I use VEVENT's as Google Calendar seems
to not support VTODO's).  By default, this is not the case, and the
todo is simply put in the past by the iCalendar export.

Is there a way to change this behavior so that the item is duplicated
as long as it's not DONE?  If not, where is a good starting point in
ox-icalendar.el to hack this in?

Thanks very much;
Cheers



Re: [O] Bug: Beamer export error

2017-08-09 Thread Jarmo Hurri

While the bug is being fixed, here is a quick band-aid for anyone else
struggling with this problem.

1. When the export hangs up, press C-g to interrupt.
2. Run the following on the intermediate tex file, here exported.tex :
   sed -i 's/\[,/\[/g' exported.tex
3. Run pdflatex by hand:
   pdflatex exported.tex

Jarmo





[O] Bug: Beamer export error

2017-08-09 Thread Jarmo Hurri

Greetings.

I get an error (pdflatex hangs up) when trying to Beamer export the
following simple Org file (key command C-c C-e l O).

# -
#+STARTUP: beamer

* This is a simple test
  - let us see what happens
# -

I have traced the issue to the extra comma in the following line in the
exported TeX file:

\begin{frame}[,label={sec:org03f80c8}]{This is a simple test}

If you remove the extra comma, then the file compiles just fine.

Thanks in advance!

Jarmo




Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

2017-08-09 Thread Rasmus
Rasmus  writes:

> Hi,
>
> Kaushal Modi  writes:
>
>> Thanks for checking. The validator (the default one in org-html-postamble)
>> never worked for me, probably because of something being blocked at work..
>> I get this when I click the validator link:
>>
>> =
>> Sorry! This document cannot be checked.
>> No Referer header found!
>>
>> You have requested we check the referring page, but your browser did not
>> send the HTTP "Referer" header field. This can be for several reasons, but
>> most commonly it is because your browser does not know about this header,
>> has been configured not to send one, transferred the referring document
>> over a secure protocol such as https but is accessing the validator over
>> ordinary non-secure http, or is behind a proxy or firewall that strips it
>> out of the request before it reaches us.
>>
>> This is not an error in the referring page!
>> =
>
> There’s definitely some sort of issue...
>
> I guess this is for a local file?  I guess it needs to be publicly
> available.  But it doesn’t seem to work all the time even for public
> pages.
>
> Using the following example, it only works from the http version, not the
> https version.

Https pages not working is a known "bug" cf.

https://validator.w3.org/docs/help.html#faq-referer

If a JS solution is OK, we could do something like this:

  http://validator.w3.org/check?uri=referer;
 onclick="this.href=
'https://validator.w3.org/check?uri='+encodeURIComponent(document.URL)">
Validate
  

This would work with public https pages if JS is supported.  See:

https://validator.w3.org/favelets.html
https://lists.w3.org/Archives/Public/www-validator/2005Mar/0011.html

I have not found a way to send the raw source code via an url for local
files.

Rasmus

-- 
Dobbelt-A




Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

2017-08-09 Thread Rasmus
Hi,

Kaushal Modi  writes:

> Thanks for checking. The validator (the default one in org-html-postamble)
> never worked for me, probably because of something being blocked at work..
> I get this when I click the validator link:
>
> =
> Sorry! This document cannot be checked.
> No Referer header found!
>
> You have requested we check the referring page, but your browser did not
> send the HTTP "Referer" header field. This can be for several reasons, but
> most commonly it is because your browser does not know about this header,
> has been configured not to send one, transferred the referring document
> over a secure protocol such as https but is accessing the validator over
> ordinary non-secure http, or is behind a proxy or firewall that strips it
> out of the request before it reaches us.
>
> This is not an error in the referring page!
> =

There’s definitely some sort of issue...

I guess this is for a local file?  I guess it needs to be publicly
available.  But it doesn’t seem to work all the time even for public
pages.

Using the following example, it only works from the http version, not the
https version.

https://pages.gitlab.io/org-mode/
http://pages.gitlab.io/org-mode/

Rasmus

-- 
Send from my Emacs




Re: [O] clock start time is gone

2017-08-09 Thread Nicolas Goaziou
Hello,

Samuel Wales  writes:

> clocking in produces this bt:
>
> Debugger entered--Lisp error: (wrong-number-of-arguments decode-time 2)

I see. The you are missing b561c8b7efa5e88763c67d9327507e01af601352.

You need to update Org.

Regards,

-- 
Nicolas Goaziou0x80A93738