| Code formatting on check-in/commit and check-out/edit for first time? [message #148187] |
Thu, 11 March 2004 14:11  |
Eclipse User |
|
|
|
Hi,
In our company, each of us developers has a slightly different way we would
like to see our code formatted, especially when working with it. I so happen
to put my screen at high res and can see 130+ columns of text at one time
when editing. As such, I don't line-wrap my code. Some co-workers work on
laptops and see 60 or so lines at most, and prefer to have it line-wrapped,
as well as some like the braces at the end of the line, I like them on a new
line, etc. I know the formatter in 2.x and more so in 3.x can handle this.
What sucks is that we manually have to do this for every file every time we
want it in our way. Since we work as a team, we use VSS (and CVS for some
projects). I believe it should be a simple addition to add some sort of
trigger that on check-out OR first edit (in CVS case) of a file, it can
format the code into the way the IDE's formatter is set up. Then on
check-in/commit, it can also format it into perhaps a "standardized" format
that the company may want all code to be formatted in.
Is there any such ability now that I am not aware of in 2.x or 3.x that may
allow this type of triggering to occur? For the Eclipse team, if there
isn't, is it something ya'll might consider adding?
I can see this being useful for more than just formatting code on
inbound/outbound. It may trigger a rebuild (which already works though, but
hypothetically speaking...), or some other ability when files are committed.
Maybe a code analysis, spell check, etc.
Thanks
|
|
|
|
|
|
|
|
| Re: Code formatting on check-in/commit and check-out/edit for first time? [message #155036 is a reply to message #148253] |
Mon, 19 April 2004 18:45  |
| Eclipse User |
|
|
|
Spiderman,
that is a really nice feature. It would also finally make sense of
the diffs sometimes sent out to mailing lists. All the reformatting
messes things up with cvs.
There is a search facility at bugs.eclipse.org. I tried to search
your bug report with not much of a success. Could you try again with
your search phrase and post the bug # ?
Cheers,
Mariano
spiderman wrote:
> Did so..just added, but closed the browser before copying the # down. Is
> there a quick way to look up feature requests?
>
> "Eric Bodden" <newsserver_mails@bodden.de> wrote in message
> news:c2qop9$9rp$1@eclipse.org...
>
>>Also a server-based solution would not be very helpful in that case since
>>the formatting options have to be set per client.
>>
>>I would suggest you file a feature request on that.
>>
>>Eric
>>
>>spiderman maundered in <c2qlte$6ga$1@eclipse.org>
>>
>>>True indeed, but generally on a per file, this may add a second or
>>>two for formatting anyway. I would be willing to live with that. For
>>>CVS I know you can set up stuff on the server to fire off when
>>>commits come in as well, I just prefer to do it on the client, so the
>>>server is not burdened as much.
>>>
>>>"Eric Bodden" <newsserver_mails@bodden.de> wrote in message
>>>news:c2qevk$tnr$1@eclipse.org...
>>>
>>>>Hi!
>>>>
>>>>I must say I love that idea. However I think that there could be
>>>>slight performance problems on large commits. At least on my
>>>>(probably not latest) PC code formatting takes sometimes quite some
>>>>time (2-3 seconds) for large files.
>>>>
>>>>Eric
>>>>
>>>>--
>>>> ------------------------------------------------------------ -----
>>>>Eric Bodden
>>>>ICQ UIN: 12656220
>>>>Website: http://www.bodden.de
>>>>PGP key available
>>
>>--
>> ------------------------------------------------------------ -----
>>Eric Bodden
>>ICQ UIN: 12656220
>>Website: http://www.bodden.de
>>PGP key available
>>
>>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.14150 seconds
Home