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

Code Formatting vs Trailing Whitespaces

From
FKFlorian Köberle <florianskarten@web.de>
Date
Jun 23, 2008, 18:15 UTC
Message-ID
<485FE856.1080808@web.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi

I noticed that Robin removed trailing whitespaces from my patch(thanks). It appears that if you enable code formatting and the removement of trailing whitespaces in the save actions option that the formatting option will win. It will add a space at the second line of a javadoc comment: /** ~ * <----

I think this is a bug in eclipse, did any of you create a bug report for that? Or a feature request for an "no whitespace after javadoc" option in the code formatter page?

I want to have both options active, because I don't want to commit wrong formatted patches.

Best regards,
Florian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIX+hW59ca4mzhfxMRApU4AKCbYzwRFqVcBCr11zc9lk6jqick2ACeMBhW nXOoN4nIsTjzWWhQzDOxiz4= =bm+i -----END PGP SIGNATURE-----

Next: Robin Rosenberg
Message 1 of 4 in “Code Formatting vs Trailing Whitespaces”
  1. Florian KöberleJun 23, 2008
  2. Robin RosenbergJun 23, 2008
  3. Florian KöberleJun 23, 2008
  4. Robin RosenbergJun 24, 2008

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.