I should note that the reason I updated to 2.1.2 was that I upgraded from
Debian Wheezy to Debian Jessie. I bet some package was omitted in the upgrade
process.
On Friday, July 03, 2015 02:01:44 PM John White wrote:
> I recently upgraded to lyx 2.1.2 and now to 2.1.3
>
> The following preambl
On Fri, 3 Jul 2015, Liviu Andronic wrote:
While not developed much these days, Sweave has the merit of being stable
and mostly ironed out; updating your installation is unlikely to break
your documents.
Makes sense.
knitr on the other hand can be a moving target, and not always backwards
c
On Fri, Jul 3, 2015 at 11:30 PM, Rich Shepard wrote:
> On Fri, 3 Jul 2015, Scott Kostyshak wrote:
>
>> I would like to backtrack on this. Let's change "this is not just a
>> personal preference" to "this is just a personal preference". Please
>> google to read about the differences.
>
>
> Scott,
>
On Fri, 3 Jul 2015, Scott Kostyshak wrote:
I would like to backtrack on this. Let's change "this is not just a
personal preference" to "this is just a personal preference". Please
google to read about the differences.
Scott,
Eh, semantics. From what I've read knitr is an augmented Sweave th
On Fri, Jul 3, 2015 at 4:17 AM, Scott Kostyshak wrote:
> On Thu, Jul 02, 2015 at 03:16:05PM -0700, Rich Shepard wrote:
>> On Thu, 2 Jul 2015, Rich Shepard wrote:
>>
>> > How do I tell Sweave that the data frame, b.cast, is in the same directory
>> >as the document?
>>
>> And, ... there is no Swe
On Fri, 3 Jul 2015, Liviu Andronic wrote:
results="hide"
or
echo=FALSE
Liviu,
is your friend, depending on what you want to hide. Using LyX chunks,
you would right-click in Chunk to insert Options argument, and insert
the above in there.
Thank you.
A chunk MUST always be on its own par
I recently upgraded to lyx 2.1.2 and now to 2.1.3
The following preamble worked fine until I did the upgrade to 2.1.2 and 2.1.3
didn't help.
* \usepackage{geometry}
* \newgeometry{top=.85in, bottom=.85in, left=1.30in, right=.65in}
* \setlength{\footskip}{15pt}\usepac
On Fri, Jul 3, 2015 at 10:33 PM, Rich Shepard wrote:
> On Fri, 3 Jul 2015, Liviu Andronic wrote:
>
>> It should. Try to inspect how the function is created, whether the
>> function object exists, if the workspace is loaded as expected, etc.
>
>
> Liviu,
>
> The function exists in the workspace.
On Fri, 3 Jul 2015, Scott Kostyshak wrote:
I strongly agree. It takes a long time to get it right (and "right" is of
course subjective and depends on your workflow). For me, a lot of it has
to do with how long each chunk takes to run. If it is short, then it is in
as a simple chunk. If it is lon
On Fri, 3 Jul 2015, Liviu Andronic wrote:
It should. Try to inspect how the function is created, whether the
function object exists, if the workspace is loaded as expected, etc.
Liviu,
The function exists in the workspace. But, I cannot list the workspace
objects (see attached .pdf).
Als
On Fri, Jul 3, 2015 at 4:09 PM, Liviu Andronic wrote:
> At the same time it can be a pain until you get the hang of it. Right
> now I use a mix where I prepare the data and save it in the workspace,
> load workspace, and run needed code from there. It's not reproducible
> as purists will have it,
On Fri, Jul 3, 2015 at 9:29 PM, Rich Shepard wrote:
> On Fri, 3 Jul 2015, Liviu Andronic wrote:
>
>> If you have the results already ready, then what you generally want to do
>> is: load(".RData")
>
>
> Liviu,
>
> For some reason this does not allow a function (saved in the current
> workspace)
On Fri, 3 Jul 2015, Liviu Andronic wrote:
If you have the results already ready, then what you generally want to do
is: load(".RData")
Liviu,
For some reason this does not allow a function (saved in the current
workspace) to be found and run in a knitr chunk in the lyx document. It does
run
On Fri, Jul 3, 2015 at 2:59 PM, Rich Shepard wrote:
> On Fri, 3 Jul 2015, Scott Kostyshak wrote:
>
>> Let's take this step-by-step. First, I strongly recommend using knitr over
>> Sweave (this is not just a personal preference). If you go to Help >
>> Specific Manuals > Knitr and compile, does it
On Fri, Jul 03, 2015 at 11:37:38AM -0700, Rich Shepard wrote:
> On Fri, 3 Jul 2015, Rich Shepard wrote:
>
> >>Can you please send the document with the above "chunk" in it?
> >
> > Later.
>
> Aha! Found the problem: it was the Sweave-options box at the top of the
> document. Removed that and al
On Fri, 3 Jul 2015, Rich Shepard wrote:
Can you please send the document with the above "chunk" in it?
Later.
Aha! Found the problem: it was the Sweave-options box at the top of the
document. Removed that and all's well. Obviously, knitr does not like that
remnant.
Sorry for the distra
On Fri, 3 Jul 2015, Scott Kostyshak wrote:
On Fri, Jul 03, 2015 at 10:21:27AM -0700, Rich Shepard wrote:
Here's the chunk:
<>=
rnorm(5)
@
Just to be clear, the above is in ERT or in the Chunk inset?
Scott,
Chunk.
Can you please send the document with the above "chunk" in it?
La
On Fri, Jul 03, 2015 at 10:21:27AM -0700, Rich Shepard wrote:
> On Fri, 3 Jul 2015, Scott Kostyshak wrote:
> Here's the chunk:
>
> <>=
> rnorm(5)
> @
Just to be clear, the above is in ERT or in the Chunk inset?
Can you please send the document with the above "chunk" in it?
> and here's the
On Fri, 3 Jul 2015, Scott Kostyshak wrote:
Let's take this step-by-step. First, I strongly recommend using knitr
over Sweave (this is not just a personal preference). If you go to
Help > Specific Manuals > Knitr and compile, does it work?
Scott,
That's certainly a brief manual. :-)
If so,
On Fri, 3 Jul 2015, Liviu Andronic wrote:
It's not very clear what you're trying to do, but you can always
load(".RData")
towards the beginning, and then reuse existing objects from a previously
saved workspace.
Liviu,
Thank you. I'll try that.
Rich
On Fri, Jul 3, 2015 at 5:06 PM, Rich Shepard wrote:
> On Fri, 3 Jul 2015, Jean-Marc Lasgouttes wrote:
>
>> You do not see Chunk in Insert>Custom Inset ? This is weird.
>
>
> Jean-Marc,
>
> There, yes. I was looking in the combobox on the extreme left of the icon
> bar.
>
>> Well, did you add som
On Fri, Jul 3, 2015 at 4:29 PM, Jean-Marc Lasgouttes wrote:
> Le 03/07/2015 15:06, Rich Shepard a écrit :
>>
>> On Fri, 3 Jul 2015, Jean-Marc Lasgouttes wrote:
>>
>>> In 2.1.x, you can use the Chunk custom inset instead of ERT; it
>>> handles transparently the <<>>=...@ syntax.
>>
>>
>> Jean-Marc,
On Fri, 3 Jul 2015, Jean-Marc Lasgouttes wrote:
You do not see Chunk in Insert>Custom Inset ? This is weird.
Jean-Marc,
There, yes. I was looking in the combobox on the extreme left of the icon
bar.
Well, did you add some read.table statement to read it? Without an example
file, it is dif
Le 03/07/2015 15:06, Rich Shepard a écrit :
On Fri, 3 Jul 2015, Jean-Marc Lasgouttes wrote:
In 2.1.x, you can use the Chunk custom inset instead of ERT; it
handles transparently the <<>>=...@ syntax.
Jean-Marc,
I do not see such an environment.
You do not see Chunk in Insert>Custom Inse
On Fri, 3 Jul 2015, Jean-Marc Lasgouttes wrote:
In 2.1.x, you can use the Chunk custom inset instead of ERT; it handles
transparently the <<>>=...@ syntax.
Jean-Marc,
I do not see such an environment.
The document suffix is .lyx. When you want to preview, LyX outputs a .Rnw
file, runs swe
On Fri, Jul 03, 2015 at 05:59:44AM -0700, Rich Shepard wrote:
> On Fri, 3 Jul 2015, Scott Kostyshak wrote:
>
> >Let's take this step-by-step. First, I strongly recommend using knitr over
> >Sweave (this is not just a personal preference). If you go to Help >
> >Specific Manuals > Knitr and compile
On Fri, 3 Jul 2015, Scott Kostyshak wrote:
Let's take this step-by-step. First, I strongly recommend using knitr over
Sweave (this is not just a personal preference). If you go to Help >
Specific Manuals > Knitr and compile, does it work?
Scott,
Interesting. I'll take a little time to try t
Le 02/07/2015 23:25, Rich Shepard a écrit :
1.) When the document refers to the 'Chunk' environment I assume that's
the LyX-code in the menu and is different from Insert -> TeX code (C-l
on my
system) which inserts the infamous ERT box. As a test, I opened a LaTeX
box and
inserted
> str(b
On Thu, Jul 02, 2015 at 03:16:05PM -0700, Rich Shepard wrote:
> On Thu, 2 Jul 2015, Rich Shepard wrote:
>
> > How do I tell Sweave that the data frame, b.cast, is in the same directory
> >as the document?
>
> And, ... there is no Sweave article class; I've been using KOMA-article.
>
> Rich
Hi
On 07/02/2015 09:37 PM, Benedict Holland wrote:
I have been working with biblatex now for over a year. It is
exceptionally complex. It might actually be too complex to automate. I
can't even think up a decent UI to present the hundreds of different
configuration options, and there are probably
30 matches
Mail list logo
