Jump to content

clevermistakes

Member
  • Posts

    9
  • Joined

  • Last visited

Everything posted by clevermistakes

  1. No problem if it's a strange one off, I usually use it to open up specific or hidden files quickly for editing, things like /.ssh/config, key files, scripts or containers I'm working on, etc. Not a big deal to do it from Sublime, just became a habit with the ">" command from Alfred...I can continue to use >subl <whateverfile> and use . for everything else! Thanks for all your help Vitor, and the workflow itself! It's been great so far!
  2. Hi Vitor, It's a different response, that's good news. No error this time, but nothing happens, all I get in the debugger is: [input.keyword] Processing output of 'action.script' with arg 'subl'
  3. Sure no problem, results in /usr/local/bin : subl -> /Applications/Sublime Text.app/Contents/SharedSupport/bin/subl The shell and path should be macOS Sierra's default, don't think our work image changes anything: /bin/bash /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin I'm sure your code is great, it's clearly time tested and approved, I'm as curious about the issue as you are! Other than subl, everything else is working great! So far I love it! I don't think there's a non-standard setup, since we regularly wipe our machines when we travel internationally. So by default macOS Sierra doesn't create a bash profile so there shouldn't be one, I just restored this machine like...a week or two ago? I haven't made any modifications to bash other than the symlink for sublime since I use it all the time. Unfortunately my work machine is kind of boring haha, it's pretty barren short of GitHub and Docker since everything I do for work is otherwise on remote machines.
  4. I actually only have a symlink for sublime text, sorry for the confusion. For this issue, on my work machine, my bash profile is actually blank. I simply use the symlinks for it. Most of my aliases are done on remote machines so those machines have the full alias lists, I don't use many on my local machine, probably terribly inefficient of me. Sublime is the only one I've tried so far and use often on my machine for editing deployment configs.
  5. I've got actual aliases in ~/.bash_profile but the command for subl is a symlink to /usr/local/bin
  6. Sure! Can do. Alias: subl for this symlink: ln -s "/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl" /usr/local/bin/subl Command: Opens sublime text or a specific file in sublime, for example: subl /etc/hosts Shell Version: GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16) Alfred input before RunCommand: >subl (works) RunCommand input: .subl (fails, error 127 exit status) Debugger output: Starting debug for 'RunCommand' [ERROR: action.script] /tmp/runcommand: line 4: subl: command not found
  7. Have you ever encountered issues where some of us lazy users are creating symlinks in /usr/local/bin rather than a home folder? Tried running an alias I use and got an error. Should I just create a quick profile for it to use and path the location?
  8. This is perfect! Thanks a ton for writing this! I knew someone had to have the same complaint as me somewhere. I'm glad to know there's plenty of us risky bash users who don't care about what the shell says back to us! haha
  9. Hey All, Looking for a solution on a very minor annoyance, I usually run a lot of shell commands from Alfred using the > prefix, which is great! Love it! However, when it executes the command it pops open terminal and runs the command and leaves another lingering window around which I find annoying. Does anyone know of a way to force Alfred to close the window it opens after the command is executed? Very rarely do I need the returned command's output. It's usually for firing off quick things like docker pulls, file moves, git commits and such. If I need to do this through an AppleScript I'm open to that as well, just wanted to find some way around my terminal windows popping up everywhere like mushrooms. Thanks!
×
×
  • Create New...