Hello,
Eric Abrahamsen writes:
> Samuel Wales writes:
>
>> in recent maint, it seems ret on link follows the link. is this
>> intended? i thought we fixed that so you could do a ret after a link
>> and get a newline?
>
> Timestamps, too, which
Hello,
Thomas Alexander Gerds writes:
> great. the updated patch is attached.
It looks good. Thank you. One minor comment below.
> for ORG-NEWS:
>
> ,
> | *** Links
> | Links stored by org-gnus-store-link in nnir groups
> |
> | Since gnus nnir groups are
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> Samuel Wales writes:
>>
>>> in recent maint, it seems ret on link follows the link. is this
>>> intended? i thought we fixed that so you could do a ret
Hello,
As discussed previously, I pushed changes about footnotes in a dedicated
branch, "wip-no-plain-fn", for testing.
In a nutshell, in this branch, Org no longer recognizes [1]-like
constructs as valid footnotes, an no longer spend time matching them.
As a consequence, "fn:" can now be
Andreas Leha writes:
> I am not sure about the possible values, though. babel header arguments
> usually take 'yes' and 'no' as values for TRUE and FALSE.
Which is, IMO, a mistake. Lisp has already some definition of TRUE and
FALSE which is not
On Dec 17, 2015 8:36 AM, "Nicolas Goaziou" wrote:
>
> org-freeming.el was replaced with ox-freeming.el, in contrib directory.
> You may want to contact its author (which may not read this list) and
> discuss if it would be possible to include the feature in that library
>
Mark Edgington writes:
> I can certainly do that, but it seems like the wrong place for it, unless
> there's some precedent for it. ox-anything should be associated with the
> export from org-mode, and not the import into it, if I'm not mistaken.
True. Nevertheless, to some
Hello,
Andreas Leha writes:
> I get a spurious linting warning
> ,
> | high Unknown header argument ":imagemagick"
> `
>
> While that header argument should be valid for latex blocks.
Assuming possible values for :imagemagick are nil and t, this is
Hi all,
I think there is a bug in the handling of results of R src blocks. What
is the suggested way to make an R block return a link to a file? The
obvious way appends a newline character to the file link (which is
broken because of that).
Here is an example:
--8<---cut
Hello,
Mark Edgington writes:
> I have in the past used the org-freemind-to-org-mode function, which
> is no longer included in org-mode. It used to be part of
> org-freemind.el file (see
>
Hi all,
I just had an error (something including "search" and "wrong side" ...)
during org-lint. As it turned out this error went away after I ran
`org-element-cache-reset'. Hence my question: Would it make sense to
include running `org-element-cache-reset' into `org-lint'?
Best,
Andreas
Hi all,
I get a spurious linting warning
,
| high Unknown header argument ":imagemagick"
`
While that header argument should be valid for latex blocks.
Regards,
Andreas
Hello,
Nikolay Kudryavtsev writes:
> Currently when org-clock-into-drawer is set to t, it moves all old
> drawer-less clock records to a new drawer. But org-log-into-drawer
> does not do the same for log entries. I think it's logical for those
> two variables to
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I get a spurious linting warning
>> ,
>> | high Unknown header argument ":imagemagick"
>> `
>>
>> While that header argument should be valid for latex
Hi everyone,
I finally got org-ref up on melpa. If you have been waiting to try it
out for that, now is your chance!
Happy Holidays!
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
Hello,
John Wiegley writes:
> Forward report to Org mailing list, and closing from Emacs bug tracker.
>
>> B V Raghav writes:
>
>> 1. I open an ORG file, with template headers, default and texinfo template.
>
>> 2. I write some simple ascii data to
Hello,
Andreas Leha writes:
> I just had an error (something including "search" and "wrong side" ...)
> during org-lint. As it turned out this error went away after I ran
> `org-element-cache-reset'. Hence my question: Would it make sense to
> include
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I just had an error (something including "search" and "wrong side" ...)
>> during org-lint. As it turned out this error went away after I ran
>>
Hi everybody,
Derek Feichtinger gmail.com> writes:
> The current MELPA version (see version details below) seems to have
problems with
> the exporter. I reinstalled several times from older configurations to
> try and exlude local effects. I get the error with all exporters I tried
>
> The
Hi Nicolas,
Nicolas Goaziou writes:
> Andreas Leha writes:
>
>> I am not sure about the possible values, though. babel header arguments
>> usually take 'yes' and 'no' as values for TRUE and FALSE.
>
> Which is, IMO, a mistake. Lisp
Andreas Leha writes:
> Exactly. I guess my implicit question was, whether we should aim to
> make :imagemagick accept 'no' as nil to be consistent with the general
> org babel conventions.
>
> As I get it, you would say: no.
Not at all. My main concern was
Hi!
John Kitchin writes:
> I finally got org-ref up on melpa. If you have been waiting to try it
> out for that, now is your chance!
Thank you John! This will certainly make it easier to install org-ref.
I'm wondering should org-ref-citeproc be included in org-ref or
I've long used the following construction for displayed equations in org
#
\[
u_i(c)=p_i\lambda
\]
#
which (i) gives nice space for reading equations in the org-source, and
(ii) nicely protects the display equation from (fill-paragraph) and
friends.
However, exporting with this construction
On Wed, Dec 2, 2015 at 5:33 AM, Rasmus wrote:
> The documentation is mostly in the source of ox.el.
Worg also has this:
http://orgmode.org/worg/doc.html
One cold and dreary evening I quickly browsed the list of hooks in
org-mode when I was curious about tangling hooks.
It is a
Hello,
Ilya Yanok writes:
> I've found that in ox.el org-export--get-inbuffer-options function calls
> org-element-map ... 'plain-text with a function that tries to use
> org-element-set-element. But according to org-element.el, plaint-text
> elements don't have a content
On Thu, 17 Dec 2015, Andreas Leha wrote:
Hi all,
I think there is a bug in the handling of results of R src blocks. What
is the suggested way to make an R block return a link to a file? The
obvious way appends a newline character to the file link (which is
broken because of that).
Here is
On Tue, Dec 1, 2015 at 10:02 AM, Loris Bennett
wrote:
> Is it possible to have a variable as part of the :file specification?
Not sure how your ECM might look but header arguments can be populated
by Emacs Lisp calls so you use whatever variables you want.
On Fri, Dec 4, 2015 at 6:38 AM, Rainer M Krug wrote:
Most Git sites using the Github Flavored Markdown, and there is a
package for that in contrib: =ox-gfm=
http://orgmode.org/cgit.cgi/org-mode.git/plain/contrib/lisp/ox-gfm.el
Hello everybody,
I'm getting a strange bug while trying to export my org file.
the stacktrace shows that the problem is inside
org-export--get-inbuffer-options function (ox.el). I've done some
investigation and as I can see
org-export--get-inbuffer-options calls org-element-map with the second
"B.V. Raghav" writes:
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know how to make a good report? See
>
> http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the
Grant Rettke writes:
> On Fri, Dec 4, 2015 at 6:38 AM, Rainer M Krug wrote:
>
> Most Git sites using the Github Flavored Markdown, and there is a
> package for that in contrib: =ox-gfm=
>
>
Hello,
Ethan Ligon writes:
> I've long used the following construction for displayed equations in org
> #
> \[
> u_i(c)=p_i\lambda
> \]
> #
> which (i) gives nice space for reading equations in the org-source, and
> (ii) nicely protects the display equation from
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
There are two things worth noting:
1. The original value for org-log-into-drawer is nil.
2. There seems to be no value that would enable movement of old records
into drawers.
So assuming somebody just discovers this variable(like me), decides that
drawers is what he wants, now he has to move
Nikolay Kudryavtsev writes:
> So assuming somebody just discovers this variable(like me), decides
> that drawers is what he wants, now he has to move all those old
> entries manually. That's not too much work, but we already have
> a better behavior example in
Hi Chuck,
"Charles C. Berry" writes:
> On Thu, 17 Dec 2015, Andreas Leha wrote:
>
>> Hi all,
>>
>> I think there is a bug in the handling of results of R src blocks. What
>> is the suggested way to make an R block return a link to a file? The
>> obvious way appends a newline
Hi Nicolas and Ethan,
Nicolas Goaziou writes:
> Hello,
>
> Ethan Ligon writes:
>
>> I've long used the following construction for displayed equations in org
>> #
>> \[
>> u_i(c)=p_i\lambda
>> \]
>> #
>> which (i) gives nice space for reading
Hello,
Andreas Leha writes:
> I agree that the paragraph should not be broken in the exported
> document. There are also other use cases for comments inside
> paragraphs.
Note that Org doesn't support comments within paragraphs since a comment
ends a
Nikolay Kudryavtsev writes:
> The main consistency problem is that t would not move log entries,
> like t moves them for org-clock-into-drawer.
There is a big difference here.
Clocks are perfectly defined in Org syntax, so one can collect them
without trouble.
I'm not suggesting t to be the default value. Here I totally agree with nil.
The main consistency problem is that t would not move log entries, like
t moves them for org-clock-into-drawer.
--
Best Regards,
Nikolay Kudryavtsev
Oh, I never thought about it like this. Not having a consistent syntax
is a good reason not to include code like this in the core. Thanks.
--
Best Regards,
Nikolay Kudryavtsev
yes, I now found the "how to contribute" page :) the updated patch is
attached. thanks!
Nicolas Goaziou writes:
> Hello,
>
> Thomas Alexander Gerds writes:
>
>> great. the updated patch is attached.
>
> It looks good. Thank you. One minor comment
Hi.
With the last update to Org-mode version 8.3.2
(8.3.2-48-g700b8e-elpaplus) the following table formular breaks:
--8<---cut here---start->8---
| | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Sum |
Hi,
Nicolas Goaziou writes:
> As discussed previously, I pushed changes about footnotes in a dedicated
> branch, "wip-no-plain-fn", for testing.
>
> In a nutshell, in this branch, Org no longer recognizes [1]-like
> constructs as valid footnotes, an no longer spend time
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I agree that the paragraph should not be broken in the exported
>> document. There are also other use cases for comments inside
>> paragraphs.
>
> Note that
Nicolas Goaziou writes:
> Hello,
>
> John Wiegley writes:
>
>> Forward report to Org mailing list, and closing from Emacs bug tracker.
>>
>>> B V Raghav writes:
>>
>>> 1. I open an ORG file, with template headers, default and
citeproc is so experimental right now I don't think it is ready to be
part of org-ref in melpa yet. It is in the git repo. If/when it becomes
useful to use, we can figure out how to include it.
Martin Yrjölä writes:
> Hi!
>
> John Kitchin writes:
>> I finally got
Nick Dokos writes:
> "B.V. Raghav" writes:
>
>> Remember to cover the basics, that is, what you expected to happen and
>> what in fact did happen. You don't know how to make a good report? See
>>
>> http://orgmode.org/manual/Feedback.html#Feedback
Nicolas Goaziou nicolasgoaziou.fr> writes:
>
> Note that Org doesn't support comments within paragraphs since a comment
> ends a paragraph. In this case, the export output matches the contents
> of the document.
>
It seems odd that a comment ends a paragraph, but does not end a footnote!
On Thu, Dec 17, 2015 at 12:47 PM Nicolas Goaziou
wrote:
> Hello,
>
> Ethan Ligon writes:
>
> > I've long used the following construction for displayed equations in org
> > #
> > \[
> > u_i(c)=p_i\lambda
> > \]
> > #
> > which (i) gives nice space
50 matches
Mail list logo