On 3/10/20 9:24 PM, Allen Barker wrote:
> On 6/25/19 12:42 PM, Richard Kimberly Heck wrote:
>> Thanks for these ideas. I'm not an R user myself, though, so it would be
>> helpful to me if you could explain what it is you are trying to achieve.
>> It's best when thinking through issues like this one
On 6/25/19 12:42 PM, Richard Kimberly Heck wrote:
Thanks for these ideas. I'm not an R user myself, though, so it would be
helpful to me if you could explain what it is you are trying to achieve.
It's best when thinking through issues like this one to separate the
problem from the solution. What'
On 6/14/19 1:10 PM, Jason Sun wrote:
With the help of the reticulate package and knitr package, we are able to now embed python and R
code in lyx in a reproducible manner. But the problem is that we have to compile the file every time
we need to see the execution result of the python/R code. In
On Tue, Mar 10, 2020 at 10:31:10AM -0400, Scott Kostyshak wrote:
> your questions. I tried to test regarding Pavel's concern, but I don't
> know a situation when the depth changes;
Actually you are likely right. The destruction of depth structure comes
with moving paragraphs lfuns, not outlines-u
On Tue, Mar 10, 2020 at 08:55:06AM +0100, Pavel Sanda wrote:
> On Tue, Mar 10, 2020 at 01:24:31AM -0400, Richard Kimberly Heck wrote:
> > On 3/9/20 9:25 PM, Scott Kostyshak wrote:
> > > Is there a reason to do the following for outline-up and outline-down?
> > >
> > > setCursor(cur, cur.pit(), 0)
On Tue, Mar 10, 2020 at 01:24:31AM -0400, Richard Kimberly Heck wrote:
> On 3/9/20 9:25 PM, Scott Kostyshak wrote:
> > Is there a reason to do the following for outline-up and outline-down?
> >
> > setCursor(cur, cur.pit(), 0);
> >
> > It does not seem to be necessary in my testing, but I'm wonde
Am Mo., 9. März 2020 um 11:54 Uhr schrieb Pavel Sanda :
> By scriptable I meant to have some kind of (shell?) script, which converts
> the downloaded imagemagick to the one which is distributed by us,
> if we make any changes to it. This would have two advatages:
> 1. We are going to update imagem
