Hello,
Sebastien Vauban
writes:
> I just ran `org-test-run-all-tests' in my active WinNT Emacs session
> (with Org-mode release_8.3beta-677-g0497e3), and was surprised by the
> high number of failures:
You probably heavily customized Org, and many tests expect default
values for defcustoms to
Hello,
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> I just ran `org-test-run-all-tests' in my active WinNT Emacs session
>> (with Org-mode release_8.3beta-677-g0497e3), and was surprised by the
>> high number of failures:
>
> You probably heavily customized Org
For sure ;-)
> and many
Sebastien Vauban wrote:
> Nicolas Goaziou wrote:
>> Sebastien Vauban writes:
>>
>>> I just ran `org-test-run-all-tests' in my active WinNT Emacs session
>>> (with Org-mode release_8.3beta-677-g0497e3), and was surprised by
>>> the high number of failures:
>>
>> You probably heavily customized Org
>
On Tue, Dec 23, 2014 at 5:34 PM, Gary Oberbrunner
wrote:
> If you try to export this document:
>
> #+BEGIN_SRC sql :exports both
> select 1 limit 0;
> #+END_SRC
>
> It fails to export with an error in *Messages*:
> user-error: Empty table - created default table
> It also stops processing the d
On Tue, Dec 23, 2014 at 6:14 PM, Trevor Murphy
wrote:
>
> So, yeah. Do others use this `pre-scheduled' workflow for repeating
> deadlines? If so, is there an obvious solution to this little nuisance
> that I'm not seeing?
>
>
I do use this style of workflow. But, where I have repeating tasks th
Sebastien Vauban
writes:
> Or even more sense: calling `org-babel-execute-maybe' instead?
I think it would be better, yes. There is no point in testing
`org-ctrl-c-ctrl-c' in "test-ob.el".
Regards,
Hi,
Nicolas Goaziou writes:
> I think you can push once the issues above are fixed. Thank you for the
> work.
Pushed!
> However, this raises a question: why are we modifying definition at all?
> We are only interested in its new label, which we can get without
> modifying buffer (i.e. if defin
Hi,
Nicolas Goaziou writes:
> You can push the patch once this is fixed.
Pushed. See general comments in the other mail.
One funny thing I observed was that the following test fails, but only
when run via "make test", not from e.g. my "own" Emacs or emacs -q and
emacs -q -nw.
(should
Hi,
Rasmus writes:
> Please let me know if I did any git mistakes. Somehow the time got skewed
> up and it's behind some of your commits in cgit. . .
Hmm, inspecting cgit I see that one of those persky merge messages got up
there even though it wasn't in my local git log before pushing. Sorry
Hello,
Rasmus writes:
> Hmm, inspecting cgit I see that one of those persky merge messages got up
> there even though it wasn't in my local git log before pushing.
> Sorry!
No worries, this is not a problem.
> What is my mistake:
>
> - I wrote the patch locally in a branch called include.
> -
Hello,
Rasmus writes:
> Pushed. See general comments in the other mail.
Thank you.
> One funny thing I observed was that the following test fails, but only
> when run via "make test", not from e.g. my "own" Emacs or emacs -q and
> emacs -q -nw.
I don't see any failing test.
> When running t
Hi,
Nicolas Goaziou writes:
>> When running through "make test" (org-current-level) evaluate to one
>> (before expansion) even when narrowed (should be nil).
>
> Why? `org-current-level' ignores narrowing.
Perhaps something changed recently then. In the version I was testing
with,
(with-temp-
Nicolas Goaziou writes:
>> One funny thing I observed was that the following test fails, but only
>> when run via "make test", not from e.g. my "own" Emacs or emacs -q and
>> emacs -q -nw.
>
> I don't see any failing test.
When I use something like the attached patch, "make test" goes from
passi
I don't want to use <>. Because I typically use to set the date
when I took the note. The date [], I would like to appear in the more
granular view that the key "l", in the calendar buffer, gives you.
I am trying to figure out how to configure a timeline agenda view that
would show only state changes, rather than SCHEDULED or DEADLINE entries. I
customized the "Org Agenda Log Mode Items:" entry have only the "state"
checkbox on, and "closed" and "clock" are off, and that seems to imply that
only
Hello Rasmus.
I was to learn emacs lisp and I figured one of the ways to do it is to
read someone else's commit.
Can you please tell me what feature is your branch implementing?
Thanks in advance for your time and kind concern.
Jenia.
I think it should be another version of the logging view that shows the
most recent notes.
So if I have
* TODO Another "loggin" view in the agenda
- Note taken on [2014-12-25 Thu 01:48] \\
Right now, this will not appear in the agenda
That node should appear in the new logging view.
R
jenia.iv...@gmail.com (jenia.ivlev) writes:
> I think it should be another version of the logging view that shows the
> most recent notes.
>
> So if I have
>
> * TODO Another "loggin" view in the agenda
> - Note taken on [2014-12-25 Thu 01:48] \\
> Right now, this will not appear in the
18 matches
Mail list logo
