On 21.01.2023 03:47, Spencer Graves wrote:
On 1/20/23 7:32 PM, Duncan Murdoch wrote:
On 20/01/2023 8:16 p.m., Spencer Graves wrote:
Hello, All:
My attempts to fix this problem exposed what seems to be a
completely
unrelated problem: All five GitHub Actions end now with:
Error:
On 1/20/23 7:32 PM, Duncan Murdoch wrote:
On 20/01/2023 8:16 p.m., Spencer Graves wrote:
Hello, All:
My attempts to fix this problem exposed what seems to be a
completely
unrelated problem: All five GitHub Actions end now with:
Error: package or namespace load failed for ‘fda’ in
On 20/01/2023 8:16 p.m., Spencer Graves wrote:
Hello, All:
My attempts to fix this problem exposed what seems to be a completely
unrelated problem: All five GitHub Actions end now with:
Error: package or namespace load failed for ‘fda’ in namespaceExport(ns,
exports):
undefined
Hello, All:
My attempts to fix this problem exposed what seems to be a completely
unrelated problem: All five GitHub Actions end now with:
Error: package or namespace load failed for ‘fda’ in namespaceExport(ns,
exports):
undefined exports: refinery
The package includes ~man/refi
On 20/01/2023 6:02 p.m., Greg Hunt wrote:
xFEFF isn't a BOM in a UTF-8 file, its not anything. The UTF-8 BOM is a
different sequence of bits. If tools treat it as a BOM, that is arguably a
problem.
You're right. FEFF is the UTF-16 big endian BOM. UTF-16 is a 16 bit
encoding, not at all th
xFEFF isn't a BOM in a UTF-8 file, its not anything. The UTF-8 BOM is a
different sequence of bits. If tools treat it as a BOM, that is arguably a
problem.
On Sat, 21 Jan 2023 at 05:09, Bill Dunlap wrote:
> Setting the locale to "C" (or perhaps some other non-UTF-8 locale) will
> show the BOM
Setting the locale to "C" (or perhaps some other non-UTF-8 locale) will
show the BOM bytes. E.g., on Windows I get:
> Sys.getlocale()
[1] "LC_COLLATE=English_United States.utf8;LC_CTYPE=English_United
States.utf8;LC_MONETARY=English_United
States.utf8;LC_NUMERIC=C;LC_TIME=English_United States.ut
On 20/01/2023 12:15 p.m., Spencer Graves wrote:
Hi, Ivan and Uwe:
Thanks for your suggestions, but I've so far been unable to get them
to work. see below.
On 1/20/23 9:22 AM, Uwe Ligges wrote:
On 20.01.2023 15:53, Ivan Krylov wrote:
В Fri, 20 Jan 2023 08:41:25 -0600
Spencer Gra
Hi, Ivan and Uwe:
Thanks for your suggestions, but I've so far been unable to get them
to work. see below.
On 1/20/23 9:22 AM, Uwe Ligges wrote:
On 20.01.2023 15:53, Ivan Krylov wrote:
В Fri, 20 Jan 2023 08:41:25 -0600
Spencer Graves пишет:
** byte-compile and prepare package for
On 20.01.2023 15:53, Ivan Krylov wrote:
В Fri, 20 Jan 2023 08:41:25 -0600
Spencer Graves пишет:
** byte-compile and prepare package for lazy loading
Error in parse(nsFile, keep.source = FALSE, srcfile = NULL) :
1:1: unexpected input
tools::showNonASCIIfile('https://raw.githubuserconte
В Fri, 20 Jan 2023 08:41:25 -0600
Spencer Graves пишет:
> ** byte-compile and prepare package for lazy loading
> Error in parse(nsFile, keep.source = FALSE, srcfile = NULL) :
>1:1: unexpected input
tools::showNonASCIIfile('https://raw.githubusercontent.com/JamesRamsay5/fda/master/NAMESPACE')
Hello, All:
The NAMESPACE file in
https://github.com/JamesRamsay5/fda
is corrupted. RStudio 2022.12.0+353 (the current version) won't open
it, complaining, "File is binary rather than text so cannot be opened by
the source editor." TextEdit (macOS 11.7.2) opened it as normal, a
12 matches
Mail list logo
