search for: l507

...sn't really need or want it. It's also not great from a build hygiene perspective, as LLVM globally sets some flags and subprojects pick them up, when they don't really mean to. For example, see this workaround: https://github.com/llvm/llvm-project/blob/master/libcxx/CMakeLists.txt#L503-L507 <https://github.com/llvm/llvm-project/blob/master/libcxx/CMakeLists.txt#L503-L507>, where we need to account for some flags that might have been set globally by LLVM. I'm not sure about other projects, however this is quite problematic for projects part of the C++ runtime (libc++/libc++a...

On 09/12/2014, 10:36 PM, Yihui Xie wrote: > I took a look at the R source and I realized that the encoding was > actually never passed to the vignette engine: > https://github.com/wch/r-source/blob/e721ef5f4/src/library/tools/R/Vignettes.R#L507 > Apparently only the file and quiet arguments are passed to the > vignette engine. Did I miss anything? I think it's actually a little messier than that: sometimes the encoding is passed (e.g. by tools:::.run_one_vignette, used in R CMD check), but not always. Here's what I think...

...il.com> wrote: >> On 09/12/2014, 10:36 PM, Yihui Xie wrote: >>> I took a look at the R source and I realized that the encoding was >>> actually never passed to the vignette engine: >>> https://github.com/wch/r-source/blob/e721ef5f4/src/library/tools/R/Vignettes.R#L507 >>> Apparently only the file and quiet arguments are passed to the >>> vignette engine. Did I miss anything? >> >> I think it's actually a little messier than that: sometimes the >> encoding is passed (e.g. by tools:::.run_one_vignette, used in R CMD >&gt...

...sn't really need or want it. It's also not great from a build hygiene perspective, as LLVM globally sets some flags and subprojects pick them up, when they don't really mean to. For example, see this workaround: https://github.com/llvm/llvm-project/blob/master/libcxx/CMakeLists.txt#L503-L507, where we need to account for some flags that might have been set globally by LLVM. >> >> I'm not sure about other projects, however this is quite problematic for projects part of the C++ runtime (libc++/libc++abi/libunwind). Indeed, we often try to build those projects targetting n...

On 09/12/2014, 4:38 PM, ONKELINX, Thierry wrote: > Dear Yihui, > > I have created a reproducible example at https://github.com/ThierryO/utf8vignette > > The \usepackage{} line is needed, otherwise R CMD check --as-cran will give a warning. > %\VignetteEncoding{UTF-8} did not solve the problem. I've just taken a look at the sources, and that's only in R-devel, it never

...g fuse (ie. using the API directly) then a workaround would be to look at how our visitor code works: https://github.com/libguestfs/libguestfs/blob/master/common/visit/visit.c#L70 where it only uses APIs which are unlimited, eg: https://github.com/libguestfs/libguestfs/blob/master/lib/file.c#L507 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests....

I took a look at the R source and I realized that the encoding was actually never passed to the vignette engine: https://github.com/wch/r-source/blob/e721ef5f4/src/library/tools/R/Vignettes.R#L507 Apparently only the file and quiet arguments are passed to the vignette engine. Did I miss anything? To Thierry: I explicitly asked for library(rmarkdown);sessionInfo(), but you only told me the version of rmarkdown, which is not the only thing I was asking for. It is extremely important in this c...

...ch.duncan at gmail.com> wrote: > On 09/12/2014, 10:36 PM, Yihui Xie wrote: >> I took a look at the R source and I realized that the encoding was >> actually never passed to the vignette engine: >> https://github.com/wch/r-source/blob/e721ef5f4/src/library/tools/R/Vignettes.R#L507 >> Apparently only the file and quiet arguments are passed to the >> vignette engine. Did I miss anything? > > I think it's actually a little messier than that: sometimes the > encoding is passed (e.g. by tools:::.run_one_vignette, used in R CMD > check), but not always...