I have been curious too and found this file:
https://bitbucket.org/blais/beancount/src/tip/examples/tutorial/example.beancount
Eric S Fraga schrieb am Sun, 09. Nov 13:29:
On Sunday, 9 Nov 2014 at 11:34, Daniel Clemente wrote:
[...]
I prefer beancount (very similar to ledger but stricter)
Sharon Kimble writes:
> I am able to 'remember' text with highlighting the text required, and
> copying it to the clipboard, and then "C-c r" remembers it, and shows in
> its popup buffer that I need to "C-c C-c" to copy/move it to my remember
> storage file. Except, the last bit doesn't work for
Nicolas,
Thanks for your feedback. I agree that using the same link type is better.
Hence I took an alternate approach as detailed in the attached patch.
Enhanced org-info-follow-link to attempt index lookup if node lookup fails.
Following is my check in message found in the attached patch:
On 2014-11-10, at 00:08, Nicolas Goaziou wrote:
> Marcin Borkowski writes:
>
>> Sorry for the noise, it seems to be working now. (I threw out the
>> code, but AFAIR the non-uniqueness arised with ordinals of /items/ in
>> different lists.)
>
> Yes, ordinals for items are relative to the list th
Christopher Dannheim writes:
> org-element-context yields:
> (paragraph (:begin 6145 :end 6166 :contents-begin 6145 :contents-end 6165
> :post-blank 1 :post-affiliated 6145 ...))
>
> After relaoding org:
> (link (:type "textcite" :path "Hobart2003" :raw-link "textcite:Hobart2003"
> :application n
Marcin Borkowski writes:
> Sorry for the noise, it seems to be working now. (I threw out the
> code, but AFAIR the non-uniqueness arised with ordinals of /items/ in
> different lists.)
Yes, ordinals for items are relative to the list they belong to. OTOH
for plain lists, this is the sequence nu
On 2014-11-09, at 09:24, Nicolas Goaziou wrote:
> Marcin Borkowski writes:
>
>> Thanks, but this is not really what I'd like to have: the strings
>> generated by org-export-get-ordinal are /not/ unique throughout the file
>> (they seem to be unique within one level of hierarchy).
>
> They should
Nicolas Goaziou writes:
> It should be \ref{photo1}/\label{photo1} in this case. I pushed a fix
> for that in maint.
Thanks for the fix.
Julien.
> CM :
> I cannot reproduce either problem, though I seem to remember some
> difficulty with changing date fields in the past. What Org version are
> you using?
Um... a heap of different versions it looks like, on the systems I use
regularily, some from ELPA (one of the ELPA archives), some f
Hi Nathaniel
On Sun, Nov 9, 2014 at 11:18 AM, Nathaniel Flath wrote:
> Updated patches attached.
The second does not apply after the first on today's
release_8.3beta-552-ga95cfeb. Unrelated: The second has new closing
parentheses on an own line.
Michael
On Sunday, 9 Nov 2014 at 11:34, Daniel Clemente wrote:
[...]
> I prefer beancount (very similar to ledger but stricter): beancount
> supports org out of the box! My beancount file is an org file (with
> structure, tasks, priorities, agenda, etc. except :CLOCK:) and it
> parses correctly as a l
Updated patches attached.
0001-org-table.el-org-table-recalculate-early-returns.patch
Description: Binary data
0002-org-table.el-org-table-recalculate-is-quieter.patch
Description: Binary data
Marcin Borkowski writes:
> Thanks, but this is not really what I'd like to have: the strings
> generated by org-export-get-ordinal are /not/ unique throughout the file
> (they seem to be unique within one level of hierarchy).
They should be unique. How did you use this function?
Regards,
13 matches
Mail list logo
