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

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 3209 - formatting source code
formatting source code
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-08-20 17:03 UTC by Marc Meurrens (be)
Modified: 2010-05-15 15:38 UTC (History)
0 users

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


Description Marc Meurrens (be) 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...

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.