This still isn't ideal, since we aren't even being careful about what the
change is or to which branch the change is for.

However, it does result in our change monitor properly updating the lines
in the gutter of the current document.

Debug code that slipped into previous commit.

We need to ensure we load the new version of the repository, so this
gets that new repository version to the change monitors.

We still don't seem to be getting notification of .git/index, not
entirely sure why.

If we are at the end of the file, we will have a gunichar of zero. Handle
this specially, since it's okay to continue to walk backwards.

Using the shared recent manager seems to fix our issue with projects that
are loaded not showing up in the recently-used.xbel.

The top bar was broken for Cantarell at 10pt font because GtkEntry
was not expanding to the allotted space. (Allocation was correct,
but the draw area was not).

This simply works around the issue by using the same margin we would
get from image-button and applies it directly to margin-top.

Unused for now, so just #if 0 the helper function

if __name__ == '__main__':<Return>

This was failing to indent because we were walking back an extra character
to deal with some faulting strings. I think it is okay to simply remove
this movement.

This tries to handle tabs a bit better. Additionally, it tries to ignore
lines who's 'if' or 'for' are after the visual column we started on.

Hopefully I didn't break anything else!

This tries to use more generic style names that are more common across
style schemes.

This looked kind of tacky. Also, none of the gtk+ scrollbars change
the cursor, so it doesn't even follow convention.

This will translate the scroll event into a ::move-viewport on the
primary GtkSourceView widget.

It would be nice if we could deal with smooth scrolling here, but the
X11 gdk backend seems to be doing that pretty well with my touchpad.

We'll see how big of an issue it is based on user feedback.

There is a case we restored nothing, and the command line files have been
requested to be opened, but no buffers have yet been created.

We don't want to open a temporary buffer in that case.

Patrick Griffis authored Apr 24, 2015 and Christian Hergert committed Apr 25, 2015

https://bugzilla.gnome.org/show_bug.cgi?id=748427

Patrick Griffis authored Apr 24, 2015 and Christian Hergert committed Apr 25, 2015

https://bugzilla.gnome.org/show_bug.cgi?id=748427

Patrick Griffis authored Apr 24, 2015 and Christian Hergert committed Apr 25, 2015

https://bugzilla.gnome.org/show_bug.cgi?id=748399

Patrick Griffis authored Apr 24, 2015 and Christian Hergert committed Apr 25, 2015

The GNOME macros are quickly being deprecated
and use of autoconf-archive is suggested.

https://bugzilla.gnome.org/show_bug.cgi?id=748399

We were only updating the value when we would save/hide the project tree.
This does it after a second delay when the paned is moved. That should
still handle the animation case, where this will be spuriously updated.

Clearly, this is the type of stuff that belongs in a layout manager
abstraction.

I've tried out some alternative fonts such as Redacted and BLOKK, but they
don't give much insight to the content. Just using a bold weight seems
to improve things a bit.

It looked a bit too blocky when creating new files. I want it to be
slightly bigger than on the left gutter, but not ridiculous.

This should make the color a bit more visible for various themes.
solarized dark and light look much better, for example.

We can remove this later, but for a couple weeks we should have this.
Although, I'm not sure we are fast enough at loading gtkwidgets to
really handle over this anyway.

We need to adjust the number of popovers we use as well as listboxs.

This will restore any of the previously loaded files when restoring the
context.

   ** I'm sorry if this causes a bunch of files to open on you **
   ** initially, since we failed to prune them in the past.    **

Once you close them (and wait a few seconds for the reclamation to
happen), they shouldn't come back.

If it gets really annoying, and you want to have a clean slate, just
remove everything in ~/.local/share/gnome-builder/drafts/

I think what we want to do long term, when closing with unsaved files
is to determine which of these use cases we want.

 1) save the changes to a draft, but leave the real file untouched.
 2) just save the file to the original file.