forked from moretension/duti
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey man, needed to reach you about duti #1
Open
holdhack
wants to merge
27
commits into
nivekkagicom:master
Choose a base branch
from
holdhack:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Address comments -- move variables closer to first use.
Style cleanup because what the shit?
Clean and markdown-ify README. Add need for autoconf.
macOS 10.12 support
Add new -o option to display the URLs of applications that are able to handle a file (may be specified as path or URL) (see nivekkagicom@fb227ec)
Add new -t option to register applications as handlers for OSType file types; similar to -e (extension) option. e.g: duty -t TEXT (whereas duti -e would use txt) (see: nivekkagicom@f7f271b)
Show both the content and url scheme handlers in case same name is used for both types (see: nivekkagicom@b09528d)
Added returntype to function duti_default_app_for_type
I do not use homebrew and I have a number of tools that use duti not utid. It looks to be a fair amount of work to merge the forks and retool my environment which I cannot afford at this point. I will look at rebasing from your fork at some point. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello @nivekkagicom,
This wasn't really meant as a pull request per se, but more of a way to contact you.
As you've probably noticed, duti is pretty ill-maintained: I'm working on a fork here that basically pulls the best bits from all the forks on the network., among which your stuff. I use duti myself, so I'm happy to maintain it (and give others push rights if wanted/needed). A big advantage: no autoconf so no need for constant macOS version updates. But back to my main point: it seems to me that its much better to all just bundle our powers :)