Last modified: 2010-05-15 15:38:29 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T5209, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 3209 - formatting source code
formatting source code
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.5.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-20 17:03 UTC by Marc Meurrens (be) http://www.meurrens.org/
Modified: 2010-05-15 15:38 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Marc Meurrens (be) http://www.meurrens.org/ 2005-08-20 17:03:05 UTC
This is, in fact, a question.

I just submitted a few diff -Naurb files (regarding SpecialExport.php).
I have some other things to submit.

I am willing to stick as much as possible to your files as to avoid
too large diff files.

Unfortunately my IDE (I use Zend Studio on Linux) does not indent code exactly
as your own IDE (tabs, number of spaces, etc).

What reformatting tool do you use on your file 
(and eventuaally with which parameters) before publishing the sources.
So that I can use the same before generating the diff files...

Thanks
Comment 1 Niklas Laxström 2005-08-20 17:16:06 UTC
There is no single one IDE we developers use. But we use spaces for indenting
line starts, which should be possible to configure with every IDE or set
automatic formatting off. I don't remember what all those diff flags mean, but I
use simply diff -u, and separate diff -uw, if there is much whitespace changes
interfering the reviewing of the diff.
Comment 2 Brion Vibber 2005-08-20 23:35:37 UTC
Indent using a single tab for each level. (4-column tab stops recommended, but 
it shouldn't matter.) Never mix spaces and tabs!

Please follow existing style in new code as well, as deviating makes code more 
work to read and maintain.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links