git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: the war on trailing whitespace

From
Llinux@horizon.com <linux@horizon.com>
Date
Feb 28, 2006, 01:07 UTC
Message-ID
<20060228010715.31275.qmail@science.horizon.com>

The only language I know of where the presence of whitespace on blank lines matters is make(1). Even there, it's subtle. It's okay to have (using "cat -e" syntax)

foo : bar$
	command$
$
	command$
But there's a difference between
foo : bar$
	$
which specifies an empty command and will therefore not use a default rule, and

foo : bar$ $

which does not specify any command and so will use a default rule if one exists.
(Of course, you can also get [ \t]\n inside an arbitrary binary file, too.)
Message 1 of 1 in “Re: the war on trailing whitespace”
  1. linux@horizon.comFeb 28, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.