General / Sublime Text

+4

"Open Terminal here" as tab instead of window if possible

13 lat temu • zaktualizowano 13 lat temu • 0

I used the iTerm.sh as a basis for this:

#!/bin/bash

CD_CMD="cd "\\\"$(pwd)\\\"" && clear"
VERSION=$(sw_vers -productVersion)

if (( $(expr $VERSION '<' 10.7) )); then
    RUNNING=$(osascript<<END
    tell application "System Events"
        count(processes whose name is "Terminal")
    end tell
END
)
else
    RUNNING=1
fi

if (( $RUNNING )); then
    osascript<<END
tell application "System Events"
    tell process "Terminal" to keystroke "t" using command down
end
    tell application "Terminal"
        activate
        do script with command "$CD_CMD" in window 1
    end tell
END
else
    osascript<<END
    tell application "Terminal"
        activate
        do script with command "$CD_CMD" in window 1
        end tell
    end tell
END
fi

Głosuj

+4

Ukończony

See filename of currently active documents

14 lat temu • Ostatnio zmodyfikowane przez 13 lat temu • 1

I want to be able to see the path of the current document I have open in each editing pane. I often have files open for different sites with the same name, so I'd like to be able to see I'm editing the correct file without having to hover over the tab name to verify each time.

Głosuj

Odpowiedź

13 lat temu

This was added in build 2091

+4

Completion overlay size too small

14 lat temu • 0

When hitting ctrl+space for getting the completion overlay popped up, many of our longer class/method/function names get shortened to fit into the narrow window. It seems to be the fuzzy algo which does this. It would be better to let the window grow horizontally a little more - the screen is big enough :).

Screenshot: http://dl.dropbox.com/u/587049/sublime%202034%20too%20narrow%20overlay.png

Głosuj

+4

Haskell Syntax Highlighting - improper highlighting in import and module declarations

13 lat temu • 0

statements like:

module Text.Disassembler.X86Disassembler(

someX86function

) where

and

import Text.Disassembler.X86Disassembler

leave 86, 86function, and 86 (respectively) unhighlighted.

Similarly,

import Control.Applicative((<$>),(<*>))

leaves (<*>) unhighlighted (&, and other characters that might be used in operators are also unhighlighted).

Głosuj

+4

Project Name's Listed Above Folders On Sidebar (on title bar too?)

12 lat temu • Ostatnio zmodyfikowane przez 12 lat temu • 1

I would like it if a project could have a name associated with it and if it can be listed in the sidebar above or around 'folders'. It would also be great if this could be listed on the title bar as well. I have multiple sites with near identical folder structures. Adding all the different sites into one project is not realistic due to to many speed reasons and search reasons etc. Thank you so much!

Głosuj

+4

pythonpath

13 lat temu • zaktualizowano 13 lat temu • 1

For the wisdom of Feynman I can't make my PYTHONPATH known to the build system. I have now added it to the Environment.plist (rebooted), to my .bash_profile and also added the commands to make it known to the launchctl on my Mac. But still SublimeText can not find my PYTHONPATH.

I also tried to set an ENV variable with the build system as somebody else tried on stack overflow, but as for him it was unsuccessful for me as well.

It really should not be so hard to do this, should it?

Any other ideas?

Głosuj

+4

Showing function's arguments when typing "(".

12 lat temu • 0

For example, if I type "unlink(", a tooltip will be openned with the arguments: "unlink(string $file..."

Głosuj

+4

control click html links to open them in browser

12 lat temu • zaktualizowano 12 lat temu • 1

- hotkey to open a selection of links

- cf. http://superuser.com/questions/209258/open-http-links-from-notepad-to-default-web-browser

Głosuj

+4

Please fix the mouse trap below the mini code preview area

12 lat temu • 0

Clicking in this invisible area for extremely valid reasons has the unintentional, immediate, and frustrating effect of scrolling me all the way down to the bottom.

I understand “why” this happens — clearly the preview thing extends to the bottom of the window — but it should not.

This is very annoying and frustrating when it comes up. It forces me to think about yet one more thing when working with my code, and reduces my target click area at the end of long lines (violating Fitts’ Law).