similar to: --exclude with whitespace

Full_Name: Bj?rn-Helge Mevik Version: 2.1.0 OS: GNU/Debian 3.0 Linux Submission from: (NULL) (80.111.104.162) In Appendix B R coding standards of the Writing R Extensions manual, Emacs/ESS users are encouraged to use (add-hook 'ess-mode-hook (lambda () (ess-set-style 'C++) ;; [snip] (add-hook 'local-write-file-hooks

Hi, this patch fixes a problem with leading/trailing whitespace matching for FileCheck --strict-whitespace --match-full-lines. Consider a text file: ... $ cat DUMP bla1 bla2 bla3 bla4 bla5 ... with some leading and trailing spaces, made more visible like this: ... $ sed 's/ /_/g' DUMP bla1 bla2 _bla3 bla4_ _bla5_ ... and a FileCheck file CHECK to match DUMP: ... $ cat CHECK //

I'm having difficulty getting rid of extra whitespace above and below an EPS figure. For example, if I generate an output file using these commands: > R.test(output='none') where: R.test <- function(output=NULL) { if (output == 'yes') { ps.options(pointsize=10) postscript('plot.eps', paper='special', horizontal=FALSE, onefile=FALSE,

Please send patches to llvm-commits not llvm-dev. Writing FileCheck tests has pitfalls. A test along these lines: bla0 CHECK:bla1 will actually pass, because the CHECK pattern is also part of the input so it will readily match itself. You want the CHECK lines not to match themselves, which you can easily do by introducing {{}} into the (middle of the) pattern. That is: bla0 CHECK:{{bla1}}

Package: logcheck Version: 1.2.34 Severity: normal the patterns for pure-ftpd in ignore.d.server are not matching a user with a trailing whitespace. here a some examples: Feb 18 13:02:33 web1 pure-ftpd: (stupid-pure-ftpd @84.56.131.73) [NOTICE] /example/example.txt downloaded (5908 bytes, 152196.03KB/sec) Feb 18 13:16:14 web1 pure-ftpd: (stupid-pure-ftpd @84.56.131.73) [INFO] Logout. every

On 14/12/16 18:48, Robinson, Paul wrote: > Please send patches to llvm-commits not llvm-dev. > > Writing FileCheck tests has pitfalls. A test along these lines: > > bla0 > CHECK:bla1 > > will actually pass, because the CHECK pattern is also part of the input > so it will readily match itself. You want the CHECK lines not to match > themselves, which you can easily do

> -----Original Message----- > From: Tom de Vries [mailto:Tom_deVries at mentor.com] > Sent: Thursday, December 15, 2016 2:31 AM > To: Robinson, Paul > Cc: Jonathan Roelofs; llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] [FileCheck] Fix --strict-whitespace --match-full- > lines > > On 14/12/16 18:48, Robinson, Paul wrote: > > Please send patches to

+jyknight, who added --match-full-lines On 12/14/16 5:37 AM, Tom de Vries wrote: > Hi, > > this patch fixes a problem with leading/trailing whitespace matching > for FileCheck --strict-whitespace --match-full-lines. > > The resulting regexp string is '^bla3$' instead of '^ bla3$'. > > The patch fixes this, and makes the behavior match the documentation.

When porting patches from dash git to klibc git, where dash has a different directory structure those switches are handy: Exported with format-patch on dash side and used am as import for klibc side. Signed-off-by: maximilian attems <max at stro.at> --- Documentation/git-am.txt | 5 ++++- git-am.sh | 4 +++- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git

Hi I am sorry if this has been asked before but after searching I haven't been able to find an answer. I have samba installed on a Centos machine and joined a windows active directory. Everything works fine in general except for users who have a whitespace in their password. For example if I have a user called myuser whose password is pass word when I do wbinfo -a myuser%pass word it gives

Dear R-users, I have a large data file that I am trying to read in R where the file has a white space at the begging and at random places. The whitespace is actually NA so I am trying to read the file using scan but with no success!! Please help Here are some example rows from the data file. 1 1 0 0 2 1 1 0 0 2

https://bugzilla.samba.org/show_bug.cgi?id=4371 Summary: unable to rsync filenames with whitespace from remote source Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hello, markdown (Python implementation) seems to render:  to <img src="pfad/und/eine" title="lange/url zum bild.jpg" alt="alternativer text"/> breaking the URL at the whitespace. AFAIK whitespaces are ok in URLs so why is it breaking up the URL here? Thanks, Florian -- I'm using an

On Thu, 21 Apr 2005, Reid Spencer wrote: > Why not put all this into a pre-commit filter in CVS and be done with > it? We'd never be bothered with it again as it would never be committed > again. I'd rather not have CVS commit scripts mucking with the code. If you want to have the nightly tester whine about source code with spaces at the end of lines (like it whines about

It would be nice if R ignored more unicode white space characters. For example, if I have "\u2028" in a command (which I get from a line-break in keynote) I get the following error: > qplot(carat, price, data = diamonds, colour=clarity) Error: unexpected input in "qplot(carat, price, data = diamonds, ?" And occasionally have such problems when copying and pasting from

Dear LLVMers, If you live on the bleeding edge (i.e. CVS version), please read! On Wed, Apr 20, 2005 at 12:12:54PM +0200, Markus F.X.J. Oberhumer wrote: > Do you really want external patches for this ? A simple Perl script > that runs on all *.h and *.cpp files, and a local commit from your > side would be much simpler. I'm in the process of doing just this as we speak. What this

Hello Readers, Is it possible to disallow creation of filenames containing whitespace characters on Samba Shares ? This is causing headaches sometimes on the unix side of life. TIA -- Werner SETI@home workunit: 119 CPU-Time: 8623439.55

Why not put all this into a pre-commit filter in CVS and be done with it? We'd never be bothered with it again as it would never be committed again. Reid. On Thu, 2005-04-21 at 15:11 -0500, Misha Brukman wrote: > Dear LLVMers, > > If you live on the bleeding edge (i.e. CVS version), please read! > > On Wed, Apr 20, 2005 at 12:12:54PM +0200, Markus F.X.J. Oberhumer wrote:

It seems that Dovecot gets confused when presented with a header like: From: someone at somewhere.org i.e. with leading whitespace and no "friendly name" This shows up as ""@MISSING_DOMAIN in clients, such as Pine, that believe what Dovecot tells them rather than parsing the headers themselves (e.g. Thunderbird). Here's a sample IMAP session: xyz FETCH 728 ENVELOPE

Dear All, Yesterday I installed WINE on my Debian GNU/Linux machine. I obtained the program packages from Andreas Schuldei's site, and the winesetuptk package from Ove Kaven's. Although my machine is dual boot, I am also trying out the "WINE without Windows" option, ie by creating a /c directory in the Linux partition. Little apps (Notepad, Minesweeper, calc, puTTY, etc.)