Hi Chuck,
"Charles C. Berry" writes:
> On Tue, 19 Jan 2016, Andreas Leha wrote:
>
>> Hi Chuck,
>>
>
> [snip]
>
>> I've tested your patch and it seems to work. But it does seem to need
>> an analogous change in org-babel-R-evaluate-session to also cure blocks
>> with ':session'.
>>
>
> Correct. I
On Tue, 19 Jan 2016, Andreas Leha wrote:
Hi Chuck,
[snip]
I've tested your patch and it seems to work. But it does seem to need
an analogous change in org-babel-R-evaluate-session to also cure blocks
with ':session'.
Correct. I committed a patch like this and added a test
Thanks,
Chuc
Thank you for sharing your solution.
My current solution: avoid the issue entirely and don't use Unicode in
your source code, use pretty-mode instead:
https://github.com/akatov/pretty-mode
A future option: switch from PDFLaTeX to XeLaTeX of LuaLaTeX.
Both are great. The latter is ideal, and does
Hello, I'm having trouble understanding in which directory to download the
cdlatex.el script that Mr. Dominik wrote. I'm on Windows 7, emacs 24, my AUCTEX
version is 11.88 and I also have Org-mode 8.2 and yasnippet installed.
When I give the command M-x org-cdlatex-mode, Emacs responds "Cannot op
Rasmus writes:
> Arun Isaac writes:
>
>> How long does FSF copyright assignment typically take? I sent a request
>> around 2 weeks ago (on December 26), but haven't received a reply yet.
>>
>> Does it usually take this long? Should I resend my copyright
>> assignment request?
>
> Are you talking
Nick Dokos writes:
> Eric S Fraga writes:
>
> You are missing a quote:
>
> #+TBLFM: $1='(identity remote(2016-01-19-srctbl,@@#$1))
>
> works for me.
>
> Org-mode version 8.3.3 (release_8.3.3-456-g164555)
>
> --
> Nick
Wow,
that was an eye opener for me, first it lets me use/refer to german
u
Hi
org-resolve-clock loops over all open org buffers for detecting open
clocks (using function org-files-list). Is this really intended? I think
it should just loop over the org-agenda-files.
I was working on an extension for clocking and was recording my testing
results
into a separate org file.
Hi Kyle,
Kyle Meyer writes:
>> I just have one concern, which is pretty theoretical. Isn’t it bad to
>> define the alias to be font-lock-ensure since this is an existing function
>> and people would have clear expectations of what they are calling? I
>> realize that there’s no Emacs-25 that wi
Hi Karl
On Tue, Jan 19, 2016 at 4:29 PM, Karl Voit wrote:
> I never understood the @@#-syntax anyway. On [1] I referenced to [2].
Please see the Org manual for @# and $#. Thus @@#$1 is substituted
with @1$1, @2$1, @3$1 etc. depending on the row it is evaluated on.
@1$$# becomes @1$1, @1$2 etc.
Kyle Meyer writes:
[...]
> However, it's easy enough to switch to using an org-font-lock-ensure
> variant that avoids these issues, so I will do that (in an updated
> patch and on Org's maint).
I've attached updated patches against emacs-25. If these are applied to
the Emacs repo, I'll backpor
Eric S Fraga writes:
> On Tuesday, 19 Jan 2016 at 14:10, Karl Voit wrote:
>> Hi!
>>
>> Either I found a bug when referring to other table rows or I don't
>> understand the behavior of following example tables. My expectation
>> was that the first column of the second table is exactly the same as
Karl Voit writes:
> #+NAME: 2016-01-19-srctbl
> | Testdata |
> |--|
> | foobar |
> | fooübar |
> | fooßbar |
> | 1er |
> | 23,42|
> | 23.42|
>
> | Result | Expected Result | Comparison |
> |--+-+|
> | foobar | foobar
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
Rasmus writes:
> Kyle Meyer writes:
[...]
>> The first patch replaces the font-lock-ensure compatibility alias from
>> 6711a21f1 with the one currently used in the Org repo (from commit
>> e6883dd03). The new alias is limited to being called with no
>> arguments, but, at the moment, no Org co
Hi Eric,
* Eric S Fraga wrote:
> On Tuesday, 19 Jan 2016 at 14:10, Karl Voit wrote:
>>
>> #+NAME: 2016-01-19-srctbl
>> | Testdata |
>> |--|
>> | foobar |
>> | fooübar |
>> | fooßbar |
>> | 1er |
>> | 23,42|
>> | 23.42|
>>
>> | Result | Expected Result | Comparison |
Hi Chuck,
Thanks for following that up. And sorry for the long delay.
"Charles C. Berry" writes:
> On Thu, 17 Dec 2015, Andreas Leha wrote:
>
>> Hi all,
>>
>> I think there is a bug in the handling of results of R src blocks. What
>> is the suggested way to make an R block return a link to a
On Tuesday, 19 Jan 2016 at 14:10, Karl Voit wrote:
> Hi!
>
> Either I found a bug when referring to other table rows or I don't
> understand the behavior of following example tables. My expectation
> was that the first column of the second table is exactly the same as
> the first column of the firs
Hi!
Either I found a bug when referring to other table rows or I don't
understand the behavior of following example tables. My expectation
was that the first column of the second table is exactly the same as
the first column of the first table:
#+NAME: 2016-01-19-srctbl
| Testdata |
|--|
Kyle Meyer writes:
> Kyle Meyer writes:
>> Rasmus writes:
>>
>> [...]
>>
>>> Note, this change only lives it the Emacs version of Org. It was added in
>>> this commit:
>>>
>>>6711a21f1125c0047c56eb266eb374c1ec90a967
>
> [...]
>
>>
>> This commit was backported in Org commit d81e6b5, an
I found ob-lisp.el use SLIME by default to evaluate lisp code. I want to
use SLY to evaluate lisp code. How to change it? I found the file ob-lisp.el
is short. I tried to change slime to sly.
But it is not customizable. I hope to define a defcustom for it. So that
user can customize it. But I don'
Hi Karl,
> * Marco Wahl wrote:
>>
>> Further I think you can improve Org's reliability (and your perception
>> on it) by investing more energy into Org. Obviously you already do
>> invest energy into Org as your contributions on this list show. You
>> cold go ahead and start reading Org's code,
Kyle Meyer writes:
> I've attached two patches against emacs-25 that would get the Org and
> Emacs repos in similar states wrt font-lock-ensure.
Thanks Kyle.
> The first patch replaces the font-lock-ensure compatibility alias from
> 6711a21f1 with the one currently used in the Org repo (from co
Hello, I just want to let you know that org-mode is currently
being discussed on HN
https://news.ycombinator.com/item?id=10925655
23 matches
Mail list logo