Jump to content

Search the Community

Showing results for tags 'debug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 5 results

  1. Alfred 3.1 (711) OS X 10.11.6 In the situations where input is a sequence, not a single string (i.e. File Actions and Hotkey+Selection in OS X where files are selected), the Debug and Filter Utilities choke on the input. They do nothing and emit no output, bringing the workflow to a halt.
  2. I love Alfred but I struggled at first to troubleshoot my workflow scripts due to difficulty finding a way to debug. I've seen posts mentioning writing logs to an external file but that seemed hack-y, especially since Alfred includes a debug console. If you'd like to use the console to debug your scripts, I found the following very useful. It would be great if there were a mention of this in the docs: To show script output in the debug console, print (or echo or put, etc) the output to stderr instead of stdout. In a Bash script: >&2 echo "Log this output to the console" In a Python script: import sys sys.stderr.write("Log this to the console") For other languages, look for an equivalent method that allows you to log to stderr.
  3. A little script to help you write your Alfred Workflows. In the case your script has an error, Alfred defautls to searching your query in a search engine. To catch these errors you can run them in Terminal, and see what the errors are quickly and easily. https://github.com/willfarrell/alfred-debugger
  4. A very simple little workflow I made to automatically sample to frontmost application's process. Samples save to text files in /tmp. Useful for quickly saving a sample to send to the developer before force quitting the app. Download
  5. I've started work on a workflow bundle that I intend to use as a base for other scripting workflows. The language I'm most proficient in is Ruby, so I've taken the liberty of creating this for myself and others to use when developing in Ruby. Features: Shows exceptions and debug output in the Mac OS X Console Adds a ruby gems repository to the workflow bundle so you can package gems with your workflow. Provides access to the workflow bundle's info.plist data Provides sqlite3 gem It's incomplete, but I wanted to get feedback from others as soon as possible. For example, I've added a compiled sqlite3 gem in as part of the gem repository. Does this work across Mac systems? i.e. if you install the workflow, do you get sqlite3 support out-of-the-box? To get started: Copy the init.rb.example file into your script window (e.g. Run Script action). Choose /usr/bin/ruby as the script language. The contents of init.rb.example is some "bootstrap" ruby code that takes great care to catch all exceptions and send them to the Console.app so you can debug your scripts. Copy alfred.rb and main.rb to your bundle. Also copy ruby-1.8 and its subdirectories. This is the gem repo that will let you install gems as part of the bundle for others to use. https://github.com/canadaduane/alfred2-ruby-framework Thanks, Duane Johnson http://makerhome.ca/
×
×
  • Create New...