search for: reformatt

...ata \ > + example1 \ > + example2 \ Inconsistent spacing (space-vs-tab doesn't matter in this particular context, but it looks weird to use both) > + " > +plugins="$(echo $lang_plugins $non_lang_plugins | xargs -n1 | sort -u | xargs)" Your use of xargs as a reformatter is interesting ;) Could also be spelled: $(echo $lang_plugins $non_lang_plugins | tr -s ' \t\n' ' ' | sort -u | tr ' ' '\n')" but that's longer to type, so your version is fine. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919...

hi there, trying to follow the steps of Yan & Rossini 2003, I have two problems : first when I 'make CrossCompileBuild', I get : ****************************************************************************** make[1]: Entering directory `/home/ros/RWORK/CROSSSOMP/WinR/R-1.8.0/src/gnuwin32' make -f Makefile.docfiles make[2]: Entering directory

...matter in this particular > context, but it looks weird to use both) Ooops. Wasn't visible in emacs, but I can fix that next time. > >+ " > >+plugins="$(echo $lang_plugins $non_lang_plugins | xargs -n1 | sort -u | xargs)" > > Your use of xargs as a reformatter is interesting ;) Could also be spelled: > > $(echo $lang_plugins $non_lang_plugins | tr -s ' \t\n' ' ' | sort -u > | tr ' ' '\n')" > > but that's longer to type, so your version is fine. This one actually came from stackoverflow: http...

...ndard way of rendering the manual of an R package on CRAN is in the form of a pdf-file. From my perspective, this pdf-file has many drawbacks: - It makes the load (relatively) long - requires at least a plug-in in a browser, - breaks the forward-backward functionality of browser - Does not contain reformattable text so that the monitor space cannot be optimally used when displaying it - Has many page breaks that require space on the monitor and need to be skipped over - Introduces the dependency on latex itself. Therefore, I wanted to ask if the R core team has thought about moving away from pdf-manu...

I've noticed that throughout the code there's quite a variety of formatting styles, especially the size of TAB characters (4 or 8) and size of indents (2 or 4). Is there any agreed standard for new code now? Oh, and whoever wrote the ogg code must get an electric shock every time he hits the spacebar. It's full of spaceless lines like

Combine much common code into tests/functions.sh. Patch 1: Preparation for patch 3. Patch 2: Fix a long-standing bug in how man pages links are generated. Patch 3: Common code for iterating a test function over every plugin. Patch 4: Common code for starting nbdkit in a test and waiting for the PID file to appear. This is the largest and most complex of the patches but is