wrote:
>
> [CC'ed to Takafumi Arakaki, author of orgparse]
>
> Hello François,
>
>> Do you know happen to know how conforming it is?
>
> I can't comment on that, since I haven't really used it for anything.
>
>> I wrote many ad hoc parsers for Org already,
It turned out that the bug I encountered was due to
after-change-function in flyspell-lazy. It alters the
match data that's why org-entry-put worked unexpectedly.
https://github.com/rolandwalker/flyspell-lazy/pull/4
On Sun, Dec 2, 2012 at 9:39 AM, Nicolas Goaziou wrote:
> Takafumi
(6642177dee3ec04404ebd99391748f373ada3d2a) result was the same.
Takafumi
On Fri, Nov 9, 2012 at 3:34 PM, Takafumi Arakaki wrote:
> Thanks, I will check maint first then.
>
> Takafumi
>
> On Fri, Nov 9, 2012 at 2:25 PM, Nicolas Goaziou wrote:
>> Hello,
>>
>> Takafumi Arakaki wr
specifying a
root tree. This will make test easier, but I guess it is better to
test with a "plain" configuration first.
Takafumi
On Fri, Nov 9, 2012 at 2:28 PM, Nicolas Goaziou wrote:
> Takafumi Arakaki writes:
>
>> I am not familiar with org-mode test suite but I can try.
Thanks, I will check maint first then.
Takafumi
On Fri, Nov 9, 2012 at 2:25 PM, Nicolas Goaziou wrote:
> Hello,
>
> Takafumi Arakaki writes:
>
>> Do you know if it is fixed in both master and maint, or only in
>> master?
>
> I don't know. If it's fixed a
I am not familiar with org-mode test suite but I can try. Could you
tell me where I can find similar test cases which creates archive
entries?
---
Takafumi
On Fri, Nov 9, 2012 at 9:57 AM, Nicolas Goaziou wrote:
> Hello,
>
> Takafumi Arakaki writes:
>
>> Currently info
Hi,
Thanks for the reply.
Do you know if it is fixed in both master and maint, or only in master?
---
Takafumi
On Fri, Nov 9, 2012 at 9:58 AM, Nicolas Goaziou wrote:
> Hello,
>
> Takafumi Arakaki writes:
>
>> I have a trouble with org-columns-edit-value; updating prop
I have a trouble with org-columns-edit-value; updating property using
this command breaks property formatting.
If I update MyProp_B in,
:PROPERTIES:
:MyProp_A: a
:MyProp_B: b
:END:
I end up with:
:PROPERTIES:
:MyProp_A: :MyProp_B: x a
:END:
I found that (match-beginning
Currently information about tree structure is lost if you have a slash
in node headings. This patch fixes the problem by escaping slashes in
headings before concatenating them.
Takafumi
archive_olpath.patch
Description: Binary data
Hi Bastien,
Thanks. I will bundle my version of the function in my module while
watching development of org-src.el. I will report again if I find
something.
Takafumi
On Fri, Sep 28, 2012 at 8:53 AM, Bastien wrote:
> Hi Takafumi,
>
> Takafumi Arakaki writes:
>
>> I
Hi,
I am trying to use org-src.el bundled in org-mode to support syntax
highlighgint for multiple languages in my IPython notebook client in
Emacs (EIN) [1]. It works very well but I need to patch (please see the
attached file) it to use. The problem is that fontification is gone when I
edit the
Hi, Bastien
Thanks for the patch and I am sorry for this late reply (especially
because I pushed maintainers to review my patch before...).
Anyway, I tried the head of master
(580add2f4148fea949a4db5550577911ee6d756e) and it works fine for me.
But I couldn't reproduce this behavior:
> Note that
No comments? No one wants to have "+3h" in SCHEDULED?
--
Takafumi
reate another patch to
add the constant, please give me a name of the constant. How should
we call "dwmy"? "Time unit chars" or something like that? If the
current patch is acceptable, it is fine for me. Maybe you want to introduce
some constants afterward.
Best,
Takafumi
Hi Bernt,
> My recipe clears the list each time the agenda is generated. I only use
> appt for org-mode appointments so clearing the list works great for me.
Sorry I missed (setq appt-time-msg-list nil) in your setup code. This
is exactly what happens when you pass non-nil for REFRESH argument
Hi Bernt,
Thanks for your setup recipe. However, I noticed I failed to explain
what I meant; the old entry remains in appt-time-msg-list even if you
call org-agenda-to-appt.
So, the procedure to reproduce my problem is the following:
1. Add the following in the agenda file
* TODO test
SCHEDUL
I am using org-agenda-to-appt and I noticed a bug.
1. Add the following in the agenda file
* TODO test
SCHEDULED: <2012-01-14 Sat 12:00>
2. Call org-agenda-to-appt
3. Change the SCHEDULED time-stamp in the entry like this
* TODO test
SCHEDULED: <2012-01-14 Sat 12:00>
4. appt-time-msg-lis
17 matches
Mail list logo