similar to: Tabs in R source code

>From 1da1502b33d50bc0614a20bc217876fcb8f05d39 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at vv.meyering.net.meyering.net> Date: Thu, 24 Sep 2009 09:24:55 +0200 Subject: [PATCH libguestfs] maint: use spaces, not TABs for indentation "make syntax-check" was failing. This fixes it. * HACKING: Indent with spaces, not TABs. * configure.ac: Likewise. *

Debian bug 812166[0] reported this build failure due to Wmisleading-indentation with gcc-6: non-fatal.c: In function 'init_nonfatal_mce_checker': non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] switch (c->x86_vendor) { ^~~~~~ non-fatal.c:97:5: note: ...this 'if' clause, but it is not if (

I've made some local commits that introduce TABs as indentation, and thus provoke a "make syntax-check" failure. This would have prevented it: >From 4740b66adc5985d9a72a7648aa60c5389ffc31af Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Tue, 11 Aug 2009 09:53:16 +0200 Subject: [PATCH libguestfs] doc: improve emacs snippets * HACKING: Make (setq

this is semi-off topic but still related to ror. i had a problem with testing my depot program (which i follow the tutorial in agile web development book). it took me many hours to solved the problem. all the while i thought i was using spaces inside the test/fixtures/products.yml programmer_book: id: 1 title: Pragmatic Programmer description: Best book

Hi Folks -- There is a mix of tabs and spaces in the .py files in xen-unstable. For example: tools/python/xen/xm/create.py line 682 is indented with a mix of tabs and spaces while the surrounding lines use only spaces. Grep''ing for \t in *.py yields many hits. This is changing the apparent indentation (for me anyway) and thus apparent intent in the code. Being a python newb, I

hello, while investigating xm/main.py, i found that it is mixed with tabs and whitespaces. that is annoying and may get us misleaded when reading code. looks like that the conventional coding style of Python (and also C?) in Xen is to use (4) whitespaces instead of tabs? could anybody confirm this? i searched in all tree and found bunch of files like this. if nobody complains, i will catch them

Hi, I was building LLVM with gcc 6.1.1 recently and it was spitting out some warnings relating to misleading indention that caught my eye. This wasn't a fresh build so I may have missed some. I've CC'ed the authors of the potentially misleading lines so they can decide what do about the warnings (if anything). I'm wondering if clang-format is making some inappropriate choices

Maybe this has been reported before, but I can't find it in the archives. A code block immediately following an ordered or unordered list breaks both the list and the code block. Badly. Tab or spaces for the block don't matter, legal indentation variants of the list don't matter. Tried a bunch of casual workarounds, extra newlines, etc., but no joy. Needs explicit

On Friday, 2 November 2018 16:05:04 CET Richard W.M. Jones wrote: > diff --git a/common/utils/libxml2-writer-macros.h b/common/utils/libxml2-writer-macros.h > index d74dcd465..a99b245bb 100644 > --- a/common/utils/libxml2-writer-macros.h > +++ b/common/utils/libxml2-writer-macros.h > @@ -86,7 +86,7 @@ > * > * which produces C<<< <name>text</name>

# HG changeset patch # User Hollis Blanchard <hollisb@us.ibm.com> # Date 1158780052 18000 # Node ID f7d90f962967a5a94fce0c04f8fcac449f36344f # Parent 041be3f6b38e05f904d240630c18cadb1259317b [XEND] Remove hard tabs. Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com> diff -r 041be3f6b38e -r f7d90f962967 tools/python/xen/xend/XendDomainInfo.py ---

> +int mmu_interval_notifier_insert(struct mmu_interval_notifier *mni, > + struct mm_struct *mm, unsigned long start, > + unsigned long length, > + const struct mmu_interval_notifier_ops *ops); > +int mmu_interval_notifier_insert_locked( > + struct mmu_interval_notifier *mni, struct mm_struct *mm, > + unsigned long start, unsigned long length, > + const struct

Coming out of a long (but definately needed) silence for a moment: A few things for vorbis-tools, since I no longer have CVS access (I think I just misplaced that key): 1. Before anything, put oggchain out of its misery. Please. It's a pile of junk that should have never been committed. Any smidgen of usefulness from it belongs in ogginfo anyway (and it's already there). 2. ./autogen.sh

On Thu, Nov 27, 2008 at 4:28 PM, Aslak Helles?y <aslak.hellesoy at gmail.com>wrote: > When (if) this thread ends, let''s start a discussion about indentation > conventions! > Oh... let the pleasure be mine!... and why wait? _EVERYONE_ knows that the only way to indent ruby code is 2 plain spaces. Tabs are known to be the source of all evil and 4 spaces obviously wastes

Howdy, The following bug report was sent to the Debian BTS. Is there a way to have a code block immediately follow an unordered list? ----- Forwarded message from Joey Hess <joeyh at debian.org> ----- Consider this markdown: * bla * bla2 this should be treated as code block and it is not ... but if bullets are not above this, it works If the first code block is indented with

I run test: test:units lass ProductTest < ActiveSupport::TestCase test "product attributes not be empty" do product = Product.new assert product.invalid? assert product.errors[:title].any? assert product.errors[:description].any? assert product.errors[:price].any? assert product.errors[:image_url].any? end test "price musst be

Package: xen Version: 4.6.0-1 Severity: important User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in

Dear developers, I would like to make the following additions to the section on coding style to developers.txt. Any objections / comments ? -- Peter Index: docs/developers.txt =================================================================== --- docs/developers.txt (revision 799) +++ docs/developers.txt (working copy) @@ -154,6 +154,10 @@ off the right margin of the screen, expect them to

Personally, I favor "always use braces" because it helps readability for me. The compiler may be good at flagging misleading indentation, but my visual processing system is terrible at it, especially since we use a measly two spaces for indentation. And we grant indentation exceptions for--among other things--case labels in switches. When some nested statements have braces and others

On 2/19/20 7:56 PM, Jason Wang wrote: > diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig > index 9c4fdb64d9ac..0df3676b0f4f 100644 > --- a/drivers/virtio/Kconfig > +++ b/drivers/virtio/Kconfig > @@ -43,6 +43,19 @@ config VIRTIO_PCI_LEGACY > > If unsure, say Y. > > +config VIRTIO_VDPA > + tristate "vDPA driver for virtio devices" > +

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 7759 > Date: 2007-02-26 18:38:13 +0000 (Mon, 26 Feb 2007) > > Log message (3 lines): > tests/harness/backendmanager.cc: Indent with tabs not spaces. Hmm - this space thing is getting silly - I have my editor set to not expand tabs, but spaces crept in because I