similar to: PDF generation issue from manual page

(Belated) thanks for the confirmation, Ista. I just reported this issue on the R bug tracker: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17412 Best regards, - Mikko -----Alkuper?inen viesti----- L?hett?j?: Ista Zahn [mailto:istazahn at gmail.com] L?hetetty: 7. helmikuuta 2018 17:05 Vastaanottaja: Korpela Mikko (MML) Kopio: r-devel at r-project.org Aihe: Re: [Rd] Possible bug in

On 2019-08-09 14:27, neonira Arinoem wrote: > I do not follow you Gabriel. Package name must not use digit numbers. > Tarbal will use them, taken from the DESCRIPTION file, version field. > > That's why I consider the weird case name you presented as irrelevant, > and > not to be considered. ggplot2 ? Numbers are allowed in package names right now. > Le ven. 9 ao?t

On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem <neonira at gmail.com> wrote: > Won't it be better to have a convention that allows lowercase, dash, > underscore and dot as only valid characters for new package names and keep > the ancient format validation scheme for older package names? > Validation isn't the only thing we need to do wrt package names. we also need to

> IIRC the client should contact the PDC (domain<0x1b>). But can you > check the logs and see if the clients are trying to change it on > domain<0x1c> (any DC)? Thanks. Can you give me any hints on how to find such information in the log files? My log level is 5, and I can find some password change messages in the logs, but I don't know how to check if they are looking

Creeping code complexity ... I like to think that the cuteR names will have a Darwinian disadvantage in the long run. FWIW Hadley Wickham argues (rightly, I think) against mixed-case names: http://r-pkgs.had.co.nz/package.html#naming. I too am guilty of picking mixed-case package names in the past. Extra credit if the package name and the standard function have different cases! e.g.

I do not follow you Gabriel. Package name must not use digit numbers. Tarbal will use them, taken from the DESCRIPTION file, version field. That's why I consider the weird case name you presented as irrelevant, and not to be considered. Le ven. 9 ao?t 2019 ? 20:41, Gabriel Becker <gabembecker at gmail.com> a ?crit : > > > On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem

Naming policies are always tricky. The one proposed by Hadley, as the one proposed by Google, are usable but not optimal according to most common needs, that are 1. Name a package 2. Name a class 3. Name a function 4. Name a parameter of a function 5. Name a variable My approach is the following 1. Package names should be made of lowercase characters, dash, dot and underscore 2. Class names

Hello Just wondering what is the best way to manage unix signal in R? Though I dug up the R documentation, I haven't found any single relevant example. I could wrap C/C++ unix signal management using RCPP of course. Prior doing so, I wish to be sure that there exist no other available alternative, already implemented and tested. Let me know. Best. Neonira [[alternative HTML version

Hi I have 1800 response variables to regress on two factors (latitude and age), what is the script to run all response variables at once instead of writing 1800 models? Thanks R. ________________________________________ L?hett?j?: r-help-bounces at r-project.org [r-help-bounces at r-project.org] k&#228;ytt&#228;j&#228;n Dennis Murphy [djmuser at gmail.com] puolesta L?hetetty: 25.

It seems after checking the code that global ACL file functionality was changed at 2.2.14 so that only 1 rule is used, not multiple rules. This is not documented or said anywhere into change logs. Br, Ova -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Ovidiu Moldovan Sent: 10. helmikuuta 2015 10:26 To: dovecot at dovecot.org Subject: Dovecot 2.2.15

Good evening R devel mailing list. Just wonder if there is a way to ask for an evolution of the R language. In affirmative case, let me know. I use R for now many years, and still like it very much. It evolves quite smoothly and improves well. Nevertheless, there is one topic that I still miss in R language. It is pure native R annotation, I mean ? la java. I wish to have an @ operator

Won't it be better to have a convention that allows lowercase, dash, underscore and dot as only valid characters for new package names and keep the ancient format validation scheme for older package names? This could be implemented by a single function, taking a strictNaming_b_1 parameter which defaults to true. Easy to use, and compliance results will vary according to the parameter value,

All, I'm trying to migrate to samba3 from nt4. Unsuccesfully so far :-(. Instructions are from idealx how-to v1.6. Enviroment is RHFC2/Samba 3.0.3-5/OpenLDAP 2.1.29 Membership to the domain is ok ---------------- # net rpc testjoin Join to 'NT-DOM' is OK ---------------- The next step would be vampire but it fails with reference to smbtest2-domain. I can't figure out wherefrom

Hello, We have upgraded from Dovecot 2.2.13 to 2.2.15 and we are using global ACL file. The content of the ACL file is as following: * owner r INBOX owner lrwstipekxa INBOX/* owner lrwstipekxa user owner rwstipekxa user/* owner rwstipekxa This worked fine but after update any user cannot see any folders from under the INBOX, also they cannot create any new folders. Error into the logs are

I am going to present Linux to my ham radio club at some point in the next few months, and wanted to collect info on ham radio software, including options for echolink. Our repeater has an echolink connection, thus if I present the software available for it, it might perk up people's interests more. It would also be very helpful if the echlink applications offered proxy/firewall options

I've recently switched from Courier-imap to dovecot and I'm impressed with it's speed and reliability. However, my index file gets regularly corrupted: Feb 8 21:23:16 hive imap(hart): Corrupted index file /home/hart/Maildir/.INBOX/.imap.index: index.next_uid (129) > uid_rec.uid (128) dovecot version: 0.99.13-3 Debian sid) I use dovecot in combination with mutt, procmail and

Thank you for the introduction to these recent changes, Martin. I think this was the second time I ran "make check" on that platform (Raspberry Pi 32-bit), and the first time (some months ago) it worked fine. So, that makes it kind of "suddenly", although I must say that my use of "make check" is very irregular. I compared code before and after the split you are

@steve Seek for online document named "writing R extensions" chapter 2. It tells how to describe a list structure using item markup for R documentation files, if indeed this matches your search, thing I am not sure. Something that looks like... value{ The \\code{list} owns following names \\item{alpha}{double vector} \\item{beta}{integer vector} \\item{delta}{raw vector} } Best Le

Are there technical reasons that package names cannot be snake case? This seems to be enforced by `.standard_regexps()$valid_package_name` which currently returns "[[:alpha:]][[:alnum:].]*[[:alnum:]]" Is there any technical reason this couldn't be altered to accept `_` as well, e.g. "[[:alpha:]][[:alnum:]._]*[[:alnum:]]" I realize that historically `_` has not

Hi list members, just tried to get some old records out of my known_hosts, which is 'HashKnownHosts yes'. Is there a way to unhash host names and/or IPs? Google tells about, how to add hosts, but not the opposite, may be I miss some thing. Is this does not work at all, is there a best practice for cleaning old hosts and keys out? Thanks, Martin! -- Martin GnuPG Key Fingerprint, KeyID