Re: [O] capture template and writeroom mode ?

[Bastien]

Hi Jean-Christophe,

Jean-Christophe Helary  writes:

> What would be the best way to have writeroom mode called in one
> given capture template and not the others ?

I would you a (file+)function to get the location:

`(file+function "path/to/file" function-finding-location)'
  A function to find the right location in the file.

`(function function-finding-location)'
  Most general way: write your own function which both visits
  the file and moves point to the right location.

then tell the function to use writeroom-mode.

I've not tested, though.

-- 
 Bastien

Re: [O] Donating money to mobile org.

[Bastien]

"M. P."  writes:

> Hello If I want to donate specifically to mobile org what would I do?

If you are referring to https://mobileorg.github.io, contacting the
authors would be the best way to know.

HTH,

-- 
 Bastien

Re: [O] org babel, ess, R

[Andreas Kiermeier]

>
> Thanks Andreas. I am perhaps being to finicky. The problem with your
> approach is that you would end up permanently losing screen space for the R
> session. I don’t want the R session obstructing my writing when I am not
> working on code blocks. Ideally, the R session should appear only when I am
> editing the code blocks in an edit buffer.
>
> Vikas
>
> ​Fair enough. I guess it comes down to personal preference.​
If I have emacs maximised, I "need" to split the frame into two windows -
otherwise a single window is too wide (and I don't have a wide screen
monitor).
Because I use this set up for running data analyses and writing reports, it
has the benefit that I can refer to output and calculations at any time.
But, each to their own.
Cheers,
AK

Re: [O] org babel, ess, R

[Vikas Rawal]

> 
> for what it's worth, I usually run two windows (in the same frame), 
> side-by-side, with emacs maximised.
> On the left I have my org file and on the right I have an R session, which I 
> start immediately after I open my org file.
> When I use C-c ' on an R source block, the org buffer (on the left) is 
> replaced by by the source code edit buffer - leaving the R-session on the 
> right untouched.
> That way I can either evaluate a whole code block (from org using C-c C-c) or 
> go through the source code line-by-line (using ESS).
> Seems like that's what you want to do, too.
> Anyway, just my two cents worth, in case it helps.

Thanks Andreas. I am perhaps being to finicky. The problem with your approach 
is that you would end up permanently losing screen space for the R session. I 
don’t want the R session obstructing my writing when I am not working on code 
blocks. Ideally, the R session should appear only when I am editing the code 
blocks in an edit buffer.

Vikas

Re: [O] org babel, ess, R

[Andreas Kiermeier]

Hi Vikas,
for what it's worth, I usually run two windows (in the same frame),
side-by-side, with emacs maximised.
On the left I have my org file and on the right I have an R session, which
I start immediately after I open my org file.
When I use C-c ' on an R source block, the org buffer (on the left) is
replaced by by the source code edit buffer - leaving the R-session on the
right untouched.
That way I can either evaluate a whole code block (from org using C-c C-c)
or go through the source code line-by-line (using ESS).
Seems like that's what you want to do, too.
Anyway, just my two cents worth, in case it helps.
Cheers,
AK

On 3 July 2017 at 09:47, Vikas Rawal 
wrote:

> >
> > Vikas Rawal  writes:
> >
> >> Isn’t is what most users need while editing the code block? The
> >> possibility of evaluating the code to test and see what happens?
> >
> >
> > Many languages do not support sessions. So, the only possibility to
> > evaluate the code is to evaluate the code block in the source buffer.
> >
>
> Yes, what I am talking about is relevant only when a session is defined.
> What I would like is that if in a file the session is defined, C-c’ creates
> a window configuration that shows the edit buffer and the session. In
> other cases, the two windows could show the edit buffer and the original
> org buffer.
>
>
> Vikas
>

Re: [O] org babel, ess, R

[Vikas Rawal]

> 
> Vikas Rawal  writes:
> 
>> Isn’t is what most users need while editing the code block? The
>> possibility of evaluating the code to test and see what happens? 
> 
> 
> Many languages do not support sessions. So, the only possibility to
> evaluate the code is to evaluate the code block in the source buffer.
> 

Yes, what I am talking about is relevant only when a session is defined. What I 
would like is that if in a file the session is defined, C-c’ creates
a window configuration that shows the edit buffer and the session. In other 
cases, the two windows could show the edit buffer and the original org buffer.


Vikas

[O] capture template and writeroom mode ?

[Jean-Christophe Helary]

What would be the best way to have writeroom mode called in one given capture 
template and not the others ?

Jean-Christophe 

[O] Donating money to mobile org.

[M. P.]

Hello If I want to donate specifically to mobile org what would I do?

Re: [O] Android sync client

[Pier]

I use termux with emacs and org installed in it.  I use a hosting server
and sync org files to-from there.

Re: [O] Org mode version 9.0.9 (9.0.9-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20170622/); Org lost my state change note during idle clock resolution

[Jorge Morais Neto]

On 1 July 2017 at 13:58, Nicolas Goaziou  wrote:
> Even if the window configuration is lost, I cannot see how the "*Org
> Note*" buffer could be closed. Are you certain it was not accessible
> anymore from the buffer list?
I do not remember and unfortunately I do not have the time to test it
this week.  I intend to test it next week.

Regards

-- 
- I am Brazilian.  I hope my English is correct and I welcome feedback
- Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z
- Free (as in free speech) software for Android: https://f-droid.org/

Re: [O] org babel, ess, R

[Nicolas Goaziou]

Hello,

Vikas Rawal  writes:

> Isn’t is what most users need while editing the code block? The
> possibility of evaluating the code to test and see what happens? 


Many languages do not support sessions. So, the only possibility to
evaluate the code is to evaluate the code block in the source buffer.

Regards,

-- 
Nicolas Goaziou