search for: gelineau

...and compliance results will vary according to the parameter value, allowing strict compliance for new package names and lazy compliance for older ones. Doing so allows to enforce a new package name convention while also insuring continuity of compliance for already existing package names. Fabien GELINEAU alias Neonira Le ven. 9 ao?t 2019 ? 18:40, Kevin Wright <kw.stat at gmail.com> a ?crit : > Please, no. I'd also like to disallow uppercase letters in package names. > For instance, the cuteness of using a capital "R" in package names is > outweighed by the annoyance...

...arameter value, allowing strict compliance for new >> package names and lazy compliance for older ones. >> >> Doing so allows to enforce a new package name convention while also >> insuring continuity of compliance for already existing package names. >> >> Fabien GELINEAU alias Neonira >> >> Le ven. 9 ao?t 2019 ? 18:40, Kevin Wright <kw.stat at gmail.com> a ?crit : >> >> > Please, no. I'd also like to disallow uppercase letters in package >> names. >> > For instance, the cuteness of using a capital "R" i...

...be distinguished and distinguish-able immediately, both for humans and code parsers. Could you tell me, who should I get in touch with to share and promote this need, that I believe, could bring a new frontier to R, and could generate a lot of benefits for R users community. Best regards. Fabien GELINEAU, a.k.a Neonira [[alternative HTML version deleted]]

...ary according to the parameter value, allowing strict compliance for new > package names and lazy compliance for older ones. > > Doing so allows to enforce a new package name convention while also > insuring continuity of compliance for already existing package names. > > Fabien GELINEAU alias Neonira > > Le ven. 9 ao?t 2019 ? 18:40, Kevin Wright <kw.stat at gmail.com> a ?crit : > >> Please, no. I'd also like to disallow uppercase letters in package names. >> For instance, the cuteness of using a capital "R" in package names is >> o...

...vary according to the parameter value, allowing strict compliance for new > package names and lazy compliance for older ones. > > Doing so allows to enforce a new package name convention while also > insuring continuity of compliance for already existing package names. > > Fabien GELINEAU alias Neonira > > Le ven. 9 ao?t 2019 ? 18:40, Kevin Wright <kw.stat at gmail.com> a ?crit : > > > Please, no. I'd also like to disallow uppercase letters in package > names. > > For instance, the cuteness of using a capital "R" in package names is >...

...ce for >>> new >>> package names and lazy compliance for older ones. >>> >>> Doing so allows to enforce a new package name convention while also >>> insuring continuity of compliance for already existing package names. >>> >>> Fabien GELINEAU alias Neonira >>> >>> Le ven. 9 ao?t 2019 ? 18:40, Kevin Wright <kw.stat at gmail.com> a ?crit >>> : >>> >>> > Please, no. I'd also like to disallow uppercase letters in package >>> names. >>> > For instance, the cut...

...er value, allowing strict compliance for new > > package names and lazy compliance for older ones. > > > > Doing so allows to enforce a new package name convention while also > > insuring continuity of compliance for already existing package names. > > > > Fabien GELINEAU alias Neonira > > > > Le ven. 9 ao?t 2019 ? 18:40, Kevin Wright <kw.stat at gmail.com> a ?crit : > > > >> Please, no. I'd also like to disallow uppercase letters in package > names. > >> For instance, the cuteness of using a capital "R" in...

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

Hello, I am using samba 2.0.4b on Linux 2.0.36. Since I changed some of the parameters in my smb.conf I have a very strange Problem. Everytime my Samba-Box wins the browselist election process two nmbds are started and my WinXX-Clients do not get access to samba (I could see the server but not access the shares nor login to the domain). smbclient -L server from server works fine. From another