After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 754335 - Block cursor in emacs mode
Block cursor in emacs mode
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: preferences
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-31 08:28 UTC by Alexander Larsson
Modified: 2018-01-11 09:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander Larsson 2015-08-31 08:28:11 UTC
I see the vim mode has a block cursor. Emacs on X usually has a block cursor too, so we should probably make emacs enable it too. In fact, maybe it would make sense to make this a generic preference so that people using the "default" key theme can get it too?
Comment 1 Christian Hergert 2015-08-31 08:31:27 UTC
(In reply to Alexander Larsson from comment #0)
> I see the vim mode has a block cursor. Emacs on X usually has a block cursor
> too, so we should probably make emacs enable it too. In fact, maybe it would
> make sense to make this a generic preference so that people using the
> "default" key theme can get it too?

I'm not sure if you went through and saw how this was implemented.

We hijacked overwrite mode and then suppress what we can after looking up a binding entry.

What we really should do, is allow the cursor to be styled, and plumb that all the way into GtkTextLayout. I took a brief look at this, and it seemed non-trivial.
Comment 2 Alexander Larsson 2015-08-31 10:27:54 UTC
Ugh, yeah, better leave this as is until we have a clean implementation.
Comment 3 GNOME Infrastructure Team 2018-01-11 09:51:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-builder/issues/42.