• 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: Over zealous autocomplete
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Over zealous autocomplete


  • Subject: Re: Over zealous autocomplete
  • From: Rick Mann <email@hidden>
  • Date: Thu, 09 Aug 2012 15:29:52 -0700

I have a lot of problems with the keys used around code completion. At least in Xc4.4 I can change more of them. I got rid of ESC. Changed "next completion" to option-Tab.

I just looked a bit more. You can change "Insert Tab without Extra Action" to be tab, that will stop tab from selecting the next template placeholder.

You can then change "Insert Tab" to be something else (I used command-option-tab), and that will jump to the next placeholder, but it still inserts a tab if there's no placeholder (kinda goofy).

I bring show the next completion with option-tab (which I might change to command-tab, because I never use that as a way of switching between apps, and it's easier to type).

--
Rick



On Aug 9, 2012, at 6:52 , "Mills, Steve" <email@hidden> wrote:

> On Aug 9, 2012, at 07:41:40, Jean-Denis MUYS wrote:
>
>> "tab" means "go to the next thing". To me the choice fits nicely.
>> It's unfortunate that "tab" *also* ended up meaning "align to such line position".
>
> Primarily, tab is used for alignment (remember typewriters?). It only got the added task of moving between things when computers came along.
>
>> For me the two meanings almost never collide in the example you give, simply because when I program, my eye stays on the screen, mostly.
>
> So do mine.
>
>> I don't complain however. The only alternatives to Tab I can imagine are Return and Enter.
>> Many keyboards don't have Enter any more. And Return could yield the same issue that you raise.
>
> No, return/enter mean "accept the choice I have selected". If tab means "go to the next thing", then it shouldn't accept what's currently selected, especially when it means it will accept boolean_t when I've typed bool and didn't actually select boolean_t. BTW, that seems to be a bug that shows up sometimes, one I haven't been able to reproduce. Ever since that day, bool is always the first choice as it should be.
>
> --
> Steve Mills
> office: 952-818-3871
> home: 952-401-6255
> cell: 612-803-6157
>
>
>
> _______________________________________________
> 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


 _______________________________________________
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

References: 
 >Over zealous autocomplete (From: "Mills, Steve" <email@hidden>)
 >Re: Over zealous autocomplete (From: Jean-Denis MUYS <email@hidden>)
 >Re: Over zealous autocomplete (From: "Mills, Steve" <email@hidden>)

  • Prev by Date: Re: Mac app crashes using library built with Xcode4.3+, which used to work with Xcode4.2
  • Next by Date: Viewing values within allocated memory in C with XCode debugger
  • Previous by thread: Re: Over zealous autocomplete
  • Next by thread: Re: iOS4.3 simulator on Xcode 4
  • Index(es):
    • Date
    • Thread