GitLab

Bug #611286.

Bug #606298.

Add per-profile (and hence gconf) options for setting default size.

Add an "Unlimited" chekbox for scrollback lines.

Add a "Bold color same as text color" checkbox.

The current UI simply adds a Bold color in the Colors tab.  I think
we should also add a "Use different color for bold" checkbox before
it, otherwise (that is, right now), you need to change both foreground
and bold manually.

Also part of Bug 596688 - Expose more proxy settings

If /system/proxy/mode is set to auto, we put "pac+URL" into http_proxy
where URL comes from /system/proxy/autoconfig_url.

Last part of Bug 596688 - Expose more proxy settings (edit)

Part of Bug 596688 - Expose more proxy settings

Part of Bug 596688 - Expose more proxy settings

Get the right padding values from the inner-border style property.

Bump vte req to 0.23.1.

The terminal screen won't be realized until the first time it's becoming
the active tab.

The goal is to defer launching the child process until after the widget
is realized, and we want to defer that until the toplevel window is
realized.

Instead of the XID of the TerminalScreen's GdkWindow, which forces it to
be native.

Should fix bug #590952.

This reverts commit 5b34cfbe.

Fix variable name causing build error in terminal_screen_launch_child().

Instead of passing the error->message by the format arguments using %s in the
format, pass the GError directly and format it as secondary text.

Go back to basing the decision whether to show the confirm-close dialogue
on the number of tabs only, as before.

Go back to using the primary child to determine the cwd, instead of the foreground pid.
This fixes e.g. the cwd being set nondeterministically in new tabs when running 'find'
in the current tab.

At the point when the the TerminalScreen is mapped, we are at a
funny state:

 - The terminal window is mapped
 - GTK+ hasn't yet applied the default size

Since the terminal window is mapped, we call gtk_window_resize()
instead of gtk_window_set_default_size() and end up mapping with
the wrong default size. (The observed effect is that depending on
timing, the terminal will be reset to 80x24 when switching to
a compositing window manager.)

The simple fix is to not resize the window when the TerminalScreen
is realized - changing sizing during realize is a poor idea in
all cases - but rather at the start of show().

http://bugzilla.gnome.org/show_bug.cgi?id=564648

Don't return the home dir from
terminal_screen_get_current_dir_with_fallback. Only return the initial
working dir if priv->pty_fd == -1. Bug ##565328.

When we can't get the cwd of the process in the terminal when opening a
new tab, fall back to its initial working directory, or $HOME. See
bug #565328.

Don't match trailing punctuation and closing braces, like we used
to do previously.

svn path=/trunk/; revision=3396

svn path=/trunk/; revision=3390

svn path=/trunk/; revision=3378

svn path=/trunk/; revision=3377

factory's env.

svn path=/trunk/; revision=3372

Make sure to return a string dup.

svn path=/trunk/; revision=3329

svn path=/trunk/; revision=3325

Correctly use the broken vte_terminal_get_padding() API.

svn path=/trunk/; revision=3321

ever needed when creating a new terminal.

svn path=/trunk/; revision=3289