Matt Lundin writes:
> Perhaps someone with more experience of pandoc could assess how well it
> toggles between CSL and biblatex, especially for more complicated styles
> (e.g., Chicago).
Can you point out an example of the expected format? Bibtex.el does
pretty well and perhaps it’s trivial t
Rasmus writes:
> Matt Lundin writes:
>
>> Perhaps someone with more experience of pandoc could assess how well it
>> toggles between CSL and biblatex, especially for more complicated styles
>> (e.g., Chicago).
>
> Can you point out an example of the expected format? Bibtex.el does
> pretty wel
Jan Malakhovski writes:
> Nicolas Goaziou writes:
>
>> Could you provide an ECM with appropriate CLOCK lines?
>
> Attached.
Okay, so I bisected and found that the offender is
9f5e698679aecbed872a2030e4157e5e2b1d87e0. Since then these lines have
changed, so the following
diff --git a/lisp/org-a
Your mileage may vary, but this seems to show links in comments for me:
#+BEGIN_EXAMPLE
(highlight-regexp org-any-link-re 'org-link)
#+END_EXAMPLE
Eric S Fraga writes:
> On Monday, 26 Oct 2015 at 14:13, Kaushal Modi wrote:
>> Hi all,
>>
>> I am sending this out again in the event someone knowin
Hi John, Eric,
Thanks for the replies.
I will try out the highlight-regexp trick today.
The point I was trying to make was not that we should highlight links even
in comments (though that was my suggested alternative). The main point I
wanted to make was that links should not get hidden in comme
On Wednesday, 28 Oct 2015 at 07:07, Kaushal Modi wrote:
> Hi John, Eric,
>
> Thanks for the replies.
>
> I will try out the highlight-regexp trick today.
>
> The point I was trying to make was not that we should highlight links even
> in comments (though that was my suggested alternative). The main
On 2015-10-27 17:06, "Cook, Malcolm" writes:
>>
> > John Kitchin writes:
> >
> > > This reminds me that I think I have this problem unless I open Emacs
> from a
> > > command line.
> >
> > Yup - this is one way of circumvent the problem: by starting emacs from
> > the command line.
>
Hello,
Kyle Meyer writes:
> Fixed with 1c74002. Thanks for reporting the issue.
Thank you for the patch, and the tests.
Regards,
--
Nicolas Goaziou
Jan Malakhovski writes:
> Okay, so I bisected and found that the offender is
> 9f5e698679aecbed872a2030e4157e5e2b1d87e0. Since then these lines have
> changed, so the following
[...]
> I'm willing to listen, but I seriously doubt there's such a compelling
> argument defending the change. Even w
Jan Malakhovski writes:
> I'm pretty sure that there are other org-mode users that are weeping
> silently since that change. Suppose you have more than a screen of clock
> lines in LOGBOOK under a heading (I have headings that have thousands).
> (org-agenda-goto) before 9f5e698679aecbed872a2030e4
cesar mena writes:
> however the face is now `org-scheduled-today, as opposed to
> `org-scheduled-previously, and the agenda sorting is wrong. instead of
> bubbling to the top (since it is so late) it is staying within the
> "scheduled today" range.
I committed another attempt in master. Thank y
On 10/24/15 10:28 AM, Nicolas Goaziou wrote:
Peter Davis writes:
Possibly. I'm not sure how to determine that. FWIW, org-version tells
me 8.2.5g.
I suggest to update Org and try again.
I will report back when I get a chance to do the upgrade.
Thanks,
-pd
"Stefan-W. Hahn" writes:
>
> For example of a link:
>
>[[link][description]]x
>
> If cursor was at position x the old behaviour of org-return (hitting )
> was to open a new line, and position the cursor at the beginning of the new
> line. The old behaviour of org-open-at-point was to say "no l
Matt Lundin writes:
> Jan Malakhovski writes:
>
>> I'm pretty sure that there are other org-mode users that are weeping
>> silently since that change. Suppose you have more than a screen of clock
>> lines in LOGBOOK under a heading (I have headings that have thousands).
>> (org-agenda-goto) befo
On Tue, Oct 27, 2015 at 11:31 PM, Matt Lundin wrote:
> Matt Price writes:
>
> > On Tue, Oct 27, 2015 at 9:51 AM, Rasmus wrote:
> >
> >
> > Aaron Ecay writes:
> >
> > Indeed. I guess this is what they use:
> >
> > https://github.com/zotero/citeproc-node
> >
> > It also looks rat
Hello,
I have a file that exports well synchronously, but that fails when
exporting asynchronously. I set the `org-export-async-debug' to t but
the Org Export Process buffer that is left behind in not very useful.
--8<---cut here---start->8---
Source file `/Use
Aaron Ecay writes:
>
> As Nicolas said, it would be good to know if upgrading org fixes the
> issue that you see.
I just tried updated via the list-packages, but ...
1) org-version now says 8.3.2 (formerly 8.2.10)
2) I now get this error:
Making completion list...
Quit
Mark set [2 times]
org-
On Wed, Oct 28, 2015 at 10:36 AM, Matt Price wrote:
>
> That does seem to be an issue, but I bet it wouldn't be too hard to fix.
> Currently outputformat is hardcoded on line 94 of lib/citeServer.js; I'm a
> little slow at reading JS but I think replacing line 259 with a switch
> statement analog
Matt Lundin writes:
Jorge A. Alfaro-Murillo writes:
Ken Mankoff writes:
I'm using the examples from
https://www.gnu.org/software/emacs/manual/html_node/org/Exporting-Agenda-Views.html
Specifically,
(setq org-agenda-custom-commands [...]
But the HTML, PS, and ICS files are not bein
Hi,
Anyone else seeing this?
I'm trying to update Org for the first time in ages, using "make
update2" on Mac OS X 10.6.8. (No, haven't upgraded that for a while,
either.)
The process gets as far as "Compiling path/to/lisp/org-timer.el" and
hangs there until I kill it.
Yours,
Christian
On 10/28/15, John Kitchin wrote:
> Your mileage may vary, but this seems to show links in comments for me:
>
> #+BEGIN_EXAMPLE
> (highlight-regexp org-any-link-re 'org-link)
> #+END_EXAMPLE
nice workaround! thanks!
it's a matter of perspective. comments mean two separate things:
1] "comment
(highlight-regexp org-ts-regexp3 'org-date)
Hi all,
babel's :cache seems to be ignored during export. At least on #+call
lines.
In the example below the caching works fine for interactive evaluation,
i.e. C-c C-c on the #+call line returns immediately.
If I export the subtree with the #+call line, however, the code block
gets executed an
Hi all,
Andreas Leha writes:
> Hi all,
>
> babel's :cache seems to be ignored during export. At least on #+call
> lines.
>
> In the example below the caching works fine for interactive evaluation,
> i.e. C-c C-c on the #+call line returns immediately.
>
> If I export the subtree with the #+call
When I export file to PDF/ODT, the source block is start from left without
indent.
How to add some indent?
25 matches
Mail list logo