On Sat, Aug 19, 2017 at 6:19 AM Nicolas Goaziou
wrote:
> Fixed. Thank you.
>
Thanks! I confirm the fix.
--
Kaushal Modi
Hello,
William Denton writes:
> I noticed this last week, but I'm on vacation. I'm compiling and running Org
> and Emacs from source, and have been keeping up to date, but the problem's
> been
> there for a while. For Org, I'm on the master branch, not tables, and
>
> "William" == William Denton writes:
William> I was able to use git bisect (on master) to narrow down
William> where the problem started (for me, at least):
William> 27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4 is the first bad
William> commit commit
On Mon, Aug 14, 2017 at 1:55 PM William Denton wrote:
> I was able to use git bisect (on master) to narrow down where the problem
> started (for me, at least):
>
> 27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4 is the first bad commit
> commit 27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4
>
I was able to use git bisect (on master) to narrow down where the problem
started (for me, at least):
27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4 is the first bad commit
commit 27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4
Author: Nicolas Goaziou
Date: Thu Jul 27 15:22:45
I noticed this last week, but I'm on vacation. I'm compiling and running Org
and Emacs from source, and have been keeping up to date, but the problem's been
there for a while. For Org, I'm on the master branch, not tables, and running
"make update" to update.
In the example below, the <40>