Hi Nicolas,
Nicolas Richard writes:
> Could you review this ? thanks.
Applied, thanks!
--
Bastien
Hello,
Bastien writes:
> Please do
>
> ~$ git fetch --tags
>
> to update all your tags, and make again.
That worked. Thank you.
> Tags are on commits, not on "branches", and commmits can belong to
> multiple branches.
>
> Since the tagged commit is both on the maint and the master branch,
> ma
Nicolas Goaziou writes:
> That is what I don't understand. You added "8.2.5h" to "maint", and
> master wasn't merged into "maint" since then. How can the tag
> propagate to "master"?
It doesn't. But maint is included in master as an ancestor and git
describe uses the most recent tag in common anc
Bastien writes:
> Hi Nicolas,
>
> Nicolas Richard writes:
>
>> OTOH, I find it a bad idea that some arguments are ignored in
>> non-interactive uses, it'd be better to have a function which fully
>> obeys its arguments, and has an interactive spec which sets the
>> argument. If you're interested
Hi Nicolas,
Nicolas Richard writes:
> OTOH, I find it a bad idea that some arguments are ignored in
> non-interactive uses, it'd be better to have a function which fully
> obeys its arguments, and has an interactive spec which sets the
> argument. If you're interested I can do that.
Of course I
Bastien writes:
> Daimrod writes:
>
>> Awww that's tricky, M-x org-version doesn't have the same behavior than
>> M-: (org-version)
>
> That's on purpose: (org-version) is what you want to call in a
> program, hence the short version, while M-x org-version RET is what
> you want to call interact
Nicolas Goaziou writes:
> I always do:
>
> make && org-reload
>
> from Eshell. That doesn't change anything.
Please do
~$ git fetch --tags
to update all your tags, and make again.
>> I always add the release tag on maint, that's where both minor and
>> major releases are made from (expect t
Bastien writes:
> Daimrod writes:
>
>> Awww that's tricky, M-x org-version doesn't have the same behavior than
>> M-: (org-version)
>
> That's on purpose: (org-version) is what you want to call in a
> program, hence the short version, while M-x org-version RET is what
> you want to call interact
Bastien writes:
> Well, make sure you did a ~$ make or ~$ make autoloads so that
> lisp/org-version.el is correct.
I always do:
make && org-reload
from Eshell. That doesn't change anything.
> I always add the release tag on maint, that's where both minor and
> major releases are made from (
Daimrod writes:
> Awww that's tricky, M-x org-version doesn't have the same behavior than
> M-: (org-version)
That's on purpose: (org-version) is what you want to call in a
program, hence the short version, while M-x org-version RET is what
you want to call interactively (hence the longer one.)
Hi Nicolas,
Nicolas Goaziou writes:
> Good question. I have absolutely no clue. OTOH, my tree looks
> up-to-date, and my .git/config reports:
>
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = orgm...@orgmode.org:org-mode.git
>
Daimrod writes:
> Nicolas Goaziou writes:
>
>> Daimrod writes:
>>
>>> I had forgotten to rerun make after I pulled the latest version.
>>> `org-version' now returns "8.2.5h".
>>
>> This is still not right. 8.2.5h refers to "maint" branch, where cache
>> doesn't exist.
>>
>> When I compile the l
Hello,
Bastien writes:
> Mhh... now *I* am confused. The latest release on master is
>
> Org-mode version 8.2.5h (release_8.2.5h-676-gfb8a04)
>
> How can it be 8.2.5e for you?
Good question. I have absolutely no clue. OTOH, my tree looks
up-to-date, and my .git/config reports:
[remo
Bastien writes:
> Hi Nicolas and Greg,
>
> Nicolas Goaziou writes:
>
>> Daimrod writes:
>>
>>> I had forgotten to rerun make after I pulled the latest version.
>>> `org-version' now returns "8.2.5h".
>>
>> This is still not right. 8.2.5h refers to "maint" branch, where cache
>> doesn't exist.
>
Nicolas Goaziou writes:
> Daimrod writes:
>
>> I had forgotten to rerun make after I pulled the latest version.
>> `org-version' now returns "8.2.5h".
>
> This is still not right. 8.2.5h refers to "maint" branch, where cache
> doesn't exist.
>
> When I compile the latest release on "master", I g
Hello Nicolas
On 5 March 2014 09:25, Nicolas Goaziou wrote:
> Daimrod writes:
>
> > I had forgotten to rerun make after I pulled the latest version.
> > `org-version' now returns "8.2.5h".
>
> This is still not right. 8.2.5h refers to "maint" branch, where cache
> doesn't exist.
>
> When I comp
Hi Nicolas and Greg,
Nicolas Goaziou writes:
> Daimrod writes:
>
>> I had forgotten to rerun make after I pulled the latest version.
>> `org-version' now returns "8.2.5h".
>
> This is still not right. 8.2.5h refers to "maint" branch, where cache
> doesn't exist.
I think Greg did C-h v org-vers
Daimrod writes:
> I had forgotten to rerun make after I pulled the latest version.
> `org-version' now returns "8.2.5h".
This is still not right. 8.2.5h refers to "maint" branch, where cache
doesn't exist.
When I compile the latest release on "master", I get:
Org-mode version 8.2.5e (release
Nicolas Goaziou writes:
> Hello,
>
> Daimrod writes:
>
>> I use org-mode version release_8.0.2-101-gce5988 (I follow the git
>> upstream) and I tried it with `org-element-use-cache' set to nil.
>
> There was no `org-element-use-cache' in Org 8.0. Could you update Org
> and try again?
I had forg
Hello,
Daimrod writes:
> I use org-mode version release_8.0.2-101-gce5988 (I follow the git
> upstream) and I tried it with `org-element-use-cache' set to nil.
There was no `org-element-use-cache' in Org 8.0. Could you update Org
and try again?
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> Hello,
>
> Daimrod writes:
>
>> I think that there is a bug in `org-element-context' because it doesn't
>> seem to parse link with spaces consistently.
>>
>> For example:
>>
>> #+BEGIN_EXAMPLE
>> v
>> [[file:test 1 2 3]]
>> ^
>> #+END_EXAMPLE
>>
Hello,
Daimrod writes:
> I think that there is a bug in `org-element-context' because it doesn't
> seem to parse link with spaces consistently.
>
> For example:
>
> #+BEGIN_EXAMPLE
> v
> [[file:test 1 2 3]]
> ^
> #+END_EXAMPLE
>
> If the cursor is before the '1', then `or
Hello,
I think that there is a bug in `org-element-context' because it doesn't
seem to parse link with spaces consistently.
For example:
#+BEGIN_EXAMPLE
v
[[file:test 1 2 3]]
^
#+END_EXAMPLE
If the cursor is before the '1', then `org-element-context' will return:
#+BEGIN_E
23 matches
Mail list logo
