Disqus - Latest Comments for chendo

Re: Selectively ignoring Objective-C exceptions in Xcode - chendo

chendo — Sun, 13 Jul 2014 09:46:56 -0000

Just add more selector:regex arguments to the end. The matching is OR'd

Re: Selectively ignoring Objective-C exceptions in Xcode - chendo

chendo — Sun, 13 Jul 2014 09:44:46 -0000

In some cases, the name selector of an exception does not match the class. Try className:NSRange instead.

Re: Improved non-Latin language support - Shortcat Blog

chendo — Sun, 06 Apr 2014 19:02:32 -0000

I didn't have the time to do much testing in all the languages heh. Can you provide the specific case it doesn't work on? I'm still trying to decide whether or not prefix searching is appropriate for non-Latin languages.

Re: Selectively ignoring Objective-C exceptions in Xcode - chendo

chendo — Fri, 04 Apr 2014 20:22:38 -0000

The arguments after ignore_specified_objc_exception is a list of OR filters on the exception to filter out, where the name:NSRangeException format refers to [selector]:[regexp]. It will call the selector on the exception, and ignore it if what is returned by [exception name] matches the regexp /NSRangeException/. I found that some exceptions were a bit weird and had what you were looking for in `className` rather than `name`. You can always try capturing the exception in a try/catch, then finding out its `className` and `name` values and use that accordingly.

Re: 10 Mac Productivity Tools That You Can't Live Without - by Taylor Hatmaker

chendo — Tue, 19 Nov 2013 19:52:17 -0000

There's also Shortcat (https://shortcatapp.com) which lets you click on UI elements with just the keyboard, but it's mainly targeted at super power users and fast typists.

Re: Reverse engineering Xcode with dtrace

chendo — Sat, 26 Oct 2013 02:02:00 -0000

Thanks :)

Re: Reverse engineering Xcode with dtrace

chendo — Sat, 26 Oct 2013 01:57:21 -0000

I'd say that's in the realm of another plugin, as ideally it would patch a different part of Xcode as it's not ideal to patch it where FuzzyAutocomplete patches due to performance reasons. I didn't find a good entry point to remove suggestions where I was digging through Xcode either..

Re: Reverse engineering Xcode with dtrace

chendo — Sat, 26 Oct 2013 01:54:28 -0000

Since v1.3.1, the Tab key inserts completion.

Re: Reverse engineering Xcode with dtrace

chendo — Tue, 22 Oct 2013 20:25:56 -0000

Ah, that behaviour. That is due to my prefix algorithm being different to Xcode's built in one as theirs is designed around all the completions in the current filtered set to have the same prefix, which is obviously not the case in fuzzy autocomplete. Tab has always inserted the current prefix or the full completion when there are no other alternatives. I can have a look at fixing it once I have time for it again.

Re: Reverse engineering Xcode with dtrace

chendo — Tue, 22 Oct 2013 04:32:41 -0000

I don't believe I have changed the behaviour of the Tab key... Without FuzzyAutocomplete, Tab will partially complete the completion, rather than fully completing it, at least for me.

Re: A test server for Rails applications

chendo — Wed, 19 Nov 2008 18:52:13 -0000

Awesome, thanks! (sorry for late reply)

Re: A test server for Rails applications

chendo — Tue, 18 Nov 2008 03:20:00 -0000

This commit fixes this issue: http://github.com/chendo/ra...

Re: A test server for Rails applications

chendo — Tue, 18 Nov 2008 03:19:14 -0000

Sorry Roman2K, the commit we posted actually didn't work (service_uri was returning the mkdir_p, which was tmp/sockets and not the actual file).

This commit (http://github.com/chendo/ra... works and also fixes the machinist problem we were having, where the first test would run, but any after that would error saying 'no blueprint for Foo'.

This fork solves it by adding a TEST_SERVER_OPTIONS constant that you define before you require 'rails-test-serving'.

Example:

TEST_SERVER_OPTIONS = {
:reload => [/blueprint/]
} unless defined? TEST_SERVER_OPTIONS

The 'unless defined' part is there to stop the warnings.

This forces any required files that match /blueprint/ to be reloaded.

Also my fork allows you to run tests when not in RAILS_ROOT, since the SERVICE_URI in Roman2K's branch is relative to the current directory. Our fork currently looks up three directories (three because the test folder shouldn't be any deeper than that) to find config/boot.rb, then adds tmp/sockets/test_server.socket to that path.

This is awesome and hopefully our fork has made it even more awesome.

P.S. Shouldn't it be called 'rails-test-server'?

Re: A test server for Rails applications

chendo — Tue, 18 Nov 2008 02:31:55 -0000

Don't use my fork yet... turns out it's got some issues (it was requiring the wrong gem so it might not have been working properly).

Also ran into issues with clean_up_app nuking machinist blueprints, but should have a solution soon.