Hello,
Sébastien Delafond writes:
> On 2017-03-05, Nicolas Goaziou wrote:
>> I don't think so. Maybe we need to implement an equivalent to
>> `org-scheduled-past-days' for deadlines.
>
> That'd be awesome :)
Done in master as `org-deadline-past-days'.
Hello,
Nick Dokos writes:
> Peter Salazar writes:
>
>> Hi everyone,
>>
>> I figured out that the problem I've been having with
>> org-html-slideshow
>> (https://github.com/relevance/org-html-slideshow) is that it relies
>> on the old-style numbered
Hello,
Samuel Wales writes:
> can ascii output for id links be inline?
>
> === org source
> Some recent test results are
> [[id:aa8795c5-7ee7-48e2-84f7-49d26f371632][here]].
> ===
>
> === current output
> Some recent test results are [here].
>
> [here] See section 6.2.2.2
Hi Nicolas,
Thank you for your time. I really appreciate it.
On Tue, 07 Mar 2017 01:41:34 +0900,
Nicolas Goaziou wrote:
>
> Yasushi SHOJI writes:
>
> > I assume that the key phrase is "anywhere Org markup is recognized".
> > Link format doesn't allow Org markup, right?
Peter Salazar writes:
> Hi everyone,
>
> I figured out that the problem I've been having with
> org-html-slideshow
> (https://github.com/relevance/org-html-slideshow) is that it relies
> on the old-style numbered anchors that org-mode used to generate for
> div ID's in
Hi everyone,
I figured out that the problem I've been having with org-html-slideshow (
https://github.com/relevance/org-html-slideshow) is that it relies on the
old-style numbered anchors that org-mode used to generate for div ID's in
HTML export—the ones that looked like "sec-1-2".
Example:
can ascii output for id links be inline?
=== org source
Some recent test results are [[id:aa8795c5-7ee7-48e2-84f7-49d26f371632][here]].
===
=== current output
Some recent test results are [here].
[here] See section 6.2.2.2
===
=== possible new output
Some recent test results are in section
On 2/19/17, Samuel Wales wrote:
> * x
>link
> https://mail.google.com/mail/u/0/h/rfjkj7op114w/?=15a580ccf5cb9d34=c
>description Gmail - %( in capture template
>region
> %(alpha-org-protocol-string
>
Does anybody have a good system for writing exams with Org mode ?
Thanks,
M
signature.asc
Description: Message signed with OpenPGP using GPGMail
Matt Price writes:
> Anyone else getting this? I'm unable to publish. I don't see what is
> unlist-like about the first
> argument to plist-put.
> --
> Debugger entered--Lisp error: (wrong-type-argument listp (:base-directory
> "~/RLG231/Lectures/"
>
So, I did some more digging into this. First, I installed an older version
of org:
M-x org -version: Org-mode version 8.2.10 (8.2.10-41-g42228a-elpa @
c:/Users/mheller/AppData/Roaming/.emacs.d/elpa/org-20150601/)
With this, the clocking-related issues went away. I know this version is
probably
Anyone else getting this? I'm unable to publish. I don't see what is
unlist-like about the first argument to plist-put.
--
Debugger entered--Lisp error: (wrong-type-argument listp (:base-directory
"~/RLG231/Lectures/" :base-extension "org" :publishing-directory
Hello,
Eduardo Bellani writes:
> org-clock.el: Add nullary function evaluation as a clocktable scope
> parameter
Applied with some tiny changes: I remove "nullary function" from the
manual, preferring "function of no argument". I updated the test to
reflect latest changes
Yasushi SHOJI writes:
> I assume that the key phrase is "anywhere Org markup is recognized".
> Link format doesn't allow Org markup, right?
Not in the first part indeed. You can, however, use a macro in the
description part of the link.
> # I use
Hi everyone,
I've been using the excellent org-html-slideshow (
https://github.com/relevance/org-html-slideshow) to generate HTML slides
from org-mode, and it's been working well for me for years.
It generates HTML slides from org-mode using the org-mode heading
hierarchy. Tag any heading with
Hi Nicolas,
On Mon, Mar 6, 2017 at 5:22 PM, Nicolas Goaziou wrote:
> Yasushi SHOJI writes:
> there are two ways to interpret it: the one you expect and
>
> a_{CONTENTS} where CONTENTS is {{something}}.
>
> Since subscript syntax started first,
Hello,
Yasushi SHOJI writes:
> Ah, you mean the parser is unable to distinguish the macro and
> subscript?
It's not the parser, but the syntax. Subscript is
a_{...}
whereas macro is
{{{macro(...)}}}
so, when you see
a_{{{something}}}
there are two ways to
17 matches
Mail list logo