Re: Behaviour for key binding for jumping to the next warning/error
Re: Behaviour for key binding for jumping to the next warning/error
- Subject: Re: Behaviour for key binding for jumping to the next warning/error
- From: Mattias Arrelid <email@hidden>
- Date: Tue, 29 Apr 2008 11:29:19 +0200
On 28 apr 2008, at 17.11, Howard Moon wrote:
In the Build Results window, you can just un-click the "show or hide
warnings" button to hide the warnings. Then, Cmd+= will step through
just the errors.
Thank you very much, I didn't know about that! I still think it is
kinda strange that you have to use your mouse to enable/disable this
(I used the Help menu's search function to find a menu item with such
toggling functionality without finding one). And what's even worse, I
cannot step through warnings only.
I filed an enhancement request (which sums up to "please let me do
this without having to use the mouse - and let me step through either
errors or warnings"), and wrote a blog post about it (since I like
other people who agrees with me to find some search results on this
topic while browsing the web):
http://arrelid.com/archive/2008/04/29/xcode-3x-stepping-through-warningserrors
Thanks again.
/ Mattias
On Apr 28, 2008, at 3:02 AM, Mattias Arrelid wrote:
Good morning folks,
Since we're humans, we sometimes make mistakes. This might happen
during coding too; when trying to build the compiler will spit out
some warnings and errors if we've done something wrong.
Now Xcode has a keyboard binding that will open up the editor and
show
the last build's next warning/error (command + =). This is a very
useful key combo, but I have some thoughts on how it could be
improved.
In my day-to-day development, I'd rather much fix all the errors
first, and then step through the warnings. This could be solved in a
number of ways (each and every such is, afaik, not implemented in
Xcode today):
- Have two key combos; say that "command + =" will cycle forwards
through errors, and "command + shift + =" will cycle forward through
warnings. This way, I could cycle through all errors first and then
test run my program, without fixing the warning (of course, you
should
always strive after fixing all errors as they appear in your code)
- Have the possibility to let todays key binding first step through
each error, and then through the warnings (like a queue with all
errors first, followed by the warnings).
Is something like this possible today? If not, I might as well file a
bug with some enhancement requests over at Cupertino.
Regards
Mattias
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden