On Thu, Dec 15, 2016 at 5:35 PM, Bastien Guerry wrote:
> Hi Matt,
>
> thanks for the new patch!
>
> Before applying it (and working further on it), I suggest we wait for
> Yehonathan's feedback on making klipse.js librejs-compatible. That's
> possibly a blocking issue, and we need to sort it out
Nicolas Goaziou writes:
> Hello,
>
> Matt Lundin writes:
>
>> Ian Dunn writes:
>>
>>> I encountered these issues this morning when I updated Org from
>>> trunk (and reloaded it with C-c C-x !). I believe it's following
>>> commit "Split `org-emph-re' and `org-verbatim-re'". I've got
Replying only to say that I think both the name and the idea are brilliant.
Hello Nicolas.
> Thank you. However, this is not a "fix" per se.
I agree. I should be more explicit as to what this is.
>> * lisp/org-clock.el (org-dblock-write:clocktable): Make sure to eval
>> the scope if it is a lisp expression, or to return the scope if it
>> is just a list.
>
> This co
On 12/15/16, Nicolas Goaziou wrote:
> Could you fill in the dots and give the capture template you're using?
* bug
***
[[file:$dorg/executive--a.org::*%5B%5Bfile:$dorg/executive--a.org::*test%5D%5Btest%5D%5D][test]]
link to next header
captured
says no match for fuzzy expression
***
Hello,
Samuel Wales writes:
> header a has a link on it.
>
> * [...]
>
> header b is created by capture and points to header a.
>
> * [...]
>
> this goes to the file but fails to find header a.
Could you fill in the dots and give the capture template you're using?
Thank you.
Regards,
--
Hello,
Ingo Lohmar writes:
> The culprit seems to be in org-agenda.el, ll. 6098 ff., in
> org-agenda-get-deadlines:
>
> ((eq org-agenda-skip-deadline-prewarning-if-scheduled
> 'pre-scheduled)
> ;; Set pre-warning to no earlier than SCHEDU
Hello,
Eduardo Bellani writes:
> org-clock.el: Fix clocktable scope parameter
Thank you. However, this is not a "fix" per se.
> * lisp/org-clock.el (org-dblock-write:clocktable): Make sure to eval
> the scope if it is a lisp expression, or to return the scope if it
> is just a list.
This
On Thu, Dec 15, 2016 at 5:50 PM, Matt Price wrote:
>
>
> On Thu, Dec 15, 2016 at 5:07 AM, Bastien wrote:
>
>> Hi Matt,
>>
>> Matt Price writes:
>>
>> > Would we need a switch to permit the old syntax for people with
>> > complex setups who don't want to change?
>>
>> Yes. We need to be more ca
On Thu, Dec 15 2016 21:02 (+0100), Ingo Lohmar wrote:
> [Sorry for not replying in-thread...]
>
> Hi All,
>
> after updating I'm getting the same result, but I could not reproduce it
> even with my org-config until now.
>
> The culprit seems to be in org-agenda.el, ll. 6098 ff., in
> org-agenda-g
[Sorry for not replying in-thread...]
Hi All,
after updating I'm getting the same result, but I could not reproduce it
even with my org-config until now.
The culprit seems to be in org-agenda.el, ll. 6098 ff., in
org-agenda-get-deadlines:
((eq org-agenda-skip-deadline-prewar
Hello,
"Thomas S. Dye" writes:
> orgmanual.org is an old experiment about keeping the org mode manual in
> org mode.
I don't consider it as an outdated experiment however. I welcome any
work to keep it up to date.
> The documentation is in org.texi, and this is the one you should work on
> fo
header a has a link on it.
* [...]
header b is created by capture and points to header a.
* [...]
this goes to the file but fails to find header a.
On 12/15/16, Nicolas Goaziou wrote:
> Hello,
>
> Samuel Wales writes:
>
>> file links don't hang now, thanks.
>>
>> however, if the header
org-clock.el: Fix clocktable scope parameter
* lisp/org-clock.el (org-dblock-write:clocktable): Make sure to eval
the scope if it is a lisp expression, or to return the scope if it
is just a list.
* doc/org.texi: Document the feature of using a function as the scope
for the clocktable.
Thi
Aloha Eduardo,
orgmanual.org is an old experiment about keeping the org mode manual in
org mode.
The documentation is in org.texi, and this is the one you should work on
for new documentation.
All the best,
Tom
Eduardo Bellani writes:
> Hello everyone,
>
> One extra question, about documentati
Hello everyone,
One extra question, about documentation.
The place for documenting this feature seems to be 'orgmanual.org'. But
my searches revealed that there is also 'org.texi' there. Exporting the
first file to the texi format didn't match the second file.
Is there a documentation about, wel
On Thu, Dec 15, 2016 at 5:07 AM, Bastien wrote:
> Hi Matt,
>
> Matt Price writes:
>
> > Would we need a switch to permit the old syntax for people with
> > complex setups who don't want to change?
>
> Yes. We need to be more careful on being backward compatible.
>
> The new patch in that other
Hi Matt,
thanks for the new patch!
Before applying it (and working further on it), I suggest we wait for
Yehonathan's feedback on making klipse.js librejs-compatible. That's
possibly a blocking issue, and we need to sort it out.
Thanks!
--
Bastien
Hello Nicolas,
I agree with you about introducing 'eval' into the code base. This was
just me getting the code from 8.3 back in a format the current code
understand. Which leads me to conclude that this is not new
functionality, just old undocumented functionality. I've found out about
it through
Hello,
Samuel Wales writes:
> file links don't hang now, thanks.
>
> however, if the header to be searched consists of only a link, it
> fails to find the link. perhaps it needs regexp-quote.
>
> * [[file:/home/a/b.org::*add%20another%20link%20bug][add another
> link bug]]
I'm not sure t
Hello,
Samuel Wales writes:
> in ascii export, id links to nodes that are being exported
> do not have any referent. this source prints the id but
> there is no referent for it.
>
> It is firmly outside the [scope of this post]
> (id:ab33e255f-b9f7-2fc7-6d3b-1c88ddd65590) to ask
Hello,
Eduardo Bellani writes:
> org-clock.el: Fix clocktable scope parameter
>
> * lisp/org-clock.el (org-dblock-write:clocktable): Make sure to eval
> the scope if it is a lisp expression, or to return the scope if it
> is just a list.
>
> This adds back to the clocktable the capacity to h
On Thu, Dec 15, 2016, 8:14 PM Matt Price wrote:
>
> I took a look at org.texi but my understanding of texi syntax is very poor
> and I don't think I have time to learn today.
>
Why not write the new sections in org mode, and then export to texi? :)
--
Kaushal Modi
(actually attaching the patch)
(seemed silly to have a whole bunch of tiny patches but can resubmit as a
series if that's preferred).
On Thu, Dec 15, 2016 at 9:42 AM, Matt Price wrote:
>
>
> On Thu, Dec 15, 2016 at 8:39 AM, Nicolas Goaziou
> wrote:
>
>> Hello,
>>
>> Matt Price writes:
>>
>> >
org-clock.el: Fix clocktable scope parameter
* lisp/org-clock.el (org-dblock-write:clocktable): Make sure to eval
the scope if it is a lisp expression, or to return the scope if it
is just a list.
This adds back to the clocktable the capacity to have as scope both a
list of file paths or a f
On Thu, Dec 15, 2016 at 9:50 AM, Kaushal Modi
wrote:
> On Thu, Dec 15, 2016, 8:14 PM Matt Price wrote:
>
>>
>> I took a look at org.texi but my understanding of texi syntax is very
>> poor and I don't think I have time to learn today.
>>
>
> Why not write the new sections in org mode, and then e
On Thu, Dec 15, 2016 at 8:39 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Matt Price writes:
>
> > I'm such a slow coder that this is all I got to in my free moments
> > today:patch for defcustoms that inserts the necessary code into a src
> > block. further refinements necessary before it works pro
Hello,
Matt Price writes:
> I'm such a slow coder that this is all I got to in my free moments
> today:patch for defcustoms that inserts the necessary code into a src
> block. further refinements necessary before it works properly; severla
> more would be useful for hte improvements that Bastie
Hello,
Eric S Fraga writes:
> Is it possible to have C-c C-c on an inline task headline prompt for
> tags as it would on a normal headline? I can add tags manually but my
> fingers insist on using C-c C-c...
I couldn't reproduce it, but I spotted an issue within
`org-ctrl-c-ctrl-c'. Could you
Hello,
Jeffrey DeLeo writes:
> With latest version of org:
>
> Org mode version 9.0.2 (9.0.2-elpaplus @
> /home/me/.emacs.d/elpa/org-plus-contrib-20161214/)
>
> I get the following error when trying to create an agenda:
>
> org-agenda-get-day-entries:
> Wrong type argument: number-or-marker-p, "
Hello,
Scott Otterson writes:
> This is interesting. A heading named "Footnotes" will be deleted from the
> export result (html, latex,...).
See (info "(org) Headlines").
Regards,
--
Nicolas Goaziou
Hi Matt,
Matt Price writes:
> Would we need a switch to permit the old syntax for people with
> complex setups who don't want to change?
Yes. We need to be more careful on being backward compatible.
> - make src-clojure in customizable
> ?
>
> Is this likely to break anything in deri
This is interesting. A heading named "Footnotes" will be deleted from the
export result (html, latex,...).
--- example.org: Do "C-c C-e h o" or whatever on it --
* Heading 1
* Footnotes
* Heading 3
--
33 matches
Mail list logo
