Jump to content

Search the Community

Showing results for tags 'Terminal'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


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

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL




Found 82 results

  1. When I type > followed by a shell command and hit enter, Alfred command window disappears but nothing else happens, terminal doesn't open and command is not executed. This feature used to work, but I'm not sure after which upgrade it broke. I have iTerm2 installed so I tried changing terminal app setting, and changing prefix – no result. Only when I switched to "Custom" setting (and left default Action Script snippet) it worked again. OS X 10.10.1 (14B25) Alfred v2.5.1 (308)
  2. This was now consolidated into RunCommand, so you should download that instead.
  3. Tmux Workflow for Alfred app Alfred workflow to manage tmux sessions, integrated with iTerm2. It can list current sessions, connect to them, kill them or create a new one. The connect or create action actually opens iTerm2 and connects to the session. Additionally, in all the open actions (new session or connect to session) it can cd to the current Finder's or Path Finder's directory. Please note: the workflow only handles tmux sessions. It doesn't handle windows, panes, or any other tmux command. Dependencies iTerm2 installed tmux installed in /usr/local/bin/tmux; easily installed with homebrew doing brew install tmux Usage Write the tmux keyword in Alfred to trigger the workflow. The initial menu options are: An initial not actionable menu item indicating to keep writing after the keyword to search/filter or create a new session. Option to connect to a default tmux session. It's a session named "default" that will always appear in the menu, and if it doesn't exists it will be automatically created. You can start typing right away after the keyword for search or create a session, or optionally add a space after the keyword for readability; the space is ignored. You'll see the filtered results (bash/zsh included), and a last option to created a new tmux session with the entered name, if non existent. If you want to kill a session, action it with ⌥ down. If failure, for example trying to kill the bash/zsh option, you'll hear a classic error sound. If you want to open the current Finder's or Path Finder's folder, action the current or new session with ⌘down. This command is very fast for new tmux sessions but adds a delay of 1 second for existent tmux sessions, since I cannot find a way to wait for tmux session to load, except by waiting long enough. Still, opening current Finder's path in already existing sessions shouldn't be that common. Installation For OS X 10.9 Mavericks, Download the alfred-tmux.alfredworkflow and import to Alfred 2. For Previous OS X Versions, Download the alfred-tmux.alfredworkflow and import to Alfred 2. Source Code Clone or Fork the Workflow: https://github.com/ramiroaraujo/alfred-tmux-workflow Changelog 2014-02-05 - Released
  4. Greetings -- I'm writing documentation and would like to paste code examples from my editor into an interactive shell running in a given Terminal tab, e.g. a tab named "Scala". How should I go about building a workflow for it in Alfred? Cheers, A+ (Alexy)
  5. Hi, I want to use a series of terminal commands, first to open the terminal ( if needed ), change the user ( log in as another user ), enter in a folder and execute a command to start a SQL server and then log out and close the terminal window ( if needed, maybe I can do it without opening it ). After that I want to do the same to stop the server, but following the logic is the same script just changing the start to stop. # Manually Start PostgreSQL ## su as user "postgres" and run server: su postgres # type the password ( if possible do it automatically ) cd /Library/PostgreSQL/9.0/bin/ ./pg_ctl -D /Library/PostgreSQL/9.0/data/ start # then logout exit # close the terminal window Anyway thanks for the attention !
  6. Hi, Here is a new workflow: https://github.com/raguay/MyAlfred/blob/master/OpenInAlfred.alfredworkflow You type "oa:install" to install a helper script into your /usr/local/bin directory. Make sure that directory exists, is writable by you, and in your path. Then you can use these commands: oa:terminal open the topmost terminal window in Alfred oa:iterm open the topmost iterm window in Alfred Let me know if this works for you.
  7. 1. Create a new Workflow 2. Add a new Terminal Command 3. Type quotes in the dialog box for the script RESULT: The quotes ("") are made into smart quotes, if your system is set to use them. Bash does not like smart quotes, and your script will fail. EXPECTED: This dialog should disable smart quotes, dashes and the like, as they are not appropriate for Bash scripts. Alfred Version: 2.2 OS X Version: 10.9.2
  8. Hi, I'm currently using a workflow that does not work at desired. I try to open a specific location in iterm using the specific applescript tell the last session write text "cd " & q & "; clear; pwd" end tell Going to regular destinations like: /Users/MyName/Downloads works fine, but going to locations with two words or more like: /Users/MyName/Git Projects/Project1 doesn't work. Does anybody with applescript and iterm knowledge know the fix? Thanks, Nolan
  9. As a new Powerpack user, I've been downloading several great workflows that I'm already using many times a day. However, a workflow I couldn't find is one that opens a terminal window and sets the current working directory based the results of an Alfred query. So I created my own and I'm sharing it here in case others find it useful. What it Does: Opens a new terminal window and sets thw current working directory based on an Alfred query that only considers folder names. Link to Workflow: https://bitbucket.org/gotz/alfred/src Dependencies or System Modifications: None Examples:
  10. When using a Terminal Action in a workflow, the Terminal app is started and the command run successfully. If, however, a new tab is started with cmd-T or through the Terminal "Shell" menu, the command that Alfred originally sent to Terminal is run again in the new tab. Cheers, -Ben
  11. Hi all, interesting behavior I'm seeing with a workflow I made. The workflow (linked below) waits for 'w directory' then opens that directory in terminal and runs a command to open Sublime Text on the directory. It works great but when I have that original terminal window open, any time I then open new window (in tab or new window), the command is repeated. When I close the original window, the command no longer happens when opening a new window. Seems odd, any ideas? Thanks! https://dl.dropboxusercontent.com/u/1662270/Workon.alfredworkflow
  12. I'm new to the update of alfred 2 and I'm having some problems when creating a workflow. i would like to run the following script: cd /application/language/nl_BE/LC_MESSAGES/ grep -v '^#: ' common.po > common.po.tmp && mv common.po.tmp common.po It works perfectly when I choose 'Actions -> run script' but nothing happens while when I use 'Actions -> terminal command' it works.
  13. Hello, Here is a workflow that let you choose between preconfigured iTerm2 windows/panes configurations. This is useful when you have to work with different terminal windows. And possibly launch remote ssh session in each one to process some "tail -f" kind of real time log analysis. This workflow is an Apple Script script that embed your windows configuration. So you have to configure/set/change the configs you will call as parameter from the keywords. Dependencies: iTerm2. Configuration: At top of AppleScript. Download: Alfred2-iTerm2 on GitHub. Olivier.
  14. Hi, first of all, sorry for my english. The other day I found that there is a terminal command to force openning an app more than 1 time. For example, openning two VLC windows. That terminal command is 'open -n /applications/vlc.app' My idea is to create a ALFRED WORKFLOW similar to this: openn USER_INPUT_(APP_NAME) an example: typing openn vlc then, execute the terminal command: open -n /applicaciones/USER_INPUT_(APP_NAME).app I know how to get USER_INPUT_(APP_NAME), but I do not know how to "paste" this text in the TERMINAL COMMAND One more thing, is there any command to really close a TERMINAL WINDOW? I know there is 'exit' but this command does not close the windows, just finish the console. Again sorry for my english, and thank in advance.
  15. I am working on a workflow which should execute a shell script command for of the documents (*.xml files) currently selected in the Finder. I did some experiments around it, but could not get it to work yet. Any pointers, e.g. what workflow elements I will need? I am currently thinking along the lines of first calling an applescript which gives me the selected files, then filtering out only the xml files and lastly calling a shell script for each of the files or alternatively calling the script once but passing along an array of xml files. What do you guys think? Thanks for any suggestions / sample workflows.
  16. I dont understand how the "Keyword to terminal command" workflow works. I am trying to simply run silentely if possible (do not need to see the terminal poping up) the following command: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user This command clear the "Open with" menu from multiple entries. I usally run it from the terminal but I thought I could do a simple straightforward Workflow. I dont know how to run this in the background without having the terminal window coming up. Any help appreciated.
  17. When I was using "Open Terminal here" action today, I found that this command is not executed with arguments quoted. For example, here I got a folder named "a&b", when I perform "Open Terminal Here", a error happened. Why? I am guessing that the terminal actually executes such a command, "cd a&b", so it is apparently that this command is split by the symbol "&". I hope you can fix this bug just by surrounding the target folder path with a pair of quotes like this: cd "a&b" instead of: cd a&b thanks~ by iSMart
  18. I have a simple workflow that looks like this: cd ruby_projects/{query} tab bundle exec guard tab bundle exec rails console tab tail -f log/development.log powder open I'm using ZSH with "oh-my-zsh" and including the osx plugin. the "tab" command opens a new tab and runs the proceeding command. Powder is a control utility for 37-signals "pow" app. When I execute the workflow, it runs each of those commands in each terminal tab that it opens. The result is much more than four terminal windows and I also get several browser windows open from the "powder open" command being run multiple times. Does this seem like an alfred issue? When I executed the series of commands directly in the terminal I do not have this problem.
  19. I like to quickly get to the terminal and quickly hide it. This Alfred workflow allows you to show/hide iTerm with Shift+Cmd+Space. Download
  20. There are already multiple discussions on Alfred-run Applescript sometimes having a different behaviour than on other places, and in many cases, it seems like nothing can be done about it, since Alfred is not doing anything special with the scripts (which means it may be out of reach for the developers to solve). In this case, however, it’s a case of Alfred apparently having a different implementation in different places. It’s seems more of an oddity than a bug, but there’s no “oddities subforum”. Using the latest builds of both Alfred (2.0.6) and Mountain Lion (10.8.4). The code in question is on alfred_script(q) tell application "System Events" to set isRunning to (name of processes) contains "iTerm" tell application "iTerm" if not isRunning then set _term to (make new terminal) set _term to the first terminal tell _term to set _session to current session else set _term to the first terminal tell _term to set _session to (launch session "Default") end if tell _session to write text q activate end tell end alfred_script What this does is, taking a command as an argument, if iTerm is currently closed, it’ll open a window, and run the command; if it’s open, it’ll open a new tab on the current window, and run the command. If I set this on Run NSApplescript connected to Keyword, in a workflow, or run it from AppleScript Editor, it runs just as intended. However, if I set this as the Custom code for the Terminal / Shell option on the Features tab, it does not — if iTerm is closed, it opens it and a new tab, running the command on this second tab, and if iTerm is already open, it’ll behave as expected. Why is it working differently in these two places? What is it about the Terminal / Shell feature that makes it behave differently (and in a suboptimal manner)?
  21. When I select a directory 'foo' in Alfred and choose the "Open Terminal Here" action, a Terminal window opens and Alfred and the command 'cd foo' is entered. At this point, my clipboard contents has now changed to 'foo'. This is annoying, especially if I'd just copied something I wanted to paste. Probably a better behavior would be to replace the clipboard contents after pasting the directory in, or to not even use the clipboard, right? I'm using Alfred 2.0.5 and OS X 10.8.4.
  22. Hello, Can anybody tell me what i have to do to start the maintenance scripts with an workflow ? I mean the sudo periodic daily, weekly, monthly scripts. Sorry for the bad english !!!!!!!!! Best Regards jm1982
  23. dysonant

    Amber Waves

    A throwback amber screen theme that is minimal and easy to read. DOWNLOAD AMBER WAVES
  24. I would like to create a workflow that basically executes a series of terminal commands, one after another. The input requires no query or variables, it's just a series of commands. The only hitch may be that I have to wait for the first terminal command to finish before executing the next command.
  • Create New...