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 154080 - Close Tag plugin
Close Tag plugin
Status: VERIFIED DUPLICATE of bug 163014
Product: gedit-plugins
Classification: Other
Component: General
Other All
: Normal enhancement
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Reported: 2004-09-29 17:42 UTC by Alan Horkan
Modified: 2019-03-23 20:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8

Description Alan Horkan 2004-09-29 17:42:14 UTC
I have recently reviewed an application you might have heard of called "GTK2
Text Editor" 

despite the authors ill received overly ambitious statements that it could
replace Gedit (and the equally unfair hostile reactions to his attempts to earn
money in return for producing windows binaries) 
GTK 2 Editor is not yet as good as Gedit 
(nowhere near as HIG compliant) 
however it did have one particularly clever thin I liked which was a "Close Tag"
feature, which with a simple keyboard shortcut will automatically create a close
tag for whatever tag you last opened.  

If you had typed <blockquote>you could then with a quick keypress have
</blockquote> added automatically

i think a similar feature could make a good useful plugin for gedit 
(as GTK2 Text Editor is licensed under the GPL it might even be possible to
reuse the code)
Comment 1 Paolo Maggi 2004-12-09 16:05:50 UTC
I like the idea.
It shouldn't be to difficult to implement even for a new gnome lover?
Should we post a reference to this RFE on gnome-love ML?

Here a reference to the GTK2 Text Editor code that implemets this feature:

Comment 2 Paolo Maggi 2005-01-11 10:31:16 UTC

*** This bug has been marked as a duplicate of 163170 ***
Comment 3 Paolo Maggi 2005-01-11 10:32:47 UTC
ops... wrong duplicated.
Comment 4 Paolo Maggi 2005-01-11 10:33:11 UTC

*** This bug has been marked as a duplicate of 163014 ***
Comment 5 Alan Horkan 2005-01-11 13:24:31 UTC
Why is an older bug report being marked a duplicate of a later report?  
Surely who ever files later is the true Duplicate?  
Comment 6 Paolo Borelli 2005-01-11 13:31:50 UTC
In general it is true, but in this case the newer bug has a patch attached and
some bit of discussion which we would prefer not to loose.
Comment 7 Alan Horkan 2005-01-11 19:31:04 UTC
Okay, makes sense, I'll accept and verify this.  
Wish you'd explained it when marking it though.