Yes, absolutely, it's annnoying. This probably is the bug I reported a
day ago.
But in the past I observed this a bit differently:
Your description is correct, but there is/was a workaround: If you go to
x from the line below (i.e. press cursor left from the beginning of the
next line) it doe
Hello
"Stefan-W. Hahn" writes:
> as I observed there is a change in behaviour of org-return from on
>
> commit 4e864643bdb6bba3e000ea51fb746a26e40b1f77
> Author: Nicolas Goaziou
> Date: Sun Oct 18 09:36:15 2015 +0200
>
> for timestamps, date ranges and any link.
>
> The same change of behavio
Hello,
"Stefan-W. Hahn" writes:
> commit 72c3f5e8e55ccab8a9793f729bfbaa89f4fab732
> Author: Nicolas Goaziou
> Date: Wed Oct 28 14:41:31 2015 +0100
>
> org-agenda: Fix `org-agenda-get-scheduled'
>
> * lisp/org-agenda.el (org-agenda-get-scheduled): Rewrite function.
> Comment
Kyle Meyer writes:
> Simon Thum writes:
>
>> I was a bit early; I am getting this error now:
>>
>> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
>> replace-regexp-in-string("[]+\\'" "" nil)
>> (lambda (s) (replace-regexp-in-string "[ ]+\\'" "" s))(nil)
>> mapconc
I guess I'm saying that the whole `org-babel-lob-ingest` into
`org-babel-library-of-babel` exercise should make code ready and available.
Otherwise (especially with the extra `org-babel-lob-ingest` in Local
Variable step I mentioned), what John Kitchin suggested with
`org-babel-load-file` is just a
Lawrence Bottorff writes:
> Yes, I experimented with this too -- and got it to work. But strangely, if
> you leave out the
>
> # eval: (org-babel-lob-ingest "./a.org")
> # eval: (org-babel-lob-ingest "./b.org")
>
> lines and do a regular `org-babel-lob-ingest` (or C-c C-v i) on those
> two fil
Yes, and see my response. Having to explicitly re-do the
`org-babel-lob-ingest` in the Local Variables with an eval tells me org
babel doesn't really know about LOB until my file explicitly tells it.
Doing `org-babel-lob-ingest` outside of the org file (at Emacs startup)
should set something to t a
Yes, I experimented with this too -- and got it to work. But strangely, if
you leave out the
# eval: (org-babel-lob-ingest "./a.org")
# eval: (org-babel-lob-ingest "./b.org")
lines and do a regular `org-babel-lob-ingest` (or C-c C-v i) on those two
files -- *it doesn't work. *Rather bizarre beha
On Oct 30, 2015 09:09, "Christian Moe" wrote:
>
>
> Thomas S. Dye writes:
>
> > Sorry, I forgot to give an example. I use it like this [[sc:ad][AD]].
> >
> > The advantage of a link over a macro is that the link should export
> > correctly to both LaTeX and HTML.
> >
> > If you intend to export t
Lawrence Bottorff writes:
> New thread. Anyway, putting lisp/SLIME aside, I experimented with emacs lisp
> -- and got
> the same results, i.e., no real LOB functionality, despite proper loading. I
> must be doing
> something wrong? I'll describe my process again:
>
> Load a.org and b.org into `
Mehul Sanghvi writes:
> Nicolas,
>
> Thanks for pointing out that the latest version works. I updated
> org-mode and it seems to be working now.
> I wonder what changed to cause it to work.
>
My guess would be
commit b4af3f0852e9705ddbac66d78cd8a508c547be85
Author: Nicolas Goaziou
Date:
Lawrence Bottorff writes:
> I would use local variables for this--something like (untested):
>
> # eval: (org-babel-lob-ingest path/to/your/file)
> # eval: (sbe "my-add")
> # eval: (sbe "multi_x2")
>
> Computer savvy Org moders don't like eval because anything can happ
I think you are mistaken in what you think it does. I am pretty sure what
it does is allow you to call named src-blocks with this syntax:
#+call: some-func-in-lob(args)
It doesn't make the functions in the code blocks necessarily available in
another code block (although through side effects for
Nicolas,
Thanks for pointing out that the latest version works. I updated
org-mode and it seems to be working now.
I wonder what changed to cause it to work.
cheers,
mehul
On Sat, Oct 31, 2015 at 10:57 AM, Mehul Sanghvi
wrote:
> I am currently using:
>
>Org-mode version 8.3.
New thread. Anyway, putting lisp/SLIME aside, I experimented with emacs
lisp -- and got the same results, i.e., no real LOB functionality, despite
proper loading. I must be doing something wrong? I'll describe my process
again:
Load a.org and b.org into `org-babel-library-of-babel` with
`org-babel
I am currently using:
Org-mode version 8.3.2 (release_8.3.2-195-gbf9146
I will try updating and seeing what happens.
On Sat, Oct 31, 2015 at 5:23 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Mehul Sanghvi writes:
>
> > I have the following written in an org file:
> >
> > The =\,= allo
On Friday, 30 Oct 2015 at 16:25, Subhan Michael Tindall wrote:
> I'm a fairly well versed org user for managing projects, on a personal
> level.
> I'm trying to set up some projects that need to have fixed numbers of hours
> from other departments distributed among projects and/or users. In order t
Hi Lawrence,
Lawrence Bottorff writes:
> There are many, many Babel examples, but I can't seem to find this
> functionality: A function in a Lisp code block in one org file is to be
> called from a Lisp code block in another org file. Is this possible? I know
> you can stick stuff into your pers
Hello,
Mehul Sanghvi writes:
> I have the following written in an org file:
>
> The =\,= allows you to put a Lisp expression there and the =#= is
>the /replace-count/. Read /*replace-regexp*/ for more information.
>
> When I render this in HTML I get the following:
>
>The
19 matches
Mail list logo
