• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Behaviour for key binding for jumping to the next warning/error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: Howard Moon <email@hidden>
  • Date: Mon, 28 Apr 2008 08:11:15 -0700

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.

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:
40antarestech.com


This email sent to email@hidden

_______________________________________________ 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
  • Follow-Ups:
    • Re: Behaviour for key binding for jumping to the next warning/error
      • From: Mattias Arrelid <email@hidden>
References: 
 >Behaviour for key binding for jumping to the next warning/error (From: "Mattias Arrelid" <email@hidden>)

  • Prev by Date: Exceptions thrown when writing to stderr when running under Xcode 2.5
  • Next by Date: Re: Exceptions thrown when writing to stderr when running under Xcode 2.5
  • Previous by thread: Behaviour for key binding for jumping to the next warning/error
  • Next by thread: Re: Behaviour for key binding for jumping to the next warning/error
  • Index(es):
    • Date
    • Thread