global config setting "window_state = maximise" does nothing

[Sam Chodur Jr.]

Reading the manual page for terminator_config tells me that in the global config scope of the configuration file, I should be able to set: window_state = maximise so new instances of terminator will be maximized. When I put this setting in my config file, it does nothing.

I tested using window_state = fullscreen and it worked, but window_state = maximise, window_state = maximize, do nothing.

[Stephen Boddy (stephen-j-boddy)]

Are you by any chance launching terminator with dbus active and already have an instance running? If dbus is active the new window is actually a new window from the first terminator that initialised the dbus interface. If that instance was started before you changed the config, then it would not automatically detect the change to the config file. The simplest way to check is to use the "-u" flag to launch terminator which disables the dbus, and launches an entirely separate process. Alternatively exit everything terminator related, and run from scratch.

Also be careful if using a layout as layouts have a maximise = True/False option in newer versions (post 0.97 IIRC) that may well override this global option.

[Sam Chodur Jr. (samuelchodur)]

I can assure you I am launching a fresh instance of terminator. I also make sure the config file is the way I want it to be before launching the new instance.

I am using terminator version 0.97.

Again, using window_state = fullscreen works just fine, but window_state = maximise does not work.

I will attach the config file being used while testing.

Maybe someone else will test if window_state = maximise works for them?

The reason I am using this in the global scope is because the manual page for terminator that exists on my distribution shows no other way to start terminator maximized.

[Stephen Boddy (stephen-j-boddy)]

Hi Bug subscribers, this is the maintainer (Steve Boddy) of Terminator, who took over from Chris.

In case you were not aware there has been a new release 0.98 of Terminator in the last few days which has many changes, fixes and updates. We also have an ongoing GTK3 port which uses a much more up-to-date libvte.

Even with the ~50 issues closed by that release, and discounting the ~90 outstanding wishlist items, we still have an unwieldy 95 bugs. With the oldest approaching it's 6th birthday and some that haven't seen any updates in nearly 5, it is time for a purge.

My intention is to try and get this list down to a minimum, and for that I need your help.

First I'm going to work through, oldest to newest, setting bugs to Incomplete, pending confirmation that they are still an issue. If after a month there is no feedback, the issue will get closed as Invalid. Here's where you come in. I can't always reproduce, or setting up (i.e. other distros) to even test takes a long time, so I'm going to try crowdsourcing this.

1. Get the latest release. Is it still an issue? If yes, set the confirmed-0.98 tag. For bonus points follow the guide http://gnometerminator.blogspot.com/2015/09/so-you-want-to-try-terminator-gtk3.html and see if the GTK3 branch has same issue, and set the confirmed-gtk3 or notaffected-gtk3 tag.

2. Can you reproduce with an empty/default config file? You can pass "-g temp_config" to do this without affecting your existing config. If you already have Terminator running, you'll need to pass -u as well to disable the DBus.

3. If able to, can you reproduce with another user/guest account?

4. If the issue does not already have clear, precise instructions to reproduce with minimal setup/steps, add them.

5. Put as much info about what you are running.
   * Software/library versions (libvte, gtk, pango, cairo, distro, desktop environment, language)
   * Screens (single or multi)
   * Any unusual / custom packages or configs that might be interacting.

6. If possible attach the config file, unless the issue also happens with an empty one, but mention that.

7. Attach the "-d" debug output from 0.98.

Some common things that cause incidents.

* Strange sizing issues or rapidly shrinking windows - Try turning off Window geometry hints.
* Input (esp. broadcasting duplicate chars etc) problems - Try killing IBus.
* Hand editing of the config file can cause various issues - Due to misunderstanding, incorrect structure or typos.
* Some issues are actually in libvte - This is why testing GTK3 is so important.
* segfaults - Unfortunately these are dying inside the C libraries, and it is usually beyond me to fix those.

Many thanks for your assistance, and hopefully this will get us closer to a bug-free Terminator.

[Stephen Boddy (stephen-j-boddy)]

Old bug, codebase has moved on a lot, and unable to reproduce. Also OP has never returned to bug.

[Stephen Boddy (stephen-j-boddy)]

Marking as Invalid/no-response.