You Got A Question? Ask    GNOME Community!


GNOME Terminal 3.7.0 release!

This post was made with an older stylesheet


No Close Option in Context Menu

I have hundreds of time closed Terminal without wanted. I just “Right Click” and Terminal is gone :)

terminal-close-tab

The close option will now be gone in Terminal 3.8. Following the bug (#551284) there is a funny report from Joseph:

I accidentally close the terminal too. I have a sensitive touchpad that occasionally opens the popup. I hit the “l” trying starting to type “ls” and my window is gone before I realize what has happened. It’s been annoying enough change it and compile it myself.

Okay, that was really annoying but re-compiling Terminal just for it, is extreme, yet funny :)


Scroll-back length is now default at 8192 lines

According to bug report (# 624195) a suggestion was that the length of history could be set relative to the RAM, for example:

  • If you have 128MB RAM,  scrollback could be set to ~500 lines
  • If you have 1GB RAM, scrollback could be set to ~10.000 lines
  • If you have 16GB RAM, scrollback  could be set to ~10.000 lines

The default was 512 lines, but from now on the default scroll-back length -no matter the RAM- will be set at 8192 lines. You can change this anyway from Terminal Settings.

scroll-back-settings

Some Distros are affected from a bug, that even if you change this value you won’t notice any difference.

Speaking of history for the people that don’t know it there is a history command, just give history in a terminal

$ history

You can run a history command by using “!” + the number of history

$ !<history number>

This is specially helpful (and a must in a Console that doesn’t support mouse) if you have a long command because you can search it, and run it

$ history | grep -i "your command" (search for it)
$ !<history number> (and run it)

With “!!” you can run the previous command, which is handy if you want to re-run a command with sudo permissions.

$ sudo !!

Or you can use the “-” to run an older command.  For example:

$ !-4

Will run the latest 4th command.

Another useful tip is to enable the reverse search by pressing <Ctrl+R>. Anyway there are endless possibilities with bash history, and you can Google around for it.


GNOME Terminal 3.7.0 Changelog

  • Terminal now uses GSettings and DConf instead of GConf. The existing profiles and settings will be automatically migrated from GConf when first running this version.
  • To make new tabs opened within Terminal have the same same working directory as the current tab, it is necessary for the shell running in the terminal to cooperate. For this, vte installs a bash shell script that you  must use in your bash PS1 prompt. For example, you can put this at the end of your ~/.bashrc: export PS1=’\[$(__vte_ps1)\]’$PS1
  • Many bugs fixed
  • Many translations updated

Changelog in Git


 
  We can't watch comments unless G+ provides an API or if you send a notification, e.g +World Of Gnome
     Sometimes is better to place your questions on GNOME Community
  • http://varemenos.com/ Adonis K. (Varemenos)

    @close window ‘fix': Instead of getting rid of that, they should be fixing the source of the problem (which is the weird right click behavior)

    • alex285

      Agree, but they should had get-rid Close from there anyway.

      • http://varemenos.com/ Adonis K. (Varemenos)

        Ya i know, i agree with the decision. It was a really bad UX decision to have it there.

  • martinvars

    try “control+r” to reverse search history in bash.

    • alex285

      Thanks for it, I added it!

  • Stiph

    “According to bug report (# 624195) length of history is relative to the RAM:”

    Heh? No, you misread the bug: these are just reporter suggestions to how the length of history could be adjusted automatically depending on the amount of RAM on the system, the numbers are irrelevant, just to illustrate the suggestion. How would you expect to find RAM usage without even knowing the number of columns?

    I think you’ll scare readers by saying “1GB RAM, scrollback is ~10.000 lines”. That’s ~100KB by line?!!

    On my box I’ve got ~200 columns, and with a history of 10k lines with all columns full, gnome-terminal consumes ~10MB.

    Please update/remove that, please :)

    • alex285

      Hello,
      That means that if you have 1GB RAM your scroll will be 10.000 lines, not that 10.000 consumes 1GB. Do I placed it wrong?

      • Stiph

        Ok, I’ll try to rephrase:

        1) The bug just changed the default from 1024 to 8192 (not 10000) and nothing else, look by yourself:

        http://git.gnome.org/browse/gnome-terminal/commit/?id=7c987a13911b53349fdf29b7132044b89f5397a2

        2) The reporter suggested to adapt the number of lines depending on the available RAM, but that it is not done. It was just a suggestion.

        3) The way everybody will read the article it is that 10k lines consumes 1GB in the way it is written, and anyway the whole first paragraph is false!

        Only “but anyway from now on the default scroll-back length no matter the RAM will be set at 10.000 lines” at the start of the article can be kept and is almost the truth. Please remove the text before that.

        I’m sorry, I do not know how to explain that better…

        • Stiph

          “The way everybody will read the article it is that 10k lines consumes 1GB in the way it is written”

          I meant the RAM usage will look like incredibly ultra high.

        • alex285

          Okay, fix that. I didn’t read the commit, my bad!

    • alex285

      Aha I see, it was a suggestion, so I edit that, thanks for noticing!

      • Stiph

        Still, I suspect readers will think the terminal RAM consumption is terrible with that big figures! Not your fault but the reporter, but I would have just removed that paragraph. Anyway, I suppose it should be enough, thanks.