dterm icon indicating copy to clipboard operation
dterm copied to clipboard

Fails to open shell with iTerm2 3.0

Open aberezin opened this issue 9 years ago • 7 comments

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".

aberezin avatar Jun 09 '16 09:06 aberezin

oh… interesting! I'm maintaining a fork of DTerm here: https://github.com/muhqu/dterm I did not yet noticed there is a 3.x beta/nightly. Thanks for letting us know.

muhqu avatar Jun 09 '16 11:06 muhqu

Awesome! I really like this little app and was hoping someone would take it on. This may even motivate me to learn a little iOS dev skills. I clone/built your fork and it seems to have fixed the problem.

aberezin avatar Jun 09 '16 12:06 aberezin

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 also need a way in my bashrc to detect if this is dterm and exit early before I set a bunch of stuff that dterm doesnt like. This is even more true with iTerm2 3.x since they have an optional bash script to add more goodies that are iTerm specific. I can make separate issue if needed for one or both items. Thanks again for taking this project on.

aberezin avatar Jun 09 '16 12:06 aberezin

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 believe this only happens in bash 4 (and some other shells like mksh), not in version 3.

I don't know of a workaround though.

I also need a way in my bashrc to detect if this is dterm and exit early before I set a bunch of stuff that dterm doesnt like.

DTerm sets TERM_PROGRAM to DTerm, so you can check something like

case "$TERM_PROGRAM" in
DTerm)
    # It's DTerm!
    ;;
*)
    # It's something else!
    ;;

mkhl avatar Jun 09 '16 13:06 mkhl

Maybe it's also helpful to list all variables that are present to commands executing in DTerm. With bash you can list them like this: (set -o posix; set)

muhqu avatar Jun 09 '16 13:06 muhqu

Thanks. Yes, Bash 4 is what I am using. $ bash --version GNU bash, version 4.3.42(1)-release (x86_64-apple-darwin14.5.0)

aberezin avatar Jun 09 '16 13:06 aberezin

Thank you for this fix. It is my favorite feature of DTerm and I'm glad it's working again.

leingang avatar Nov 17 '16 13:11 leingang