Coder Social home page Coder Social logo

alfred-terminalfinder's People

Contributors

kevinxucs avatar leenno avatar olibob avatar raghavpillai avatar vitorgalvao avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

alfred-terminalfinder's Issues

Finder -> iTerm command launches session named "Default" instead of using the one marked as default

The fi command in TerminalFinder.alfredworkflow should use "" instead of "Default" to launch a session with the default Profile instead of one with the Profile named Default.

tell myTerm
    if not isRunning and termCount is not 0 then
        set mySession to current session
    else
        set mySession to (launch session "Default") -- replace "Default" with "" on this line
    end if
    tell mySession to write text "cd " & pathList
end tell

The src/fi.scpt.txt file has the correct line already so I guess an export might be all that's needed.

Both tf and ft does not work fine

when I type tf
[2018-06-29 16:53:34][ERROR: action.applescript] {
NSAppleScriptErrorBriefMessage = "The result of a numeric operation was too large.";
NSAppleScriptErrorMessage = "The result of a numeric operation was too large.";
NSAppleScriptErrorNumber = "-2702";
NSAppleScriptErrorRange = "NSRange: {87, 12}";
}

when I type ft
[2018-06-29 16:54:06][ERROR: action.applescript] {
NSAppleScriptErrorBriefMessage = "The result of a numeric operation was too large.";
NSAppleScriptErrorMessage = "The result of a numeric operation was too large.";
NSAppleScriptErrorNumber = "-2702";
NSAppleScriptErrorRange = "NSRange: {623, 12}";
}

macos 10.13.5 (17F77)
alfred v3.4
iterm2 Build 3.2.0beta5

Add Warp support?

open -a Warp.app $(osascript -e 'tell application "Finder" to get the POSIX path of (target of front window as alias)')

Use iTerm instead of Default Terminal app

First of all thanks for this very helpful Workflow 🙂

Can somebody help me out in setting iTerm as the Terminal app to use?
Do I have to manually adjust the NSAppleScript or set any other option I am not aware of?

Not work with iTerm version 3.0

Alfred 2 latest version
alfred-terminalfinder version 1.6.0

User Keyword fi

Starting debug for 'Terminal Finder v1.6.0'

[ERROR: alfred.workflow.action.applescript] {
NSAppleScriptErrorBriefMessage = "Expected class name but found identifier.";
NSAppleScriptErrorMessage = "Expected class name but found identifier.";
NSAppleScriptErrorNumber = "-2741";
NSAppleScriptErrorRange = "NSRange: {417, 8}";
}

Pathfinder to iTerm not working

Using PI shortcut to open current Pathfinder location in iTerm is no longer functioning correctly. It will open iTerm, however, it will not apply the expected path

fi gives error on iTerm 2.9.20151001 + OSX Version 10.10.5 (14F27)

When Finder has focus, calling the fi extension (Finder -> Iterm), with error logging activated via Alfred this error is logged:

Starting debug for 'TerminalFinder'

[INFO: alfred.workflow.input.keyword] Processing output 'alfred.workflow.action.applescript' with arg ''
[ERROR: alfred.workflow.action.applescript] {
    NSAppleScriptErrorBriefMessage = "Expected class name but found identifier.";
    NSAppleScriptErrorMessage = "Expected class name but found identifier.";
    NSAppleScriptErrorNumber = "-2741";
    NSAppleScriptErrorRange = "NSRange: {345, 8}";
}

finder ---> iTerm failed

Environment:
OS X EI Capitan Version: 10.11.3
Alfred 2 Version: 2.8.2
iTerm2 Build 2.1.4

I used custom-iterm-applescripts-for-alfred for fixing iTerm integration with Alfred 2.

I have installed branch 2.1.x 's workflow but it opened Terminal with the correct path. Here is a snapshot:

2016-03-08 22 43 33

@LeEnno Please let me know if I missed something or needing more detail and log. Thanks very much!

[Bug] Finder->Terminal/iTerm not working on macOS Catalina

Hi!

When I tried to use fi or ft to open the current finder path in Terminal/iTerm, the generated command is clear; cd '/Users/tillchen/Downloads:/', which is actually an invalid path due to the colon at the end. I guess this might be caused by the change of macOS Catalina?

Thank you!

Error on using "fi"

This error occurs when using "fi" command

[ERROR: alfred.workflow.action.applescript] {
    NSAppleScriptErrorBriefMessage = "Expected class name but found identifier.";
    NSAppleScriptErrorMessage = "Expected class name but found identifier.";
    NSAppleScriptErrorNumber = "-2741";
    NSAppleScriptErrorRange = "NSRange: {417, 8}";
}

Not working ft command

It works perfectly fine when I open a finder window from terminal, but not vice versa.

Improve performance of opening iTerm

You might want to use

tell application "iTerm"
    set myterm to (make new terminal)
    tell myterm
        launch session "Default Session"
        tell the last session
            write text "cd " & pathList
        end tell
    end tell
end tell

for opening iTerm. This is much faster.

fi in iterm2 doesn't work

iTerm2 Build 3.0.5
Alfred 3.0.3

fi

[2016-07-20 12:19:58][ERROR: action.applescript] {
NSAppleScriptErrorBriefMessage = "Expected end of line but found class name.";
NSAppleScriptErrorMessage = "Expected end of line but found class name.";
NSAppleScriptErrorNumber = "-2741";
NSAppleScriptErrorRange = "NSRange: {566, 6}";
}

find -> iTerm don't work

Starting debug for 'TerminalFinder'

[ERROR: alfred.workflow.action.applescript] {
    NSAppleScriptErrorBriefMessage = "Expected end of line but found class name.";
    NSAppleScriptErrorMessage = "Expected end of line but found class name.";
    NSAppleScriptErrorNumber = "-2741";
    NSAppleScriptErrorRange = "NSRange: {566, 6}";
}

fi cannot bring hotkey window to front

iterm2 3.1 beta 5
macOS 10.12.6
current workflow version

There is always a hotkey window in the background. When I use fi, however, it open a new tab in hotkey window profile but not bring hotkey window to front. I trie append tell application "System Events" to key code 103(which F3 is my hotkey) but it doesn't work.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.