New answers tagged

1

Thanks to @don_crissti's help and the answer they pointed me to. In order to change Gnome Terminal keybindings a path must be provided for the schema (as it is relocatable). So we need to define both a schema and a path: GSETTINGS_SCHEMA=org.gnome.Terminal.Legacy.Keybindings GSETTINGS_PATH=/org/gnome/terminal/legacy/keybindings/ SCHEMA_PATH=$...


2

You are likely (attempting) to redirect the output of your shell to a file, e.g., something like bash -i | tee foo $ vim Vim: Warning: Output is not to a terminal While you can read (most) commands from the keyboard via that approach, the output is no longer a terminal. You can recover by closing that shell and capturing output in a different way: the ...


0

Last time I had to do this I overrode the default gnome-terminal, which I don't have, with xterm. Assuming you have installed xterm then edit your local.conf file, eg with echo 'OE_TERMINAL = "xterm"' >>conf/local.conf


0

It seems i can not find correspond command to solve the problem. So I created recommended script. This script has some problems but better than nothing. Before use script i need install xdotool with command. apt-get install xdotool to restore saved terminal i use: gnome-terminal --load-config='my path to script' But anyway i hope someone knows better ...


1

You can simplify your solution so that you only need to specify the hostname once. The test.sh script can set the prompt directly with the echo command and then run the ping you want. $ cat test.sh #!/bin/bash echo -ne "\033]0;$1\007" script -a -c "ping $1" $PATH_REPORT/$1.log Now you can call this with gnome-terminal -x ./test.sh $varname (make sure ...


0

There is only a tiny fault I think. sudo opens a new shell for executing the command and after sudo the user is root. So maybe you should use something like this: MYUSER=$USER sudo chown $MYUSER:$MYUSER as i think MYUSER is not systemspezific overwritten and shall work.


5

Have you tried having script be the outer part gnome-terminal -x script -c "ssh user@IP" logfile.log


1

This turned out to be because I had enabled the ui color=always option in git, not directly because of my shell prompt or the parse_git_branch function. The "git branch" command was displaying with color, but the original author of the parse_git_branch function did not account for that and chopped the string up in such a way that the color codes didn't get ...


1

When you install git package. It should install a local file that you can source which has the branch parsing built in. Have you tried using that instead? I use this with no issues. This is taken from RHEL, so git-prompt.sh might be in a different location on ubuntu. Just do a "locate git-prompt.sh", alternatively looks like a version is available ...


0

put this in .bashrc: function title() { p1='echo -ne "\033]0;' p2='\007"' PROMPT_COMMAND=$p1$@$p2 p1= p2= }


2

The strings aren't actually ANSI sequences. Rather, they started as ANSI sequences, but are translated (due to some scripting error) on your remote machine so that most of the characters are converted to a different form. An ANSI sequence for instance would have escape[A possibly with an optional ; before the A, but the problematic output shows a 133 ([ ...


0

This data very much looks like ANSI escape sequences. Those can be used to switch color of your characters, to change the title bar of your terminal emulator and much more. They work by printing those codes directly to screen and hoping that your terminal emulator understands them correctly. Some (like changing color) are implemented in pretty much every ...


0

CentOS 6 has 2.31.3; CentOS 7 has 3.14.3 (where the feature works). It is not a new feature, having been introduced in 2007: Bug 118967 – single line scrolling with "Ctrl+Shift+ArrowUp/ArrowDown" while 2.31.3 dates from 2010 (a noticeable delay even for the enterprise releases). However, it does not work with CentOS 6 and incidentally, the git-commit logs ...


0

On more recent versions of gnome-terminal, Shift+Ctrl+↑ and Shift+Ctrl+↓ work for scrolling by line, but I have no way of checking for 2.31.



Top 50 recent answers are included