>>> "Nicolas" == Nicolas Goaziou writes:
> Hello,
> Uwe Brauer writes:
>> When finishing a note and running C-c C-c I obtain an error which I
>> attach
>> ,
>> |
>> | Debugger entered--Lisp error: (error "Invalid version syntax: ‘N/A’
(must start with a number)")
>
Hello,
Thank you for your quick patch.
Since I wasn’t able to solve it on my own, I’ll take a look at
your solution to understand what you did.
Have a great day.
Best,
Nicolas Goaziou writes:
Hello,
Leo Vivier writes:
Hello,
There seems to be a bad interaction between
‘(org-resolve-c
Hello,
"Ulrich G. Wortmann" writes:
> no. I did not. How do checkout the "next" branch?
You need to install Org from git, as described in the manual. Then,
before calling "make", just use "git checkout next".
Regards,
--
Nicolas Goaziou
Hello,
Bernt Hansen writes:
> There is a regression in the master branch.
>
> In master if you use
> M-x org-capture
> t
> and save your task with C-c C-c
> then go to the task with C-u C-u M-x org-capture
> you end up after the captured task instead of on the headline of the
> newly captured ta
Hello,
Here is a MWE:
1. With point on the "** Foo" section, running C-c C-e C-s h o, will
result in noweb-duplicate-bug.html with the <> block
expanded only once, as expected.
2. But with point on the "* Foo Included" section, running the same
C-c C-e C-s h o, will result in foo_included.html w
Hello,
Allen Li writes:
> On Tue, Dec 4, 2018 at 2:14 AM Allen Li wrote:
>>
>> Or did you mean ITEM omits the stars? That doesn't appear to be the
>> case as of 04641c4bbefc5f90e05fe4e846f4aeab15f1c262 on master
>> yesterday.
>
> So org-entry-properties does indeed return ITEM without the lead
Hi
I am using the following function (I think provided generously by John
Kitchin)
org-ref-get-bibtex-entry-html (key)
(defun org-ref-get-bibtex-entry-html (key)
"Return an html string for the bibliography entry corresponding to KEY."
(let ((output))
(setq output (org-ref-get-bibtex-en
Nicolas Goaziou writes:
> Hello,
>
> Bernt Hansen writes:
>
>> There is a regression in the master branch.
>>
>> In master if you use
>> M-x org-capture
>> t
>> and save your task with C-c C-c
>> then go to the task with C-u C-u M-x org-capture
>> you end up after the captured task instead of on
Hello,
emanuel.charpent...@gmail.com writes:
> Please find enclosed a proposed patch (against master) to document the
> need for babel/polyglossia in order to honor #+language in LaTeX
> export.
I applied your patch with slight modifications.
Thank you.
> This is purely a documentation patch.
How does org identify which table rows should be exported with header tags?
It seems rows above a horizontal line are automatically converted using
tags. Is there a way of controlling this?
My specific use case is that I have a multi-row table header created in an
R code block. I do not have a wa
On Thu, Dec 6, 2018 at 6:35 AM Nicolas Goaziou wrote:
> We could ignore the level when displaying ITEM in agenda column view. As
> a consequence, every item would start with a single star, which is
> shorter and still not confusing.
Sounds good to me.
>
> WDYT?
>
> Regards,
>
> --
> Nicolas Goaz
At the moment, ob-R.el does not support :colnames to have a list of column
names as an argument. This seems to have been raised on the list many years
ago [1], but it does not look like it was implemented. Is there a
possibility that this could be implemented?
Also, is it possible to allow :hlines
12 matches
Mail list logo