muhqu / dterm Goto Github PK

There are some CAs that provide Code Signing Certificates for open source developers...

• http://stackoverflow.com/questions/1177552/code-signing-certificate-for-open-source-projects/1177748#1177748
• https://www.certum.eu/certum/cert,offer_en_open_source_cs.xml

Hi!

Since updating iTerm2 to the latest beta (Build 2.9.20160206, from https://github.com/gnachman/iTerm2/releases/tag/v2.9.20160206 or https://iterm2.com/downloads/beta/iTerm2-2_9_20160206.zip), the Execute in Terminal command won't open a new iTerm window as it used to do.

I've reached out to the developers (https://gitlab.com/gnachman/iterm2/issues/4210) and their response is that DTerm needs to be updated:

George Nachman @gnachman 2 days ago

DTerm will need to be updated to use the new applescript syntax. I've reached out to their support folks by email.

Looking forward to this issue getting sorted as this is greatly reducing my productivity!

Thanks to both parties!

Remember window size and position, like Terminal/iTerm app. Reasoning is even if sometimes I like half height, I still prefer full width, like all other windows I have controlled with my window manager.

@aberezin raised the following issue last year (bdrister#4)

On an unrelated topic, I have been seeing this error/clutter in the non-terminal output
bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell

I confirm the same (OS X, GNU bash, version 4.4.12(1)-release (x86_64-apple-darwin16.4.0)). (This version of bash allows bash-completion, which is a nice feature.) Would love to see this fixed!

If working directory and current document could not be determined, it should be possible for the user to drop some 'user script' (bash script, executable...) a defined location and hav DTerm invoke it to get the desired information.

I think it more about sandboxing issue while fish shell can't get $TERM env.
fish global config (/usr/local/etc/fish/config.fish) and --init-command both not working as expect.

disable interactive mode to get rid of warning message seems works fine

DTRunManager.m

+ (NSArray*)argumentsToRunCommand:(NSString*)command {
    NSString* shell = [[DTRunManager shellPath] lastPathComponent];
    
    if([shell isEqualToString:@"bash"] || [shell isEqualToString:@"sh"])
        return @[@"-l", @"-i", @"-c", command];
    else if([shell isEqualToString:@"fish"])
        return @[@"-c", command];
    else
        return @[@"-i", @"-c", command];
}

Partial of the debug result with fish shell under NSTask or Process in swift

<2> fish: init_locale() setlocale(): 'C'
<2> fish: curses var TERM=''
<2> fish: curses var TERMINFO=''
<2> fish: curses var TERMINFO_DIRS=''
<W> fish: Could not set up terminal.
<W> fish: TERM environment variable not set.
<W> fish: Using fallback terminal type 'ansi'.
<2> fish: 256 color support: using 8 colors per terminfo
<2> fish: curses var TERM='ansi'
<2> fish: curses var TERMINFO=''
<2> fish: curses var TERMINFO_DIRS=''
<2> fish: 256 color support: using 8 colors per terminfo
<2> fish: sourcing /usr/local/share/fish/config.fish

When working in projects that have deeply nested directory structures (e.g. Java/Scala projects) it would be great to identify the project's working directory by searching for common top-level project files...

• Given open file is /Users/leppich/workspace/ProjectA/src/main/java/com/example/Example.java
• And file exists /Users/leppich/workspace/ProjectA/pom.xml
• When DTerm gets invoked
• Then working directory should be /Users/leppich/workspace/ProjectA/

The working directory could be discovered by searching the filepath upwards for entries like:
Makefile, Rakefile, build.xml, pom.xml, .git, .svn, .hg etc..

I've seen many scripts using colorised output depending on the severity of the information. CocoaPods for example uses red for errors and green for success. Maybe we can incorporate colored outputs to dterm?

From prior comments it appears that muhqu is no longer supporting DTERM. It is one of my favorite things about my Mac setup, I've been using it for 10 years and am about to move over to an M2. I'm open to supporting the project financially so we can get long term support going. My company does Qt programming in C++ so Objective C is outside of our area of expertise. If anybody is interested in collaborating on this let me know. Presumably somebody who knows how to compile DTERM and can add functionality via objective C. You can write me via the contact information on my company website, cepuder.com.

IntelliJ doesn't support the Apple Scripting Bridge per default.

However, using the SystemEvents api we should be able to get the filepath and window position:

$ osascript -s so -e ''\
'tell app "System Events" to '\
'tell first process whose frontmost = 1 to '\
'return {'\
'value of attribute "AXDocument", '\
'value of attribute "AXPosition", '\
'value of attribute "AXSize" '\
'} of window 1'

{"file:///Users/leppich/IdeaProjects/path/to/some/Awesome.java", {0, 23}, {2560, 1364}}

I think that some of the startup behavior changed in the newer version (4.x) of Bash as opposed to the Mac OS X supplied version.

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

I am using El Capitan.

Any ideas? Thanks!

I would like to be able to scroll through the command history and copy a command previously entered.
Current the command output can be selected and copied but not the command itself.

Hi!

I'm just starting to use Big Sur from a fresh install, and "out of the box", the $PATH I get in DTerm is not the same that I get in e.g. Terminal or iTerm. I'm also new to ZSH so I expect it's something related to how the path gets built

On Terminal I get:

% echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Contents/Public:/Library/Apple/usr/bin 

While in DTerm I get /usr/bin:/bin:/usr/sbin:/sbin

I have not customised any ZSH files yet. I can "see" that the path on iTerm/Terminal gets "built" out of /etc/paths and the files in /etc/paths.d but I don't know why DTerm is not "picking" it.

Could you please consider adding a Homebrew formula for the release?

Thank you.

should use https://github.com/andreyvit/yoursway-create-dmg

As filed over here: bdrister#4

I upgraded to from iTerm2 2.x to 3.0. dTerm silently fails to open a terminal window now. But this is in the logs:
6/8/16 6:45:48.825 PM DTerm[526]: Can't find app with identifier net.sourceforge.iTerm
6/8/16 6:45:48.834 PM DTerm[526]: warning: <ITermApplication @0x40015bce0: application "iTerm" (309)> has no class for scripting class "terminal".

Thanks @aberezin for reporting!

Please make a release for Apple Silicon.

A command line anywhere and everywhere

sounds like multi-platform

First, thanks a lot for maintaining DTerm.

After upgrading to the latest release (1.7.73-4a3bc5c), Execute in Terminal does not work unless if the Terminal (iTerm) is not opened. Before it was fine, where it opens a new terminal (iTerm) window regardless of if iTerm is running or not.

My system info:

• El Capitan 10.11
• DTerm: Version 1.7.73-4a3bc5c (1.7.73)
• Default Terminal: iTerm

Problem;

• Nothing happens when I click cmd-enter, if iTerm is active.

thanks again.

Hi!

DTerm is not properly "autocompleting" the commands that are available in the PATH.

For example, I have ffmpeg and mediainfo on /usr/local/bin and typing media⇥, which I expected would trigger autocompletion, in fact does not.

I thought it was due to the issues with the PATH I mentioned on #20 - but once I sorted them out, I still can't autocomplete the commands. If I type them in full, they work (so the PATH is correct), but it's a pain to do so...

Looking around for potential solutions, I found this reference to the need for doing rehash, so I've added to the bits of my .zshrc file that run when it's DTerm... but they seem to be run after the command is typed and executed?

Where does DTerm "get" the autocomplete list?

DTerm is showing iTerm2 v3.0.2's Shell Integration variables. How can we prevent it from showing? These don't show in iTerm 3 or Terminal (OS X).

DTerm

iTerm

Terminal