search for: metachars

Displaying 10 results from an estimated 10 matches for "metachars".

2014 Jul 08
2
[Bug 2253] New: No "$@"-like SSH_ORIGINAL_COMMAND leads to escaping, arg-sep and metachar issues
...In a normal shell, one uses "$@", which is the argument-separation-and-metachar aware version of "$*". OpenSSH lacks any equivalent. It needs one to make it possible to use SSH_ORIGINAL_COMMAND securely without making arbitrary rules ("the command may not contain any shell metachars and spaces within arguments are not permitted"). It really needs a $SSH_ESCAPED_ORIGINAL_COMMAND . -- You are receiving this mail because: You are watching the assignee of the bug.
2005 May 12
3
R2.1.0: Bug in list.files
R2.0.1 (MS Windows) > list.files(myloc,"*.zip",full=T) [1] "P:/SARsoftware/Rlibraries/gnlm_0.1.zip" [2] "P:/SARsoftware/Rlibraries/lms2_0.2.zip" R2.1.0: > list.files(myloc,"*.zip",full=T) Error in list.files(path, pattern, all.files, full.names, recursive) : invalid 'pattern' regular expression Bug? or have I missed something
2006 Jan 25
14
[Bug 1094] Local to local copy (and also remote to remote) uses shell expansion twice
http://bugzilla.mindrot.org/show_bug.cgi?id=1094 vapier at gentoo.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vapier at gentoo.org ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the
2005 Apr 26
5
[Bug 2647] --exclude options work from commandline but not in script
...ion is if the single-quotes are being retained in the --exclude values instead of being removed by whatever shell you are using for scripting. So rsync tries to exclude '/proc/' instead of /proc/ In your case, the quotes aren't even needed since you don't have wildcards, shell metachars, or whitespace in those path values. Remove the single-quotes and see if that helps. If it does, then either your shell has a problem or they weren't really single-quotes to begin with. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this...
2019 Feb 08
12
[Bug 2966] New: scp rev 1.202 fix doesn't quite hit the mark
https://bugzilla.mindrot.org/show_bug.cgi?id=2966 Bug ID: 2966 Summary: scp rev 1.202 fix doesn't quite hit the mark Product: Portable OpenSSH Version: 7.9p1 Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P5 Component: scp Assignee: unassigned-bugs at
2019 Feb 08
12
[Bug 2966] New: scp rev 1.202 fix doesn't quite hit the mark
https://bugzilla.mindrot.org/show_bug.cgi?id=2966 Bug ID: 2966 Summary: scp rev 1.202 fix doesn't quite hit the mark Product: Portable OpenSSH Version: 7.9p1 Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P5 Component: scp Assignee: unassigned-bugs at
2017 Jul 26
5
[PATCH 0/2] daemon: Reimplement handling of lvm.conf and filters.
Simplify how we handle lvm.conf.
2014 Aug 26
6
[PATCH 0/3] fix setting lvm filter with newer lvm2
Hi, newer lvm2 releases don't have have uncommented "filter" lines, so the current way to edit lvm.conf doesn't work anymore. Instead, switch to augeas (with a "custom" len) for a cleaner and working way to set the lvm filter. Pino Toscano (3): daemon: add add_sprintf daemon: move AUGEAS_ERROR to the common header daemon: lvm-filter: use augeas for setting the
2005 Apr 18
1
R-2.1.0 is released
...o Readline is not used for tilde expansion when R is run with --no-readline, nor from embedded applications. Then "~name" is no longer expanded, but "~" still is. o The regular expression code is now based on that in glibc 2.3.3. It has stricter conformance to POSIX, so metachars such as { } + * may need to be escaped where before they did not (but could have been). o New encoding 'TeXtext.enc' improves the way postscript() works with Computer Modern fonts. o Replacement in a non-existent column of a data frame tries harder to create a column of the co...
2005 Apr 18
1
R-2.1.0 is released
...o Readline is not used for tilde expansion when R is run with --no-readline, nor from embedded applications. Then "~name" is no longer expanded, but "~" still is. o The regular expression code is now based on that in glibc 2.3.3. It has stricter conformance to POSIX, so metachars such as { } + * may need to be escaped where before they did not (but could have been). o New encoding 'TeXtext.enc' improves the way postscript() works with Computer Modern fonts. o Replacement in a non-existent column of a data frame tries harder to create a column of the co...